The agile manifesto makes clear the authors’ value of people over process. With that, many readers/users of the manifesto somehow misconstrue this as “People. No process.”
Others, being more intelligent and reasonable, do see the value of having and using processes, they’re thinking a little beyond the next 11 seconds and are reflecting a bit deeper on the roles of and interplay between people and processes. Such people are seeing that the real question isn’t about people or process, but that what they struggle with is how to find value in what people do and the processes they perform.
Value.
That’s a powerful word. I love this rich word. You can get all sorts of people to stop and think about what they’re doing when you ask them the value of their effort.
Asking about value can come full circle – even for process people. What’s the value, for example, of checking on a process?
Many use process audits, but what’s the value in it? Especially if the process works fine, and, there’s a cost to check on it – with a net result that you spent time (= money) checking for something that didn’t and might not happen.
Calling them “objective evaluation”, CMMI® is replete with efforts that are expected to check on processes. (GP2.9, PPQA, OPF, et al.) Though, CMMI® is purposefully thin on exactly how to accomplish this, many have chosen to carry out “objective evaluation” using ‘audits’.
Audits not only invoke a confrontational and defensive entrenchment, but also have the attribute of easily devolving into “process policing” and other non-value-added paradigms. Don’t misunderstand, we’re not saying it’s not important to keep tabs on your processes, but there are more and less value-added approaches to how you go about doing them.
At the risk of sounding too much like advice from an Eastern mountain top, I propose that you allow people to be the process.
That is, imbue a cadre of people whose jobs are to know the processes best. Not CMMI® processes, not Agile practices, but the processes the organization wants everyone to know and use. How else will anyone know what to do? Great organizations do this all the time. No one questions their use of such people.
Clearly, it would be out of character for me to suggest that you don't have processes, or that you create “lottery sensitive positions” (i.e., critical, single-point-failure positions whose loss would be severely disruptive to success). So, this is not what I’m saying.
But if the idea is that you want everyone to be on the same page, that you want to create processes that people want and love and that they can identify with;
if you want to create a reliable culture of excellence where everyone truly participates in creating exquisite results;
where everyone is fully invested in the organization and its success;
in the language of CMMI® -- where the processes are firmly institutionalized;
that people who know the process very well and whose jobs are dedicated to helping everyone else learn and use the process are out in the projects coaching and mentoring teams in the process, facilitating retrospectives, demos, peer reviews and whatnot...
There isn't a non-CMMI® or a non-Agile thing about this!
We’re talking about coaching, mentoring, and facilitation.
Self-directed, self-organized teams still have coaches, Scrum masters, and someone to turn to when things are stuck or just don't seem to be working correctly...
... you want to grow an organization where everyone knows what to do without being told? Use coaching and mentoring of your patterns in your patterns.
There can be a smaller organization of just such coaches, mentors and facilitators, with others rotating in and out of on some regular cadence, these people can also gather lessons, collect information, spread new ideas, create experiments, and routinely check to see whether and how well what teams are doing is working.
If/when there are new and better ways of doing things, these coaches can help refine them and make them usable by other teams, when things are broken, they help fix them.
Why do audits want to know whether the process is being followed? If it’s compliance, then it might very well be a waste of time.
The real reason is to learn about the process and to use the audit as an opportunity to learn about and share what’s working and what doesn’t. So, instead of audits, why not jump straight to the real purpose behind them and ask, “what are you doing?” and “how’s that working for you?”
You’ll get the same benefit without all the baggage, waste and negativity.
Doesn't everyone know this is what having a defined process is?
Doesn't everyone understand that this is how process evaluations or audits are supposed to work?
No? Really? Huh!
People over Process, Right? Great! Let people *be* the process!
Labels: Agile Manifesto, Audit, Coaching, facilitation, Mentoring, Objective Evaluation, People over Process, PPQA
