This is a question that comes up from time to time and to me, it’s like asking; “What does it mean to be 100% Chinese, Indian, German or Italian?”
If we have everyone doing Scrum, does that mean we are 100% Agile? That’s like asking, “If I listen to Italian music, eat Italian food, drink Italian wine, and live in Italy, does this make me Italian?” Maybe it does…maybe it doesn’t! If you have read about my talk at Agile-2011 know where I am going with this. Being 100% Agile to some extent means we cannot explain why we are Agile, we simply are. Why am I Italian? I just am.
I come from a Punjabi culture. While preparing my talk for Agile-2011, I asked my sister why we value respect and deference to our elders. Her comeback was “The culture of guilt and shame.” We laughed. She reminded me of how if we failed to accord the appropriate respect to our elders, which included our parents’ best friends, we were taken aside and admonished with, “Aren’t you ashamed of yourself? Go say sorry to your Auntie!” Mom and Dad never explained WHY we should feel ashamed, only that we should…
I’ve been reading “Implementing Beyond Budgeting” by Bjarte Bogsnes. Finance is sometimes a neglected area in terms of Agile Transformation and Bogsnes’s book offers rock-solid advice. The first element is the set of leadership and process principles.There are 6 of each:
- Customers. Focus everyone on improving customer outcomes, not on hierarchical relationships.
- Organization. Organize as a network of lean, accountable teams, not around centralized functions.
- Responsibility. Enable everyone to act and think like a leader, not merely follow the plan.
- Autonomy. Give teams the freedom and capability to act; do not micromanage them.
- Values. Govern through a few clear values, goals, and boundaries, not detailed rules and budgets.
- Goals. Set relative goals for continuous improvement; do not negotiate fixed performance contracts.
- Rewards. Reward shared success based on relative performance, not in meeting fixed targets.
- Planning. Make planning a continuous and inclusive process, not a top-down annual event.
- Controls. Base controls on relative indicators and trends, not on variances against the plan.
- Resources. Make resources available as needed, not through annual budget allocations.
- Coordination. Coordinate interactions dynamically, not through annual planning cycles.
These are difficult principles to live by without trust, transparency and simplicity in your organization. Adopting these principles takes time and effort, and a rather gargantuan mind shift. Eventually you’d want them all, but if you had to start somewhere, which principles would start acting on tomorrow?
Can we apply Pareto to the budgeting process, focusing on the top 20% of financial decisions and issues aligned with the Product Backlog?
Decisions on what to STOP doing are as important as the decision on what to START doing. Are you making the hard calls? Can you apply Pareto to both decision types? What will we fund? What will we kill?
More to follow on this topic in a future post.