Fletcher Dunton

Series:Axioms for Good IT Process

I was recently asked by a client to help them evaluate their current IT process. As I browsed their existing  policy, project notebooks and other artifacts I came to realize just how deceived and misinformed (these) folks were about what “good IT process“ is and is not. 

In fact, some of the comments I received back from both management and developers ranged from “I just hate (any) process” to “Should I go to CMM training?”  (I just love that one) and “We can't afford to have a process.“ (well “boo-hoo-hoo”).  And these were highly paid professionals.

Look, we've all had the displeasure of working on projects that have no requirements, plan or direction. And conversely, many of us have worked for shops that have so much process that one must fill out a leave slip just to take a break for a call to nature!  To the extreme, each of these environments are highly ineffective and introduces risk ($$$), both to the system under development and our collective livelihood.  Surely, there has to middle ground.  There must be way. 

Ah-hah: I see I’ve piqued your interest.  Over the next few weeks, I’ll be expanding on “Axioms for Good IT process”, including the following

1.       “Its not that you have a process, rather it’s what process you have.”

4.       It’s not that you can’t afford to have a process, it’s that you can’t afford NOT to have GOOD process.

5.       Eventually, the Sarbanes-Oxley Act (http://www.sarbanes-oxley.com) will affect you and your IT Shop and the integrity with which each project’s artifacts are maintained.

Listen, your process is not static. It must evolve over time. And it is a living reflection of you and your firm.

I welcome your feedback. By the way, you know that Mom and Pop Shop that just opened down the street? Well they're CMM Level 5.