We need to make sure that they are all captured and then
processed as outlined earlier in this chapter. If we use tasks correctly then the
developers will always know what they personally have left to do, and likewise our
project leader will know what is left to be done to reach the next release. By using
the task information to create and update our roadmap??”a concept we will look at in
greater detail later??”everyone will always be able to determine where we are going.
Sandboxes Aren't Just for Children
Now that our "development support system" is set up, our developers know how
to use it, and our tasks are being managed, we can finally write some code! We can
save ourselves a significant amount of effort by developing in isolation. This means
keeping our work separate from other developers' work until it is ready??”features
and bug fixes are developed away from the main code, and only integrated when
complete. This means that:
We are developing against a known base, not a constantly changing one.
We are responsible for making sure our code integrates with the rest; if
another developer integrates their bug fix before we integrate our new
feature, the blame can only lie with ourselves if our code doesn't work or we
break something the other developer fixed.
Pages:
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34