Two important parts of the activities related to time schedule planning for a project, are creating the work breakdown structure and the time interrelationships of start and finish of these tasks. Later, when using the same time schedule to monitor the progress of the project, we look at how these times might have changed and how to ensure the final project outcome is achieved. Right from the start then, we have to keep the final outcome in sharp focus; first to determine the path to undertake, the sequence of tasks to be completed to reach this outcome, second as a milestone to measure the progress against.

The Destination Determines How to Get There

Things change and that’s a reality of life. So you can be absolutely certain changes are going to happen. Controlling the changes and to make sure the time schedule does not run away is another aspect of the time schedule management. But that is not something we are going to discuss here now. Though we know things could and would change, we still need to start with as clear a outcome definition as possible. A complete set of blueprints in case of a construction project, or a requirements document along with specified use cases in case of a software project could provide this target definition. We can easily visualize here that the definition of the target or the product being built determines what steps/tasks are to be completed to reach this goal. What is to be built also determines what technologies are to be used. The technology to be used will affect the tasks that we need to define for accomplishing the goal.

Breaking down the tasks and determining how they influence the outcome is an iterative process. Initially you may start with simply the tasks required to build the major subsystems of the project. As you refine the breakdown, lot of detailed tasks would appear. What exact tasks you would undertake and the time estimate for completion of the task would depend on the implementation technology chosen. What tasks can be carried out in parallel also would emerge out of this work breakdown exercise.

Desired Outcome Determines What Progress is Being Made

As you progress through the project you need to monitor how well you are travelling towards the destination. If there are delays and slips in completing some activities you need to react as soon as possible and take corrective action. Clearly how effective these actions would be, are determined by how well the outcome is defined. When as many characterization of the outcome as possible are known, it is that much easier to determine how close or away you are from reaching that outcome. The more dimensions one can attach to a item, the more precise is its definition and thus it is as much well-known and understood.

One can try and define this outcome down to the task levels too. Well defined outcomes and success criteria (discussed in another section) will make it easy to determine, objectively, the progress of a project at the task levels and thus the overall progress of the project.

Two important parts of the activities related to time schedule planning for a project, are creating the work breakdown structure and the time interrelationships of start and finish of these tasks. Later, when using the same time schedule to monitor the progress of the project, we look at how these times might have changed and how to ensure the final project outcome is achieved. Right from the start then, we have to keep the final outcome in sharp focus; first to determine the path to undertake, the sequence of tasks to be completed to reach this outcome, second as a milestone to measure the progress against.

The Destination Determines How to Get There

Things change and that’s a reality of life. So you can be absolutely certain changes are going to happen. Controlling the changes and to make sure the time schedule does not run away is another aspect of the time schedule management. But that is not something we are going to discuss here now. Though we know things could and would change, we still need to start with as clear a outcome definition as possible. A complete set of blueprints in case of a construction project, or a requirements document along with specified use cases in case of a software project could provide this target definition. We can easily visualize here that the definition of the target or the product being built determines what steps/tasks are to be completed to reach this goal. What is to be built also determines what technologies are to be used. The technology to be used will affect the tasks that we need to define for accomplishing the goal.

Breaking down the tasks and determining how they influence the outcome is an iterative process. Initially you may start with simply the tasks required to build the major subsystems of the project. As you refine the breakdown, lot of detailed tasks would appear. What exact tasks you would undertake and the time estimate for completion of the task would depend on the implementation technology chosen. What tasks can be carried out in parallel also would emerge out of this work breakdown exercise.

Desired Outcome Determines What Progress is Being Made

As you progress through the project you need to monitor how well you are travelling towards the destination. If there are delays and slips in completing some activities you need to react as soon as possible and take corrective action. Clearly how effective these actions would be, are determined by how well the outcome is defined. When as many characterization of the outcome as possible are known, it is that much easier to determine how close or away you are from reaching that outcome. The more dimensions one can attach to a item, the more precise is its definition and thus it is as much well-known and understood.

One can try and define this outcome down to the task levels too. Well defined outcomes and success criteria (discussed in another section) will make it easy to determine, objectively, the progress of a project at the task levels and thus the overall progress of the project.

Project Outcome

August 2, 2009
By

Two important parts of the activities related to time schedule planning for a project, are creating the work breakdown structure and the time interrelationships of start and finish of these tasks. Later, when using the same time schedule to monitor the progress of the project, we look at how these times might have changed and how to ensure the final project outcome is achieved. Right from the start then, we have to keep the final outcome in sharp focus; first to determine the path to undertake, the sequence of tasks to be completed to reach this outcome, second as a milestone to measure the progress against.

The Destination Determines How to Get There

Things change and that’s a reality of life. So you can be absolutely certain changes are going to happen. Controlling the changes and to make sure the time schedule does not run away is another aspect of the time schedule management. But that is not something we are going to discuss here now. Though we know things could and would change, we still need to start with as clear a outcome definition as possible. A complete set of blueprints in case of a construction project, or a requirements document along with specified use cases in case of a software project could provide this target definition. We can easily visualize here that the definition of the target or the product being built determines what steps/tasks are to be completed to reach this goal. What is to be built also determines what technologies are to be used. The technology to be used will affect the tasks that we need to define for accomplishing the goal.

Breaking down the tasks and determining how they influence the outcome is an iterative process. Initially you may start with simply the tasks required to build the major subsystems of the project. As you refine the breakdown, lot of detailed tasks would appear. What exact tasks you would undertake and the time estimate for completion of the task would depend on the implementation technology chosen. What tasks can be carried out in parallel also would emerge out of this work breakdown exercise.

Desired Outcome Determines What Progress is Being Made

As you progress through the project you need to monitor how well you are travelling towards the destination. If there are delays and slips in completing some activities you need to react as soon as possible and take corrective action. Clearly how effective these actions would be, are determined by how well the outcome is defined. When as many characterization of the outcome as possible are known, it is that much easier to determine how close or away you are from reaching that outcome. The more dimensions one can attach to a item, the more precise is its definition and thus it is as much well-known and understood.

One can try and define this outcome down to the task levels too. Well defined outcomes and success criteria (discussed in another section) will make it easy to determine, objectively, the progress of a project at the task levels and thus the overall progress of the project.

Popularity: 3% [?]

Tags:

3 Responses to Project Outcome

  1. diamond rings on August 2, 2009 at 3:22 pm

    Here a wealth of information here. Thanks! I’ll be back for more

  2. babafisa on August 3, 2009 at 6:31 am

    Thank you for this valuable post. It changed my mindThank you for this valuable post. It changed my attitude

  3. hotspotshield on August 3, 2009 at 4:37 pm

    This is the second entry I read tonight. And I am on my third. Got to think which one is next. Thank you.

Leave a Reply

Your email address will not be published. Required fields are marked *