This premise is so far off from the way we typically learn to develop software that many people dismiss
it as a delusional fantasy. ???These XP folks obviously don??™t know what they??™re talking about,??? they say.
???Just last month I was on a project that failed due to inadequate requirements and design. We need
more requirements, design, and testing, not less!???
That??™s true. Software projects do need more requirements, design, and testing??”which is why XP teams
work on these activities every day. Yes, every day.
You see, XP emphasizes face-to-face collaboration. This is so effective in eliminating communication
delays and misunderstandings that the team no longer needs distinct phases. This allows them to work
on all activities every day??”with simultaneous phases??”as shown in Figure 3-2.
Using simultanous phases, an XP team produces deployable software every week. In each iteration, the
team analyzes, designs, codes, tests, and deploys a subset of features.
Although this approach doesn??™t necessarily mean that the team is more productive,* it does mean that
the team gets feedback much more frequently. As a result, the team can easily connect successes and
failures to their underlying causes.
Pages:
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56