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:
Ultimately, each framework operates as the guardrails – the minimum set of rules – for teams to self-manage within.
What did the team do that caused quality to improve or get worse? When did this occur?
Did the number of items that got to Done go up or down? What did the team do that caused this to happen?
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?
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.
Did stakeholders report they felt more engaged? What did the team do to cause this? How will you make sure it happens again?
Did the team acheive its goal? What did they do this time that meant the goal was acheived? Make sure you know the cause so you can repeat it next Sprint.
Optimise flow of work through upgrading the team’s visual board to Kanban
Get the most out of the latest version of the IT service management (ITSM) and agile
Yuval Yeret answers questions on flows inside and outside Scrum from a Lean and Kanban perspective
What are the key differences between traditional linear, waterfall delivery methodologies and agile frameworks?
Extreme Programming empowers developers to confidently respond to changing customer requirements, even late in the product
The Scaled Agile Framework (SAFe®), is a knowledge-base of organisation and workflow patterns. SAFe® enables Scrum,
Scrum was developed by Sutherland and Schwaber in the early 1990s. It’s is a lightweight framework
Many organisations seek agility. Its promise is faster delivery, higher quality, and lower costs, all with
All fields are required.