Agile isn’t a methodology – a set of fixed and typically highly prescriptive set of processes. Agile frameworks define a purposefully minimal and incomplete set of approaches to planning, managing, and executing work.
Agile frameworks typically fall into two categories:
Frameworks designed for teams.
Frameworks designed to help organisations practice Agile at scale, across many teams.
Ultimately, each framework operates as the guardrails – the minimum set of rules – for teams to self-manage within.
Actions
Choose a framework from the list below.
Apply the basics from the start of the next Sprint.
At the next Retrospective
Quality
What did the team do that caused quality to improve or get worse? When did this occur?
Throughput
Did the number of items that got to Done go up or down? What did the team do that caused this to happen?
Transparency
Was it easier to see the status of work and progress toward the Sprint Goal? Did stakeholders find it easier to understand these things? Why?
Teamwork
Was collaboration more effective? What did the team do to make them feel this way? Ensure you know the cause so you can repeat it next time.
Stakeholder collaboration
Did stakeholders report they felt more engaged? What did the team do to cause this? How will you make sure it happens again?
Goal Achieved
Did the team achieve its goal? What did they do this time that meant the goal was achieved? Make sure you know the cause so you can repeat it next Sprint.
Frameworks
Discover more from Zen Ex Machina
Subscribe now to keep reading and get access to the full archive.