Datasheet

MSF MSF features iterative development that reacts well to change. Requirements are
locked at the beginning of a release but can be added in subsequent releases. Major and
minor releases can be scheduled based on new requirements.
Scrum Scrum assumes that features will be added to the product backlog after work
begins. Because change is expected, it has less of a ripple effect throughout the system.
Instead of change orders, additional sprints or releases are added to the schedule to
implement new features.
Scheduling
What is the basis for scheduling features or people? When will you know if the project is slipping?
The three project management methodologies address scheduling as follows:
Waterfall Scheduling is predictive. Using a known team and known technology, an
experienced team can predict the duration of each phase and task. This method doesn t
respond well to slippage, as dependencies among tasks and phases are often very complex.
MSF Scheduling is predictive, as in the Waterfall method. However, because MSF is
iterative, with more frequent releases, schedule slippage is more manageable. Subsequent
releases can add or remove features to react to prior impact.
Scrum Scheduling is empirical. Work is scheduled based on the Scrum team s velocity.
Estimation becomes more accurate with each successive sprint, based on actual work
completed. Scheduling is very reliable because of the fi xed - duration sprints. The scope is
less reliable because features will move in and out of sprints and releases to accommodate
the xed schedule.
People
How are teams organized? When are people added to and removed from projects? The three project
management methodologies address people as follows:
Waterfall Specialized teams work on different phases of the project. Business analysts
perform the requirements defi nition work early, often before technical experts have been
assigned to the project. Once development begins, business analysts have a reduced role.
Testing begins after development completes. Project management is a specialized role, often
staffed by a project management of ce.
MSF Specialized teams work on different aspects of the project but all at the same time.
Roles are clearly defi ned and cover the full spectrum of what s necessary to build and ship
products in a predicable manner. The project is run by a team of peers, with each discipline
contributing to each phase.
Scrum A single team is involved throughout the project life cycle. Within the team, just
three roles are defi ned. The work is very collaborative within and across roles. The team is
self - organizing, and team members have full visibility into the product backlog and commit
to completing scope. The team is involved in planning, estimating, developing, and testing.
The team remains customer focused throughout the project.
Comparing Methodologies
21
CH001.indd 21CH001.indd 21 3/23/11 2:47:10 PM3/23/11 2:47:10 PM