Agile frameworks are structured methodologies that facilitate the implementation of Agile principles within organisations, enabling teams to deliver value predictably and sustainably. These frameworks, such as Scrum, Kanban, and Lean, provide specific roles, events, and artefacts that guide teams in their work, fostering collaboration, transparency, and continuous improvement. By adopting an Agile framework, organisations can respond more effectively to changing market demands and customer needs, ensuring that they remain competitive and relevant.
The systemic nature of Agile frameworks encourages a culture of experimentation and learning, allowing teams to iterate on their processes and products. This adaptability is crucial for long-term success, as it empowers teams to identify inefficiencies and optimise workflows, ultimately enhancing value delivery. Agile frameworks also promote cross-functional collaboration, breaking down silos and enabling diverse skill sets to contribute to shared goals. This holistic approach not only improves team dynamics but also aligns organisational objectives with customer satisfaction, driving better outcomes.
By embedding Agile frameworks into their operations, organisations can cultivate an environment that prioritises responsiveness and innovation, ensuring they are well-equipped to navigate the complexities of modern product development and market dynamics. The focus on continuous delivery and improvement fosters resilience, enabling teams to thrive in an ever-evolving landscape.
The strongest work on Agile Frameworks — ranked by substance, not recency. How this is ranked
Telling People What to Do Is Not Leadership. It’s a Failure of System Design
Explores why real leadership means designing systems that enable team autonomy, flow, and accountability, rather than relying on …
Delivery is the only Measure of Progress in Scrum
Scrum teams must deliver working software to real users every Sprint; true progress is measured by delivery to production, not just by …
Release planning and predictable delivery
Explores how agile teams can achieve predictable software delivery through quality focus, effective release planning, and continuous …
The Scrum Master is accountable for Delivery
Explains how the Scrum Master is accountable for enabling effective product delivery, fostering team success, and ensuring each sprint …
The Role of Agency in Scrum: Why Self-Management Without Agency is a Lie
Explains why true Scrum requires real team agency, not just self-management in name, and how lacking agency leads to ineffective, …
Your Evolving Definition of Done
Explains how the Definition of Done evolves in Scrum, aligning team practices with organisational standards to ensure consistent quality, …
Without Delivery, There Is No Value
Value in software is only realised through delivery. Frequent releases validate assumptions, reduce risk, and enable rapid feedback, …
Balance of Leadership and Control in Scrum
Explores how Scrum Masters and Product Owners balance leadership, authority, and team autonomy to ensure accountability, effective …
The Definition of Done is a Commitment to Quality
Defines the Definition of Done in Scrum as a clear, shared standard for quality, ensuring increments are releasable, transparent, and …
Telling People What to Do Is Not Leadership. It’s a Failure of System Design
Explores why real leadership means designing systems that enable team autonomy, flow, and accountability, rather than relying on …
Delivery is the only Measure of Progress in Scrum
Scrum teams must deliver working software to real users every Sprint; true progress is measured by delivery to production, not just by …
Release planning and predictable delivery
Explores how agile teams can achieve predictable software delivery through quality focus, effective release planning, and continuous …
The Definition of Done is a Commitment to Quality
Defines the Definition of Done in Scrum as a clear, shared standard for quality, ensuring increments are releasable, transparent, and …
The Role of Agency in Scrum: Why Self-Management Without Agency is a Lie
Explains why true Scrum requires real team agency, not just self-management in name, and how lacking agency leads to ineffective, …
Your Evolving Definition of Done
Explains how the Definition of Done evolves in Scrum, aligning team practices with organisational standards to ensure consistent quality, …
Great Scrum Masters Need Technical, Business, and Organisational Mastery
Scrum Masters are most effective when they combine leadership skills with technical, business, and organisational mastery to support teams, …
Balance of Leadership and Control in Scrum
Explores how Scrum Masters and Product Owners balance leadership, authority, and team autonomy to ensure accountability, effective …
Why Measuring Individual Cycle Time is Killing Your Flow (And What to Do Instead)
Measuring individual cycle time in Kanban misleads teams, hides real bottlenecks, and harms flow. Focus on system-wide metrics like PCE, …
Maximizing Transparency and Improvement in Software Engineering with Kanban
Learn how Kanban boosts transparency in software engineering, helping teams visualise workflows, identify bottlenecks, and drive continuous …
Are Your Teams Empowered to Change Requirements Based on User Feedback? If Not, You’re Probably Not Very Agile
Empowering teams to adapt requirements based on user feedback is key to true agility. Learn why backlog updates and team engagement drive …
Scrum doesn't solve problems, it reveals them. How, and why is that valuable?
Explains how Scrum exposes hidden organisational problems through transparency and feedback, enabling teams to identify issues, improve …
The Open Guide to Kanban: Unlocking Collaborative Flow and Real-World Value for Every Team
Unlock better flow and real value with the Open Guide to Kanban, a practical, community-driven resource for teams in any industry. Join the …
Acceptance Criteria vs Definition of Done: Why Getting This Right Builds Trust and Delivers Quality Faster
Stop confusing acceptance criteria with definition of done, learn the crucial difference to boost quality, speed, and trust in your agile …
Why the Concept of a "Junior Scrum Master" is a Misguided Myth
Explains why the Scrum Master role requires experience and competence, debunking the myth of a "junior" Scrum Master and highlighting the …
Unpacking the Scrum Master Role: Moving Beyond Misconceptions to True Accountability
Explores common misconceptions about Scrum Masters, clarifies their true accountabilities, and highlights the importance of principles, …
The Competence Crisis in Scrum Master Roles: A Call for Excellence
Many Scrum Masters lack essential skills and experience, leading to poor agile outcomes. True competence requires deep knowledge, practical …
The Power of Kaizen: Continuous Improvement in Scrum and Beyond
Explains how Kaizen’s continuous improvement principles enhance Scrum and Agile teams, with practical tips for retrospectives, workflow …
Kanban Guide
Comprehensive reference outlining Kanban principles, practices, and metrics for optimising workflow, value delivery, and continuous …
Kanban Guide for Scrum Teams
Explains how Scrum Teams can use Kanban practices to optimise workflow, track flow metrics, and enhance transparency, efficiency, and …
Manifesto for Agile Software Development
Outlines core Agile values and principles for software development, emphasising collaboration, adaptability, working software, customer …
Nexus Guide
Explains the Nexus framework for scaling Scrum with multiple teams, detailing roles, events, and artefacts to coordinate product delivery …
The Scrum Guide (February 2010)
A clear summary of Scrum’s framework, roles, events, artefacts, and values, explaining how teams use Scrum to deliver value and adapt to …
194 resources, newest first
Navigating Complexity: Why Agile Practices Are Essential for Modern Product Development
Explains how agile practices help teams manage complexity, adapt to change, and deliver value faster in modern product development, compared …
Mastering the Art of Scaling Scrum: Insights from the Scaled Professional Scrum Course
Learn practical strategies for overcoming common challenges in scaling Scrum, based on hands-on insights from the Scaled Professional Scrum …
Hiring a Professional Scrum Master
Covers key responsibilities, skills, and requirements for hiring a Scrum Master, including leadership, coaching, facilitation, and fostering …
Sprint Goal is an Immediate Tactical Goal
Explains how the Sprint Goal serves as an immediate tactical objective in Scrum, guiding teams toward strategic Product Goals and maximising …
If your backlog is not refined then you are doing it wrong
Explains why regular backlog refinement is essential in Scrum, how to make backlog items ready for Sprint Planning, and ways to measure …
Getting started with a Definition of Done (DoD)
Explains how to create, apply, and improve a Definition of Done (DoD) in Scrum to ensure software quality, transparency, and consistent …
A better way than staggered iterations for delivery
Explains why staggered iterations harm software delivery, increasing technical debt, and recommends cross-functional teams, test-first, and …
Professional Scrum teams build software that works
Professional Scrum Teams prioritise software quality, accountability, and continuous improvement, ensuring each release is reliable, …
The Sprint Goal is a commitment for the Sprint Backlog
Explains how the Sprint Goal guides Scrum teams by providing a clear, shared objective for each Sprint, ensuring focus, transparency, and …
Release planning and predictable delivery
Explores how agile teams can achieve predictable software delivery through quality focus, effective release planning, and continuous …
The Product Goal is a commitment for the Product Backlog
Defines the Product Goal as a clear, measurable objective in the Product Backlog that guides Scrum Teams, ensuring focus, transparency, and …
Update to the Scrum Guide on the 25th Anniversary of the Scrum Framework
Summarises key changes in the 2020 Scrum Guide, including simplified language, self-managing teams, and new commitments for goals, backlog, …
I do continuous deliver, why should I Sprint?
Explains why Sprints are valuable even with continuous delivery, highlighting benefits for planning, feedback, communication, and …
The fallacy of the rejected backlog item
Explains why rejecting individual backlog items at Sprint Review is a misconception, highlighting Scrum’s focus on learning, collaboration, …
Mastering Scrum: Key Insights on Definition of Done, Spikes, and Managing Ad Hoc Work
Explains key Scrum concepts: distinguishing Definition of Done from acceptance criteria, using spikes vs. refinement, and strategies for …
Scaling Agility: Navigating the Dragons of Change in the Future of Work
Explores practical strategies for scaling agile practices, key metrics, virtual training adaptations, and global insights to navigate change …
Can the Definition of Done change per Sprint?
The Definition of Done can evolve to improve quality but should not be weakened or vary per backlog item. Consistency ensures transparency …
In Nexus with 5 Scrum teams, how can the Product Owner attend all Sprint Planning events?
Explains how a Product Owner can manage Sprint Planning across multiple Scrum teams in Nexus by delegating, using area or team owners, and …
Are technical skills required to be a Scrum Master?
Technical skills are not required to be a Scrum Master, but understanding technical, business, and organisational contexts helps Scrum …
How do you incorporate a Design Sprint in Scrum?
Explains how to integrate Design Sprint activities within Scrum by embedding design and UX work into regular sprints and backlog refinement, …
DOD has made it illegal to do waterfall
The US Department of Defence now requires agile, iterative software development, ending mandatory waterfall methods and influencing global …
Introducing Kanban for Professional Scrum Teams
Learn how Kanban practices can be integrated into Professional Scrum teams to improve workflow, transparency, and delivery using the new …
Work can flow across the Sprint boundary
Explains how Scrum teams can strategically allow unfinished work to flow across Sprint boundaries, enhancing throughput, responsiveness, and …
Professional Scrum Training for the Ghana Police Service
Professional Scrum training introduced Ghana Police officers to Agile methods, using hands-on sprints to support organisational change and …
Transforming Scrum Training: How Real-World Insights Empower Agile Teams at Great Calm
Explores how practical, real-world Scrum training at Great Calm improved team collaboration, alignment, and continuous improvement across …
Choosing a Process Template for your Team Project
Guidance on selecting the best process template for team projects in TFS or VSTS, highlighting why the Scrum template reduces friction for …
Big Scrum: All you need and not enough
Explores how to scale Scrum effectively by applying agile values, fostering professional teams, and adapting processes to fit unique …
Big Scrum: Are you doing mechanical Scrum
Explores the difference between mechanical and Professional Scrum, highlighting the importance of values, principles, and technical …
My journey into Professional Scrum
Reflects on experiences with Professional Scrum, highlighting its impact on software development, team culture, training, and the challenges …
Upcomming Scrum at Scale Workshop from Scrum.org
Learn how to scale Scrum across your organisation, drive cultural change, and measure agile maturity with evidence-based practices in this …
Professional Scrum in Immingham, UK
Summary of a multi-team Professional Scrum training at DFDS Seaways in Immingham, UK, highlighting co-located learning, cross-team …
The Insufficiency of Scrum is a fallacy
Scrum alone does not cause project failure; lacking strong engineering practices and effective retrospectives leads to technical debt and …
Professional Scrum Foundations in Alameda, California
Covers a two-day, hands-on Scrum.org course in Alameda, teaching Scrum principles, teamwork, and practical software delivery for all roles …
What's in a burndown?
Explains burndown charts in Scrum, their purpose, common issues, and compares tracking by hours, story points, and acceptance tests to …
Scrum-damentals Webcast on 17th February 2012
Explore common challenges in Scrum adoption, practical strategies for overcoming them, and proven practices to help teams implement Scrum …
Are you doing Scrum? Really?
Explains recent changes to Scrum aimed at reducing rigidity, clarifying core practices, and providing a checklist to help teams assess if …
Scrum is hard to adopt and disruptive to your organisation
Explains why adopting Scrum is challenging and disruptive, highlighting the need for training, mentoring, and dedication for successful …
You are doing Scrum but the Scrum Master tells the team what to do!
Explains why Scrum Masters should not direct teams, emphasising self-organisation, shared responsibility, and the importance of team …
Coffee Talk: Introduction to Scrum - webcast event this Friday!
Learn the basics of Scrum, including its key roles and processes, with practical tips for adoption. Ideal for those new to agile or seeking …
My first Scrum team in the wild
A real-world account of guiding a new Scrum team through their first sprint, covering estimation, story points, sprint planning, and …
Professional Scrum Developer (.NET) Training in London
Intensive five-day course for software developers covering Scrum, Visual Studio 2010, .NET, and Agile practices through hands-on team …
Adventures in Scrum: Lesson 2 - For the record
Highlights the importance of clear communication and documenting disagreements in Scrum to prevent misunderstandings and failed sprints, …
Adventures in Scrum: Lesson 1 – The failed Sprint
Explores common pitfalls in early Scrum adoption, highlighting why full team involvement in sprint planning is crucial and lessons learned …
The Scrum Guide (February 2010)
A clear summary of Scrum’s framework, roles, events, artefacts, and values, explaining how teams use Scrum to deliver value and adapt to …