December 2004 - Posts
If the schedule is in increments longer than a week (five work days), per person, the schedule is not detailed enough. Letting people run without a schedule checkpoint weekly is risking their being off by as much as a week. Compound that by all the people
Read More...
A warning sign of a bogus schedule is magic dates. Such dates tend be in two forms, the “when do you need it” form, and the “would you look at that” form. The “when do you need it” form of magic date is the schedule date that miraculously meets the date
Read More...
One of the more reliable predictors of the health of a project can be to determine where the schedule came from. If the schedule came from anywhere other than the people who will actually do the work (with appropriate buffering applied), it is wrong.
Read More...
Jane Huxley - one of the funnest people i've worked with at MS is bailing. She was top of my list of the people who never moved to the US who would have done super well here if she had. My best memories of working with Jane are probably now for writing
Read More...
A friend of mine, who shall remain nameless, (to keep him anonymous lets just refer to him as Christian Kline of Seattle, WA) has a really cool photo blog http://www.scrapofpaper.com/blog/impermanence.html he will hate me for pointing people at his site
Read More...
Missing the finer points of process control Few teams truly handle all aspects of their process well. This is not a fatal flaw, but it can be used as an indicator of the maturity of the development team. There are many fine points that should not be overlooked.
Read More...
