I recently ran across this blog on The Power of Checklists by Ivar Jacobson. In it he describes the value of using checklists on software projects since they: “keep software projects on track,
and help maximize the delivery of value, and minimize the risk of project failure.” OUM practitioners know this since the method contains checklists in many places - templates, phase overviews, activities, tasks, etc. In fact, the WBS itself could be considered a checklist since the activities and tasks are merely “placeholders for work.”
The OUM checklists which I find particularly valuable are the Activity Checklists found in each of the Lifecycle Milestone Summaries. These checklists are designed to assist you with the determining “completeness” of the project at that point. They also contain lists of key decisions and common risks that should be addressed during that particular phase of the project – kind of like a “you are here” checkpoint for the project's progress.
I think Ivar would agree with me about the value of the OUM Activity Checklists since he is a fan of Barry Boehm’s standard project milestones. You can read more about Barry
Boehm’s standard project milestones in his seminal work – “Anchoring the Software Process” [Barry Boehm, November 1995].
Which OUM checklists do you find to be of the most value? Please share your opinion in the comments.