Individuals and interactions over processes and tools is an Agile value I believe in with a special fervor. Process is a servant to people. The right process is what makes a gestalt out of what was once a mere workgroup with product or project affinity.
There is a significant and qualitative difference between (1) teams who leverage one another to discover then achieve known objectives they believe in and (2) individuals who find commonality only in job description and, if they’re lucky, camaraderie in lamenting pointless busy work.
I’ll take option (1), thank you very much. Let’s work together. Let’s amplify and feed off one another. Let’s make our process…
… support creativity by removing busy, boring, tedious work.
… ambient, simple and usable.
… involve our users, accepting their feedback.
… well known and explicit.
… open to scrutiny, subtraction and addition.
GitHub
LinkedIn
Twitter
{ 2 comments }
Would love to hear a bit more about what you feel constitutes an “ambient” process….Also, perhaps you want to speak at Tallahassee Code Camp again this year…”The Ideal Process” would make a great session
I chose the word Ambient because I like our process to be part of our environment. It's useful knowing when a build fails; I like to know where the release is at a glance; Transparent goals are achievable goals. In short: put the way you work up on the wall!
I'd love to do Tally CC! It's gonna be hard for me to get down there, but I'd be happy to Skype it up if you think it'd be worthwhile.
Comments on this entry are closed.