During the last 20 years, the agile movement that originated from the Agile Manifesto has gained momentum, even outside of software development.
Most organizations report that their agile efforts have paid off in terms of speed, quality, value, and long-term growth. However, about half of organizations that undertake agile transformations fail in their attempts.
If your team has yet to reap the rewards of agile, you need to understand what’s preventing you from delivering fast, frictionless and scalable solutions.

Successful agile teams

When you've jointly created a list of vulnerable behaviour/response pairings, pick one to practice. If a gap appears between the vulnerable behaviour, the response it should receive and the team leader's own behaviour, the dissonance will breed cynicism and lessen credibility. If a leader tries to model the behaviours and publicly acknowledges mistakes, the team will make progress.

Focus on one behavior and practice cultural accountability

When organisations implement agile, they often revert to technical processes and tools because cultural considerations are difficult to put into practice. It's easier only to pay lip service to the human side and then move to processes with measurable and observable indicators that give the illusion of agile.
Start by framing agile as a cultural rather than a technical or mechanical implementation. Be careful not to approach culture as the completion of tasks. Culture can't be completed.

Frame agile as a cultural implementation

While agile processes and tools provide support, the primary mechanism is how team members interact.
Can team members interact with conflicting ideas, talk and listen, give and take, question and answer, analyse and solve? Or do they censor one another and end up withdrawing themselves?
If you drop agile tools and processes into a legacy culture where individuals are criticised, embarrassed, discouraged, or intimidated, they stop being agile.

Processes and tools are scaffolding

Set time aside in a meeting to review what went well and what could be improved. <ul><li>Discuss the quality of the team's interactions.</li><li>Identify potential threats to openness.</li><li>Ask if they felt included in the process.</li><li>What was the most vulnerable behaviour they engaged in?</li><li>How did the team react to it?</li><li>Did you hold back on anything because you didn't feel safe?</li></ul>

Formally evaluate your dialogic process

Meet with your team to identify vulnerable behaviours they think are vital to success. For example, asking questions, giving feedback or expressing different viewpoints. Then, identify positive response patterns for each behaviour, such as thanking someone for pointing out vulnerable behaviour. Document the behaviour and response pairing and display them in your meeting room. Create a printed job aid of the list that team members can carry with them.

Develop, document, and display vulnerable behavior/response pairings.

Scrum meetings are daily coordination meetings where team members review the backlog, identify problems, and prioritize tasks. They are short meetings used for reflection.
For example, if a team faces a complex issue, they pose a question about the problem and ask the team to come prepared to the next scrum meeting to discuss it. This allows the team to clarify their thoughts and encourages divergent thinking.

Conclude your scrum with a “question/reflection"

Want to build a high-performing team? Start with creating a safer work evironment

books

Books

problemsolving

Problem Solving

teamwork

Teamwork

leadershipandmanagement

Leadership & Management

Fostering Psychological Safety In The Workplace

Scrums and kanbans can’t help you if you’ve got a legacy culture that punishes vulnerability.