While reading some solid content on the 451 Group site, I rediscovered The Rugged Software Manifesto. I got the same feeling as the first time I read it: there should be something similar to rally around sound process. I often say we already have the necessary technology to manage risk to an acceptable level. How about adding a manifesto to help pave the way for a process you can take pride in. Thanks to a very cool Creative Commons license on the Rugged Software site, here goes:
The Rugged Process Manifesto
I am rugged… and more importantly, my process is rugged.
I understand that technology and people aren’t sufficient to serve the business.
I recognize no one requires process maturity. In fact, heroism is often rewarded but I won’t get lured into that trap.
I am rugged because I define my stakeholders, their roles, and am not afraid to sketch out a swim lane diagram.
I am rugged because I respect the difference between responsible and accountable.
I am rugged because I not only measure with metrics, I define target values with my stakeholders.
I am rugged because I go out of my way to publish my process and metrics, good or bad.
I recognize my process will become stressed and I provide stakeholders a way to help me improve.
I am rugged because I bring evidence over opinion to make decisions.
I am rugged because I refuse to be a victim of politics, workload, or under funding. That’s a business decision and my process will be transparent enough to show it’s a conscious one.
Wow, that poured off the keyboard fast. After a review, I think this version is a bit too tactical compared to the philosophical approach to the Software version but hey, it’s a v1. Feel free to jump in and make it better.