Agile Schedule Development

Deliverable Length:  400-600 words 

Now that you have completed your stakeholder analysis and developed the stakeholder register, project charter, SOW (scope document), and your WBS, it is time to start building your project schedule baseline. 

Schedule Baseline. The approved version of a schedule model that can be changed using formal change control procedures and is used as the basis for comparison to actual results.

Project Schedule. An output of a schedule model that presents linked activities with planned dates, durations, milestones, and resources.

These definitions are taken from the Glossary of Project Management Institute, A Guide to the Project Management Body of Knowledge, (PMBOK® Guide) – Sixth Edition, Project Management Institute Inc., 2017.

The project schedule should include start and finish dates for all activities. Remember, if an activity is not in the schedule, it will not be done. Establishing the schedule will allow you to estimate activity cost, and thus help you develop a budget. Therefore, a schedule helps you establish a time and a cost baseline for your project.

• Discuss how you would go about      assigning or completing the schedule elements, such as dates, durations,      milestones, predecessors, and resources. 
• How would you go about      completing resource assignments, both human and material? How would you      determine to buy (acquire) or make your resources? 
• Discuss the importance of      building slack in your project schedule. 
• Once your schedule is fully      developed, what information would any of your stakeholders learn from it? 
• Looking back at the      agile versus waterfall methodologies, how does this traditional      schedule development differ from agile schedule development?