Where is the Agile I was promised ?
We adopted agile 2 years ago. However, I feel we are still missing the Agile we were promised.
We are going through a transformation, but it feels so chaotic and people are very unhappy.
We have been Agile for the past 3 years but I am still not sure if it helped us be more productive?
And so on ….
Do you find that any of the above applies to your organization? Have you had this conversation or at least read an article on the same subject?
Hmm ...
So what do you think is happening with so many people complaining about Agile?
There are two possibilities
- We were lied to and tricked - Agile never worked for anyone and is a flawed process.
OR
- The Agile I understood and adopted is not what Agile is.
To start with, I will go with option 2 and will come back to option 1 later.
Option 2: The Agile I understood and adopted is not what Agile is.
Before I come back to Option 1, I would like to explain Agile in a non-Technical way (to simplify it).
Agile has two parts
- Body / Frame: The body of Agile includes
- Roles: Scrum Master, Product Owner & Delivery Team
- Ceremonies: Planning, Refinement, Daily Stand Up, Sprint Review & Retrospective
- Artifacts: Product Backlog, Sprint Backlog & Burndown Charts,
- Other Parts: Definition of Done, Definition of Ready, Working Agreements.
- Soul
- Agile Values (Communication, Simplicity, Courage, Feedback, Trust, Collaboration, Respect, Focus, Commitment)
- Servant leadership. (Leader who develops people, removes impediments, provides autonomy, engages & motivates)
- Autonomy of individuals (Teams have a say in decision making, they are not dependent on managers for everything)
- Performing Roles as prescribed (We act as Scrum Master and not the Manager, we act as a Product Owner and not a messenger, we act as a team and not individuals)
- System thinking (Optimization of subsystems of the systems and thinking of the system as a whole)
Now since we talked about the Soul of Agile let’s go back to basics. i.e. the Agile Manifesto.
- Individuals & Interaction over Process & Tools;
- How much time and money have you invested in motivating individuals to collaborate? Or is that an overhead?
- What have you invested in teams to come together, talk, eat, have fun, know about each other, go out together? Or have you assumed that a lunch once in a while is enough to bring together and collaborate?
- How much autonomy do your teams / individuals have? Are they aware of and involved in decisions? Can they talk and express themselves freely? Or you think that decisions are to be only made by managers?
- How accessible, approachable and involved are you with your teams? Or you think Managers are to manage and belong to their office.?
2. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
I picked three points “Motivated Individualsâ€, “Environment and Support†and Trust:
- So what have you done to motivate your teams or individuals? Activities, incentives, participation, autonomy, empowerment, involvement?
- How have you supported your teams? Are you easily accessible to remove any impediments, have you allowed your teams to make decisions, can they freely express their opinions, do they drive themselves or are they “Managed�
- Do you trust your teams? Do they trust you? What have you done to build that trust?
3. Business people and developers must work together daily throughout the project.
- Are business people really available to work with the developers? I mean Business People not a messenger?
- Alright, they are available, but are they really business people?
- Fine they are business people, how much do they engage the developers for their inputs and ideas? How transparent are they with the teams i.e. vision, roadmap, evolving needs & feedback.
4. The best architectures, requirements and designs emerge from self-organizing teams.
- So what is self-organizing to you?
- Have you invested in people to develop their skills?
- Have you given an opportunity to people to participate in discussions that help designs & architectures emerge?
I can go on and on. However, at this point I would like to ask you, how much have you invested in the Body of Agile versus the Soul of Agile? I hope you are not expecting the body to function without its soul. I will let you answer for yourself “Where is the Agile you were promisedâ€.
Also, do I still need to talk about Option 1?
PS: Special thanks to my mentor Steve Sanoff to always motivate and guide along the way.
Well said Adri Fijneman, it very well goes hand in hand. Also, it takes a lot for organizations to embrace that teams will fall, crawl and eventually walk. Also, what to do and what not to do are two sides of a coin. Well said !
Specialist Agile enterprise / Wendbare organisatie
9 å¹´Hi Pradeep. This is truly a nice read. Sometimes I advice to look at it from the other perspective. Is it really the question "what needs to be done" or is the soul in "what one shouldn't do". Trust and self-organization ask for letting go. Of course a child will fall and hurt itself, but eventually it will walk. Agility is based on confidence and trust, so let teams and professionals walk and find their way. Just give the goals to go for.
Setting up clear expectations and transparent conversations is primary on the part of coaches and trainers and also setting up clear directions that "what needs to be done" to be agile. Agile is truly bought and sold on rainbows and unicorns !
Project Manager, Program Management Office at Roche
9 å¹´I've found that organizations are sold promises like "300% improvement out of the box!" (If you write us a fat check) and they wonder where are the results they were promised. Trainers, consultants, coaches, etc. aren't up-front that you don't get the improvement for free, so organizations are set up with unreal expectations, no knowledge or agreement and commitment to the work needed to transform the organization. A symptom of this is a pervasive background of "agile doesn't work." It's the fear of saying: you don't get the results for free, and I don't mean dollars; there's intellectual and organizational effort involved... because you might be told "No" or "thanks but someone else can give us 300% for free." Didn't we see this with ISO 9000, PMP, Six Sigma,... ;)
Transforming your workforce by developing collaborative leadership increasing performance 'n engagement | 5X LinkedIn Top Voice - Facilitation, Team Facilitation, Team Management, Team Leadership, Team Building
9 å¹´True - like most methods developed over the years, organizations pick on the surface ideas but never train to understand the concepts - the "why". So, organizations feel that if they say the right words, they get it. It requires deep understanding and effort to make it work - that is true of every method. If you really understand it and get it, it works - Agile is the same.