HYBRID PROJECT 1
Peloton Bike App
We were given specific constraints and had to determine which agile or waterfall characteristics worked best for the project, keeping the constraints in mind. Because our scope, features, teams, and timeline were pre-determined, I chose a waterfall structure with mostly agile characteristics.
SCOPE PLAN OUTLINE
You’ll see waterfall components in the planning structure and agile framework in the development phases of the project.
I chose this combination because leadership wanted weekly status updates from the project manager in addition to demos from the scrum team at the end of every increment. Teams were to test individual features in development, with the integration of all 4 epics + production teams at the end of development.
WORK BREAKDOWN STRUCTURE (WBS)
A WBS was important to communicate simultaneous sprints between two scrum teams and features being developed.
CHANGE CONTROL PROCESS- INFORMAL/ CHANGE LOG
A mix of waterfall and agile change control processes was chosen because of the fixed timeline and requirements outlined in the project scope. The requirements will not change unless approved by key stakeholders. In that case, the Product Owner would put it in the product backlog to be pulled into future sprints, depending on the priority.
I chose to keep the change process informal, but record changes in a change log to manage requirements. keep all stakeholders informed, and prevent scope creep.
TRACKING KPI'S- BURNUP/ BURNDOWN
Scrum Masters will create individual team burndown charts for each sprint
Burnup chart for both scrum teams to track progress
PM’s will refer to charts to update the project schedule and inform key stakeholders on project status and timeline to completion