
Project Goal: To build an information management system that will allow the user to communicate with other users, schedule events, manage registration for events and post comments related to the events.
Overall Project Tasks:
Task ID | Task Name |
1 | Construct Test Environment (Architecture) |
2 | Construct Production Environment (Architecture) |
3 | Construct Test Environment (Software) |
3a | Construct Registration Module |
3b | Construct Scheduling Module |
3c | Construct Communications Module |
3d | Test Registration Module |
3e | Test Scheduling Module |
3f | Test Communications Module |
4 | Migrate to Production |
5 | Announce Launch |
Project PERT Network Chart:
This network diagram demonstrates the project as 13 weeks in length. Tasks 2, 3 and 5 create the critical path.
Sprint 1 – PERT Network Chart:
This network diagram demonstrates this sprint as 4 weeks in length. Tasks 3b and 3e are the critical path.
Sprint 2 – PERT Network Chart:
This network diagram demonstrates this sprint as 4 weeks in length. Tasks 3a and 4 are the critical path.
This simple example helps demonstrate how the scrum master can define the critical path of the overall project as well as for each sprint. By defining each sprints critical path, the scrum master can ensure that the appropriate resources are working each task. Focusing on those critical path tasks allows the scrum master to prioritize impediment management, scope changes, issues and risks impacting critical path tasks on a sprint by sprint basis.
No comments:
Post a Comment