Datasheet

8
❘
CHAPTER 1 SHIPPING SOFTWARE
Figure 1 - 2 shows a Gantt chart from a project
planned using the Waterfall method. Note that
each task is scheduled with a known duration.
If a task completes early or late, this will impact
all other tasks in the release. This works well
if you have a high degree of confi dence in your
task estimates, but it falls apart quickly if the
estimates are incorrect.
In a Scrum project, you must plan tasks.
Software project management requires a lot of
planning, and Scrum doesn ’ t change that need.
However, rather than plan tasks to manage
dependencies, you plan tasks to manage feature
delivery. The team focuses on building the
product rather than keeping to the schedule. The
schedule in Scrum is simple: It ’ s the sprint cycle.
Planning within a sprint focuses on the product
rather than the schedule because the schedule is so simple. Figure 1 - 3 shows a project artifact that
you ’ ll use for intra - sprint planning. This report, and many others like it, is covered in Chapter 6.
FIGURE 1 - 2: Waterfall method Gantt chart.
FIGURE 1 - 3: A Scrum project artifact.
CH001.indd 8CH001.indd 8 3/23/11 2:46:33 PM3/23/11 2:46:33 PM