Showing posts with label project schedule control. Show all posts
Showing posts with label project schedule control. Show all posts

Saturday, December 17, 2011

Chapter 27: Time Management during Monitoring & Controlling the Project


Aim: To understand the Control Schedule Process

After the project enters the executing phase, work is performed to produce the project’s deliverables. All work should be performed according to the project schedule, budget, and quality standards. But does it happen that way all the time? Unfortunately No. As Project Manager, we must closely monitor these constraints to ensure that the project progresses as planned and adheres to the scope/time/cost baselines decided during the Planning Phase.

Manage the Project Schedule

The control schedule process helps the project manager to ensure that project work is being carried out according to the planned schedule.

The table below shows the inputs, tools and techniques, and outputs for the control schedule process.

Control Schedule
Inputs Tools & Techniques Outputs

Project management plan
Project schedule updates
Work performance information
Organizational process assets

Performance reviews
Variance analysis
Project management software
Resource leveling
What-if scenario analysis
Adjusting leads and lags
Schedule compression
Scheduling tool

Work performance measurements
Organizational process assets
Change requests
Project management plan updates
Project document updates
The control schedule process identifies any deviations from the project schedule. What happens if work is falling behind? Your recourse is to implement corrective or preventive actions or a change request to align the project execution with its expected results and timelines.

Exam Trivia:
A corrective or preventive action is an action that is implemented to bring future project events and tasks into alignment with the project plan and its baseline.

Some options available at this time could be to
• Update the project baseline to reflect the current situation using the documented change process.
• Level resources. When possible, reassign over-allocated resources to avoid schedule conflicts.
• Crash the schedule. Add people (internal/external) or resources to the tasks that have fallen behind and have a direct effect on the critical path; the down side is that this might cause unscheduled expenses.
• Fast track. Rearrange your activities to perform activities in parallel.
• Outsource the project or the affected part.
• Reduce the scope of the project.

Exam Trivia:
Reducing the Project Scope should be the last resort measure only. As the manager you must exhaust all other possibilities to bring the project schedule back on track and if all measures fail, then we must use Scope Reduction. Do remember that you are likely to face significant heat from both your management as well as the customer if you suggest scope reduction.

To know more about the Control Schedule process Click Here

Prev: Chapter 26

Next: Chapter 28

Friday, July 8, 2011

Chapter 85: Controlling Schedule

Schedule control has a two-pronged goal; to ensure that the project is progressing on time as planned and to monitor any changes to this progress. As a project manager, you should be out in front of the project, performing the following tasks on a regular basis:
• Determining the current status of the project schedule
• Influencing the factors that generate schedule changes
• Determining whether the project schedule has changed. For ex: if some activities are running late
• Managing changes as they occur

You detect a schedule change by comparing the execution time to the time in the schedule baseline, which is a major input item into the schedule control process. This is formally called Control Schedule.

The picture below explains the Control Schedule Process:


Input to Schedule Control

To control the project schedule, you need to know what the schedule baseline (that is, the expectation) is, how the project is performing from the perspective of schedule, and what the plans are to monitor the schedule. The complete list is:
• Schedule management plan - This plan specifies how to monitor and control the project at hand.
• Schedule baseline - This is the approved version of the schedule, against which the schedule performance of the project will be measured.
• Performance reports - These reports provide information on the schedule performance of the project, such as missed and met planned dates.
• Approved change requests - These are requests to change the schedule or other change requests that will affect the schedule. Approved change requests can update the schedule baseline.

Tools and Techniques for Schedule Control

The schedule is monitored by progress reporting and performance measurements and is controlled using the schedule control system.

Progress reporting - Progress reports and current schedule status are key items to monitor the schedule. They can include finished activities, the percent of in-progress activities that have been completed, and remaining durations for unfinished activities.

Schedule change control system - This is the system you use to receive, evaluate, and process schedule changes. It can include forms, procedures, approval committees, and tracking systems.

Performance measurement and analysis - The following tools and techniques can be used to measure and analyze the schedule performance of the project:
• Performance measurement techniques - These techniques are used to calculate the schedule variance and schedule performance index. The schedule variance discussed there is in terms of cost, but you can also perform a barebones schedule variance analysis based on the start and end dates of the schedule activities.
• Variance analysis - Performing a barebones schedule variance analysis is crucial to schedule monitoring because it reveals the deviation of the actual start and finish dates from the planned start and finish dates of schedule activities. It might suggest corrective actions to be taken to keep the project on the track.
• Schedule comparison bar charts - Bar charts can be used to facilitate the schedule variance analysis. You can draw two bars corresponding to one schedule activity, one bar shows the actual progress, and the other bar shows the expected progress according to the baseline. This is a great tool to visually display where the schedule has progressed as planned and where it has slipped.

Project management software - You can use project management software for scheduling to track planned start/finish dates versus actual dates for schedule activities. This software also enables you to predict the effects of project schedule changes. These are important pieces of information for monitoring and controlling the schedule.

Output of Schedule Control

Schedule performance measurements and recommendations for actions based on the measurements and progress reports are the important output items of the schedule control process.

Performance measurements - The results from schedule performance measurements, such as the schedule variance (SV) and schedule performance index (SPI), should be documented and communicated to stakeholders. These measurements might trigger recommendations for corrective actions and change requests.

Recommended corrective actions - The goal of schedule-related corrective actions is to bring the future schedule performance in line with the schedule baseline—that is, the approved version of the planned schedule. To achieve that, the following actions can be taken:
• Expedite the execution to ensure that schedule activities are completed on time or with minimal delay.
• Perform a root cause analysis to identify the causes of the schedule variance.
• Make plans to recover from the schedule delay.

Updates - The following updates can result from the schedule control process:
• Schedule updates - Schedule changes can happen at the activity level (the start/end date of an activity has changed) or at the project level (the start/end date of the project has changed). A schedule change at the project level is called a schedule revision. For example, when the project scope is expanded, the project end date might have to be changed to allow the extra work. All significant schedule changes must be reported to the stakeholders.
• Activity updates - The schedule changes and the project progress will cause changes in the activity list and in the list of activity attributes. These changes must be documented.
• Project management plan - The schedule management plan, a component of the project management plan, is updated to reflect the changes that occur during the schedule control process.
• Organizational process assets - The lessons learned from the schedule control process can be documented to the historical database. Examples are:
o The causes of schedule variance
o The reasons for choosing the corrective actions that were taken
o The effectiveness of the corrective actions
Future projects can make use of this information.

Change requests - The schedule performance analysis and progress report review can result in requests for changes to the project schedule baseline. These changes must be processed through the integrated change control process for approval. As with any other change, you must think through whether a change to the schedule baseline has any other effect across the project. If it does, you might need to update the corresponding component of the project management plan accordingly.

Prev: Controlling Scope

Next: Controlling Cost
© 2013 by www.getpmpcertified.blogspot.com. All rights reserved. No part of this blog or its contents may be reproduced or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written permission of the Author.

Followers

Popular Posts