« Punchlist for a “483” – Worm Sorting | Main | Punchlist for a “483” – Prototype Review »

Punchlist for a “483” – Worm Detector

The Incident Reporting System was moving along well. We had just concluded a review of the Database design and the screen prototypes, with a successful outcome. But in a critical error, I forgot to scan the emerging design with my “worm detector”.

“Can of Worms” [n] ( informal ) a source of unpredictable trouble and complexity .

To open a can of worms in an IT project is to find an unexpected mess. I have always prided myself on my ability to anticipate where the worms are hiding, and to manage accordingly. But I missed the can of worms residing in the reporting requirements.

IT project management is all about managing risk, and you can’t manage the risk if you aren’t aware of it. Thus, the Worm Detector is a valuable tool in the PM’s toolbox. As in many other things, early detection and action is the key.

Find that can of worms, open it up, pull them all out, and sort them out by Size and Shape. Inspect each for a pulse. Separate out the dead ones, and store them in the Issues List as Resolved. Most cans of worms contain a high proportion of dead worms. These can be old problems no longer current; opinions not problems; things resolved but never documented; or undefined areas that have been “severed” with the scope axe.

But worms that you thought were dead have an annoying property of spontaneously re-animating themselves. The Issue List with the Resolution column completed is the tombstone that keeps a dead worm dead. And often, just an energetic cycle of identifying and documenting the worms, alive or dead, makes everyone feel better.

Back to the project: My can of worms here was the reporting requirements. I didn’t think to scan this area with my worm detector, because the reporting portion of the system is usually not a hiding place for worms. In the Modern Era (that’s after “banded” report writers like Crystal Reports arrived), report generation has not been a problem. The tools are so powerful and easy to use that 95% of needed reports can be laid out in the “WYSIWYG” (what you see is what you get”) tool in an hour or two each.

So what was the problem with the reporting in this project? To quote scripture: ““Legion,” he replied, for they were many.” – Luke 8:30.

Posted on Saturday, January 7, 2006 at 10:43PM by Registered CommenterLarry Cone in , | CommentsPost a Comment

PrintView Printer Friendly Version

EmailEmail Article to Friend

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
All HTML will be escaped. Hyperlinks will be created for URLs automatically.