<< Chapter 13: The Whole and the Parts
Milestones or Millstones
The first step to keeping a schedule is to actually have a schedule.
When designing a schedule, you’ll obviously need milestones. The milestones must be concrete, specific, measurable events. Don’t choose vague tasks like “coding” or “designing”, because coding is always 90% finished, and debugging is always 99% done. Pick concrete milestones that are 100% events. Ex. “debugged version of build passed all test cases”, or “specs signed by architect and implementers”
[TMMM] Ch 15 – The Other Face
<< Ch. 14 – Hatching a Catastrophe
It is not enough to just talk about documentation, the “masters” need to show the kids how to do it!
Read More »