|
6.5 Develop Schedule The process of creating a schedule from analysing the activity sequences, durations, resource requirements and schedule constraints. Simple Version: Determine how long the project will take. An iterative process that continues throughout the project as work progresses. | |
|
PMI |
Agile PMBOK, Agile Difference, Comment |
|
Inputs Activity list Activity attributes Project schedule network diagrams Activity resource requirements Resource calendars Activity duration estimates Project scope statement Organizational process assets Tools and Techniques Schedule network analysis Critical path method Critical chain method Resource levelling What-if scenario analysis Applying leads and lags Schedule compression Scheduling tool Outputs Project schedule Schedule baseline Schedule data Project document updates |
Inputs Activity list / Feature List / Story Backlog Activity attributes / Story metadata (priority, dependencies, etc) Project schedule network diagrams / Feature Groups Activity resource requirements Resource calendars Activity duration estimates / Story Estimates Project scope statement Organizational process assets Tools and Techniques Schedule network analysis Critical path method Critical chain method Resource levelling What-if scenario analysis Applying leads and lags Schedule compression Scheduling tool Release and iteration Planning Outputs Project schedule Schedule baseline Schedule data Project document updates Agile projects still need Schedules and Plans. They may change, driven by business requests, or project feedback; but plans need to exist. The format of agile plans may surprise some stakeholders. Instead of a network diagram, a prioritised backlog may be the preferred tool for illustrating and managing the sequence of project activities. Tools and deliverables that are easy to change (refactor) are preferred over harder to maintain network diagrams and WBS diagrams. |
6.5 Develop Schedule