METHOD FOR PROJECT MANAGEMENT

• US 20070288283A1
• Filed: 06/07/2007
• Published: 12/13/2007
• Est. Priority Date: 06/09/2006
• Status: Abandoned Application

• Current Assignee: Devshop
• Original Assignee: Devshop
• Inventors: Fitzpatrick, Craig
• Application Number:
  US11/759,917
• Publication Number:
  US 20070288283A1
• Time in Patent Office: Days
• US Class Current: 705/8
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/063118 Staff planning in a project environment
• CPC Class Codes: G06Q 10/0635 Risk analysis of enterprise or organisation activities

Abstract

A method for project management that can be used to achieve a more accurate project schedule at the beginning of, and during the life of a project. The method can be built into a software product, or used manually.

The method uses data collection, modeling, analysis, reporting and visualization to reduce the impact of risk in project scheduling and thereby improve the project'"'"'s chances of a successful outcome (e.g. as measured by stronger adherence to: budget, deadline, quality and specifications).

The method introduces time estimation error, distraction rate and schedule confidence into the project schedule and provides for visualization of the schedule in the form of Gantt charts in difference views organization by component, by team member and by project.

Claims

1. A method for project management by adding risk-based adjustments to a schedule for a project, the project having a plurality of tasks, each task having an estimated duration and one or more dependencies on other tasks, the project further having one of a plurality of team members assigned for executing each of the tasks and a project store for storing the task estimated duration, dependency and team member information for each task, the method comprising the steps of:

collecting all of the tasks in the project;

collecting, for each task, all of the predecessor tasks from which the task has a dependency;

adding to the collected predecessor tasks, for each predecessor task, any other predecessor tasks from which the predecessor task has dependencies until all predecessor tasks have been collected;

adding a risk-based adjustment to the finish date of each of the collected predecessor tasks, the risk-based adjustment comprising;

a distraction rate for the team member assigned to predecessor task; and

a time estimation error rate for the team member assigned to the predecessor task; and

rescheduling each of the tasks in the project to start on the business day after the latest finish date of any of the predecessor tasks of the task.

2. The method of claim 1, further comprising the step of calculating a distraction rate for a time period, the step of calculating comprising the steps of:

collecting all tasks in the project store;

filtering the tasks responsive to criteria including any one of;

a team member, a project and a time period;

creating a distraction collection;

adding to the distraction collection all tasks, not removed in the step of filtering, having meta-data indicating that the task is an explicit distraction;

adding to the distraction collection all tasks, not removed in the step of filtering, associated with other projects occurring during the period and that are assigned to a team member who is also assigned to at least one task in the project and indicate that the task is an implicit distraction in the meta-data of the task;

count a total number of working days available in the period for all of the team members who are assigned to at least one task in the project;

count the total number of distraction days by counting the estimated durations, in working days in the period, for all tasks having meta-data indicating that they any of;

explicit distractions and implicit distractions; and

calculate the distraction rate by dividing the total number of distraction days by the total number of available working days in the period for all team members who are assigned to at least one task in the project,

3. The method of claim 1, further comprising the step of calculating time estimation errors, the step of calculating comprising the steps of:

collecting all tasks in the project store that are complete;

filtering the tasks responsive to criteria including any one of;

a team member, a project and a time period;

calculating, for each task, a time estimation error by dividing the number of working days needed to complete the task that exceeded an estimated duration for task by the estimated duration for task; and

archiving the calculated time estimation error for each task.

4. The method of claim 1, further comprising the step of calculating schedule confidences, the step of calculating comprising the steps of:

collecting all tasks in the project store;

filtering the tasks responsive to criteria including any one of;

a team member, a project and a time period;

calculating, for each task, a schedule confidence by multiplying 33% by a number of approved preparation items for the task; and

archiving the calculated schedule confidence for each task;

wherein the preparation items include;

requirement, design and time estimate.

5. The method of claim 1, further comprising the step of detecting and recording circular references when making a first task dependent on a second task, the step of detecting and recording comprising the steps of:

collecting all tasks in the project store on which the second task has a dependency and adding the tasks to a pre-requisite collection;

adding to the pre-requisite collection, for all tasks in the pre-requisite collection, all tasks on which the task in the pre-requisite collection has a dependency;

creating a schedule assertion between the first task and each of the tasks in the pre-requisite collection;

testing each of the schedule assertions and capturing any resulting conflicts;

archiving the conflicts captured in the step of testing;

disallowing the making of the first task dependent on a second task when any conflicts were captured in the step of testing; and

allowing the making of the first task dependent on a second task when no conflicts were captured in the step of testing.

6. The method of claim 1, further comprising the step of presenting the rescheduled tasks in the form of a Gantt chart presenting, for each task, the estimate duration, time estimation error and a production of the distraction rate and the estimation duration.

7. The method of claim 6, wherein the Gantt chart presents the tasks organized by one of:

component, team member and project; and

wherein the Gantt chart organized by component presents the tasks grouped by task-group for a single project;

the Gantt chart organized by team member presents the tasks grouped by team member for a single project; and

the Gantt chart organized by project presents the tasks grouped by team member to whom the tasks are assigned for one or more projects.