It is the process of monitoring the status of the project to update the project schedule and managing changes to the schedule baseline.
The key benefit: the schedule baseline is maintained throughout the project.
Frequency: throughout the project.
The process concerns with:
For agile approach:
For contractual work the milestones are controlled. Scheduled status reviews and walkthroughs should be done to verify the contractor reports.
Includes:
Include:
6.6.
Include:
Includes:
Progress along the critical path -> schedule status.
Track planned dates versus actual dates.
Adjusting leads and lags to find way to bring project activities into alignment with the plan.
Schedule variance analysis/progress reports reviews/performance measures/modification of the project scope/modification of project schedule => change requests.
Includes:
Include:
The key benefit: the schedule baseline is maintained throughout the project.
Frequency: throughout the project.
Process/ Assets Group | Input | The process | Output | Process / Assets Group |
---|---|---|---|---|
Project Management Plan | Schedule management plan | 6.6 Control Schedule | Work performance information | 4.5 Monitor and Control Project Work |
Schedule baseline | Change Request | 4.6 Perform Integrated Change Control | ||
Scope baseline | Schedule management plan | Project Management Plan | ||
Performance measurement baseline | Schedule baseline | |||
Project Documents | Lesson learned register | Cost baseline | ||
Project calendars | Performance measurement baseline | |||
Project schedule | Schedule forecast | Project Documents | ||
Resource calendars | Assumption log | |||
Schedule data | Basis of estimates | |||
4.3 Direct and Manage Project Work | Work performance data | Lesson learned register | ||
Enterprise / Organization | Organizational process assets | Project schedule | ||
Resource calendars | ||||
Risk register | ||||
Schedule data |
The process concerns with:
- Determining the current status of the project schedule,
- Influencing the factors that create schedule changes,
- Reconsidering necessary schedule reserves,
- Determining if the project schedule has changed,
- Managing the actual changes as they occur.
For agile approach:
- Determining the current status of the project schedule by comparing the total amount of work delivered and accepted against the estimates of work completed for the elapsed time cycle;
- Conducting retrospectives for correcting processes and improving, if required;
- Reprioritizing the remaining work plan (backlog);
- Determining the rate at which the deliverables are produced, validated, and accepted (velocity) in the given time per iteration;
- Determining that the project schedule has changed;
- Managing the actual changes as they occur.
For contractual work the milestones are controlled. Scheduled status reviews and walkthroughs should be done to verify the contractor reports.
6.6.1 Inputs
6.6.1.1 Project Management Plan
Includes:
- Schedule management plan. Frequency to update, reserve usage, how to control;
- Schedule baseline. To compare actual with baseline.
- Scope baseline.
- Performance measurement baseline.
6.6.1.2 Project Documents
Include:
- Lesson learned register.
- Project calendars.
- Project schedule.
- Resource calendars.
- Schedule data.
6.6.1.3 Work Performance Data
- Started activities;
- Actual duration;
- Remaining duration;
- Physical percent complete;
- Completed activities.
6.6.
6.6.1.4 Organizational Process Assets
Include:
- Existing formal/informal schedule control-related policies, procedures, guidelines;
- Schedule control tools;
- Monitoring and reporting methods to be used.
6.6.2 Tools and Techniques
6.6.2.1 Data Analysis
Includes:
- Earned value analysis. To assess the magnitude of variation to the original schedule baseline;
- Iteration burndown chart. To track the work remaining to be completed in the iteration backlog. Variance with an ideal burndown (diagonal line) is analyzed. A forecast trend line is used to predict the likely variance at iteration completion.
- Performance reviews. To measure, compare, analyze schedule performance against the baseline: actual start and finish dates, percent complete, remaining duration for work in progress.
- Trend analysis. To analyze performance over time.
- Variance analysis. Analysis of variances in planned values versus actual for start/finish dates, duration, float. Also cause, degree, future implications.
- What-if scenario analysis.
6.6.2.2 Critical Path Method
Progress along the critical path -> schedule status.
6.6.2.3 Project Management Information System (PMIS)
Track planned dates versus actual dates.
6.6.2.4 Resource Optimization
6.6.2.5 Leads and Lags
Adjusting leads and lags to find way to bring project activities into alignment with the plan.
6.6.2.6 Schedule Compression
6.6.3 Outputs
6.6.3.1 Work Performance Information
6.6.3.2 Schedule Forecasts
- Earned value performance indicators,
- Schedule reserve information.
6.6.3.3 Change Requests
Schedule variance analysis/progress reports reviews/performance measures/modification of the project scope/modification of project schedule => change requests.
6.6.3.4 Project Management Plan Updates
Includes:
- Schedule management plan.
- Schedule baseline. Changes in project scope, resources, activity duration, results of schedule compression, performance issues.
- Cost baseline.
- Performance measurement baseline.
6.6.3.5 Project Documents Updates
Include:
- Assumption log.
- Basis of estimates.
- Lesson learned register.
- Project schedule.
- Resource calendars.
- Risk register.
- Schedule data.
Комментариев нет:
Отправить комментарий