# US 2008/0270197 A1 · Project status calculation algorithm

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2008/0270197 A1
- Document ID: US20080270197A1
- Status: Published application
- Kind: A1
- Application number: 11/739,229
- Filed: 2007-04-24
- Published: 2008-10-30
- Earliest claimed: 2007-04-24
- Assignees: International Business Machines Corporation
- Inventors: Joseph R. Rafter; Russell W. Taylor; Vito R. Vitale
- Web page: https://patentgrep.com/patent/US20080270197A1

## CPC

- G06Q 10/00: Administration; Management
- G06Q 10/0635: Risk analysis of enterprise or organisation activities
- G06Q 10/06393: {Score-carding, benchmarking or key performance indicator [KPI] analysis}
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

Disclosed are a method and system for assessing the status of a project that remove subjectivity from the status reporting by implementing an algorithm to calculate red, yellow, green status of each of a multitude of keys and the overall project. The assessment uses a series of questions based on risk management, project management, system engineering, architecture, and testing disciplines to probe projects and solicit objective responses with scores and a conversion of the score into a red, yellow, green status. The advantage to this solution is that a consistent standard is provided, eliminating the accidental or purposeful exclusion of key details in status reporting that frequently result in a more optimistic status than what reality should reflect.

## Claims

### Claim 1

A method of assessing the status of a project, comprising the steps of:
identifying a multitude of key aspects of the project;
defining first, second, and third states for the key aspects;
identifying a series of questions relating to the project, including the steps of (i) identifying an initial group of questions based on analysis and investigation of multiple earlier projects, (ii) identifying a set of criteria to evaluate said initial group of questions, and (iii) refining said initial group of questions to a core group of questions by using said set of criteria;
for each of the key aspects of the project, selecting an associated set of questions from said core group of questions;
for each of the sets of questions (i) identifying at least one of the questions as a key indicator of a troubled project, (ii) identifying a first subset of the questions as indicative questions that directly reflect bad behavior or poor performance on a project, wherein predetermined answers to said indicative questions contribute given scoring values to the associated key aspect, and (iii) identifying a second subset of the questions as predisposition questions that identify factors that can create a predisposition to the associated key aspect becoming troubled;
scoring each of the key aspects based on the answers to the associated set of questions; and
assigning one of the three states to each of the key aspects based on the scores of said each key aspect, including the step of assigning any of the key aspect to the first state if predetermined answers are given to any key indicator of the set of questions associated with said any key aspect.

### Claim 2 (depends on 1)

A method according to claim 1, comprising the further steps of:
scoring the project based on the scoring of the total set of key aspects; and
assigning one of the three states to the project based upon the combined score of said each key aspect, including the step of limiting the contribution of any of the key aspect to the project score, as when predetermined answers are given to any key indicator of the set of questions associated with any said any key aspect, to a maximum predetermined contribution from any said key aspect.

### Claim 3 (depends on 1)

A method according to claim 1, wherein the set of criteria includes:
whether the question identifies a known problem behavior; and
whether the question is worded such that an objective answer is required.

### Claim 4 (depends on 1)

A method according to claim 1, wherein:
a majority of the core questions are yes/no type questions;
some of the core questions ask for a numeric ranking; and
the questions ask for objective evidence of behavior, including work products, schedule milestones and meeting frequencies.

### Claim 5 (depends on 1)

A method according to claim 1, wherein scoring of the key aspects provides a standard benchmark for status reporting that is common across the globe and therefore a consistent measure of projects.

### Claim 6 (depends on 1)

A method according to claim 1, wherein the core questions are based on risk management, project management, system engineering, architecture, and testing disciplines to probe projects and to solicit objective responses with scores and a conversion of the scores into said three states to provide a consistent standard that eliminates accidental or purposeful exclusion of key details of the project.
