There are no
questions about which features to work on, how things ought to work, if the software works correctly,
or whether stakeholders are happy. All the answers are right there in one brain.
Team software development is different. The same information is spread out among many members of
the team. Different people know:
??? How to design and program the software (programmers, designers, and architects)
??? Why the software is important (product manager)
T H E X P T E A M 27
??? The rules the software should follow (domain experts)
??? How the software should behave (interaction designers)
??? How the user interface should look (graphic designers)
??? Where defects are likely to hide (testers)
??? How to interact with the rest of the company (project manager)
??? Where to improve work habits (coach)
All of this knowledge is necessary for success. XP acknowledges this reality by creating cross-functional
teams composed of diverse people who can fulfill all the team??™s roles.
The Whole Team
XP teams sit together in an open workspace. At the beginning of each iteration, the team meets for a
series of activities: an iteration demo, a retrospective, and iteration planning.
Pages:
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73