Even in an environment where you have a single, ideal, co-located cross-functional team, I believe you're going to need processes and tools. The more complex and distributed your organization, the more processes and tools you're going to need. Doesn't sound very agile does it? Well, get over it. You're going to need processes and tools to enable individuals and interactions. If you can't sit in your chair and make direct eye contact with everyone on your team, you need more processes and tools. Hell, even if you can see everyone, you'll still need processes and tools. What is Scrum? A process framework. What is a team board? A communications tool.
I'm not dismissing the Agile Manifesto. I do prefer individual and interactions over processes and tools. I'm just trying to establish some context. Most of us don't work in that ideal agile world. Rather, we have to operate within a series of non-ideal organizational constraints. Most people are sold on the idea of Agile. The values and principles resonate with us. But my job (and LeadingAgile) is to understand the goals of an organization and help them reach them. We start by laying the foundation for an agile enterprise by forming teams and installing a Lean/Kanban based governance model, but maintaining focus on longer term planning, risk management, and dependency management.
Before laying the foundation, I look at their current organizational structure, I look at their current governance (processes) and I look at their current metrics to see how good that structure and governance is working out for them.
Future State with Process and Tools
Whatever the future state looks like, I expect two things to help get us there.
1. We need to provide clarity by making process policies explicit. 2. We need to demonstrate incremental improvements by using tools.
Do you agree with me? Maybe you disagree with me. I'd love to read your feedback.
Image Credit: Pictofigo