I am interestedly watching the public discussion on the new healthcare system (and web site). I have been responsible for a good number of software development projects in my career…and few are able to move as quickly as we would aspire.
In this article, the white house chief of staff gets daily updates on the web site repair process. I confess that I laughed out loud…because few projects move fast enough to warrant a useful daily status report, no matter how many people are working on it. In fact, the larger the project the slower the progress (because of the high amount of coordination needed).
The purpose of a daily status report is usually limited to reduce everyone’s sense of anxiety. But, it is rarely helpful to advance the project any faster. Therefore, what information should we provide our leaders about our progress?
- At any time that the schedule, budget, or deliverables become jeopardized, it’s time to raise our hand and speak up
- Once a breakdown is identified and communicated up the chain of command, we should provide a fresh report whenever progress is made
- If progress is not being made, an update should be given at least weekly
- At any time the schedule, budget, or deliverables are renegotiated, our leaders should be notified as soon as possible
Thanks for listening.