Tuesday, October 30, 2007


Enterprise Architecture and Process Justification

What is the reason to have processes in the first place? More exactly what is the reason to have a heavyweight process...

Not a week goes by when I don't have a reason to be in Home Depot. Yesterday, I had to run in and get bulbs for the Kitchen when I ran across a process weenie from my past who was talking about leveraging the experience of their Indian outsourcing partner and their love of CMM. Since we were in the lumber aisle, I gradually moved away from those nice sturdy 2x4s.

The benefit of formal process models is the sharing of information about things that work, and things that don't work. Everyone who decides to "buy in" to a process needs to accept the responsibility of evaluating that process in relation to their own work. It's certainly true that following the rules of a formal process without understanding it or thinking about it can lead to bad outcomes.

Besides, everything has a process. It just doesn't need to be a heavy process, and fully described by methodologists. In India, the ability to scale the revenues by leveraging a large population requires use of process as a substitute for competence but in America where we have an age problem, it is better to prefer something more lightweight...

<< Home
| | View blog reactions

This page is powered by Blogger. Isn't yours?