Page 213 -

6 - PROJECT TIME MANAGEMENT

If any agile approach is utilized, control schedule is concerned with:

• 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 retrospective reviews (scheduled reviews to record lessons learned) 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 given
time per iteration (agreed work cycle duration, typically two weeks or one month), 6

• Determining that the project schedule has changed, and
• Managing the actual changes as they occur.

6.7.1 control Schedule: Inputs

6.7.1.1 Project Management Plan

Described in Section 4.2.3.1. The project management plan contains the schedule management plan and the
schedule baseline. The schedule management plan describes how the schedule will be managed and controlled.
The schedule baseline is used as a reference to compare with actual results to determine if a change, corrective
action, or preventive action is necessary.

6.7.1.2 Project Schedule

Described in Section 6.6.3.2. Project schedule refers to the most recent version with notations to indicate
updates, completed activities, and started activities as of the indicated data date.

6.7.1.3 Work Performance data

Described in Section 4.3.3.2. Work performance data refers to information about project progress such as which
activities have started, their progress (e.g., actual duration, remaining duration, and physical percent complete),
and which activities have finished.

©2013 Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK Guide) – Fifth Edition 187
®

Licensed To: Jorge Diego Fuentes Sanchez PMI MemberID: 2399412
This copy is a PMI Member benefit, not for distribution, sale, or reproduction.