Thursday, March 01, 2007
Metrics aren't required for Improvement...
Hopefully folks won't get it twisted and think what I discussed in a previous blog entry that metrics are a requirement for improvement...
I am also of the belief that metrics allow those unfamilar with select IT disciplines to participate. Consider the fact that the vast majority of project managers within an IT organization nowadays simply have zero clue as to how to write high quality valuable working software. If you happen to be in a shop where strong technical leadership is pervasive (I envy you) then metrics may be less worthy of your attention.
Anyway, here are several useful practices that enterprise architects should champion independent of any metrics-orientation:
| | View blog reactionsI am also of the belief that metrics allow those unfamilar with select IT disciplines to participate. Consider the fact that the vast majority of project managers within an IT organization nowadays simply have zero clue as to how to write high quality valuable working software. If you happen to be in a shop where strong technical leadership is pervasive (I envy you) then metrics may be less worthy of your attention.
Anyway, here are several useful practices that enterprise architects should champion independent of any metrics-orientation:
- 1. Continually collect from what has worked in the past.
2. Favor collections of patterns, practices, and rules over monolithic processes or structures.
3. Favor simplicity, clarity, and brevity over completeness, accuracy, and correctness.
4. Favor what works over why it works.
5. Make your word bond and commit with passion to never allowing your word to fail.
6. Periodically narrow/remix collections to your ten favorite patterns/practices/rules.
