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
Is Agile Really Just a Mindset?
Explores Agile as a disciplined system of delivery, emphasizing engineering excellence, CI/CD, observability, and system design over mindset …
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 …
Your Evolving Definition of Done
Explains how the Definition of Done evolves in Scrum, aligning team practices with organisational standards to ensure consistent quality, …
Release planning and predictable delivery
Explores how agile teams can achieve predictable software delivery through quality focus, effective release planning, and continuous …
There Is No Such Thing as a "Junior" Scrum Master
Argues that the Scrum Master role requires proven mastery and real-world experience, not entry-level skills or certifications, and should be …
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, …
Definition of Done - Objective vs Subjective
Explains the difference between subjective goals and the objective Definition of Done in Scrum, highlighting how clear, measurable criteria …
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 …
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 …
Is Agile Really Just a Mindset?
Explores Agile as a disciplined system of delivery, emphasizing engineering excellence, CI/CD, observability, and system design over mindset …
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 …
Your Evolving Definition of Done
Explains how the Definition of Done evolves in Scrum, aligning team practices with organisational standards to ensure consistent quality, …
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, …
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 …
There Is No Such Thing as a "Junior" Scrum Master
Argues that the Scrum Master role requires proven mastery and real-world experience, not entry-level skills or certifications, and should be …
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 …
Definition of Done - Objective vs Subjective
Explains the difference between subjective goals and the objective Definition of Done in Scrum, highlighting how clear, measurable criteria …
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 …
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 …
Overview of 'applying flow metrics for Scrum' course
Learn how to use Kanban flow metrics in Scrum to improve value delivery, track progress, identify bottlenecks, and drive continuous …
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 …
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 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 …
Understanding the Power of Kanban in Scrum
Explains how integrating Kanban with Scrum boosts transparency, limits work in progress, and improves workflow, helping teams identify …
Product Ownership vs. Product Management: Busting the Myth That They're Separate Roles
Explains why product ownership and product management are deeply connected in Scrum, clarifying their roles, focus on value delivery, and …
The Scrum Guide (February 2010)
185 resources, newest first
Unlocking Success in Agile: Why Your Definition of Done is Essential for Quality Delivery
Explains why a clear Definition of Done is vital in Agile and Scrum for quality delivery, transparency, and risk mitigation, with tips for …
Combatting Famine in Agile: How to Foster Stakeholder Engagement and Boost Team Morale
Explores how lack of stakeholder feedback in Agile harms team morale and alignment, and offers practical ways to boost engagement and …
Why Agile Success Relies on Effective Planning: Debunking the Myths of Scrum
Explains why effective planning is essential in Agile and Scrum, debunking myths about planning, and highlights strategies for teams of all …
Scrum is like communism, it doesn't work. Myth 1
Explains why Scrum events are not pointless meetings but structured opportunities for inspection, adaptation, and progress, clarifying …
7 Harbingers of the Agile apocalypse - Silence
Explores how silence in agile teams signals disengagement, and offers strategies to boost stakeholder participation, open communication, and …
Quotes: Less is More. True or False?
Explores how applying 'less is more' in Agile boosts productivity and quality by focusing on high-value tasks, reducing waste, and …
When is an APS course appropriate for a scrum team?
Explains when an Applied Professional Scrum (APS) course benefits Scrum teams, helping them identify and remove ineffective practices to …
Quotes: Don't scale Scrum! Pragmatic or defeatist?
Examines whether the belief that Scrum can't scale is practical or defeatist, highlighting Nexus as a proven approach for scaling Scrum to …
Quotes: "I estimate that 75% of those organisations using Scrum will not succeed in getting the benefits that they hope for from it." - Ken Schwaber
Most organisations fail to achieve Scrum’s promised benefits due to focusing on team processes over holistic, organisation-wide change and …
How to Set and Achieve Effective Sprint Goals
Learn how to define, craft, and achieve effective Sprint Goals in Scrum, using frameworks like SMART and OKR to align teams, deliver value, …
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 …
Decoding Scrum Team Work: Balancing Sprint and Refinement Work
Explains how Scrum teams can balance Sprint work and Refinement, with strategies and visual tools to track, manage, and visualise both for …
How does a Scrum Master or Agile coach motivate a Scrum Team?
Explains how Scrum Masters and Agile coaches boost team motivation by setting clear goals, fostering engagement, recognising achievements, …
What should you do if your Sprint Review delivers harsh, scathing feedback?
Learn how Agile teams can handle harsh Sprint Review feedback by analysing root causes, engaging stakeholders, and deciding whether to halt, …
Who Should Lead the Sprint Review? Unpacking the Role of the Product Owner in Agile Success
Explains why the Product Owner should lead Sprint Reviews in Agile, detailing their role in maximising value, gathering feedback, and …
What should be top of mind when a Scrum team prepare for a Sprint review?
Learn how Scrum teams can boost Sprint review success by engaging stakeholders, tailoring communication, and focusing on value, …
What is empiricism and why is it so critical to great Agile?
Explains how empiricism, continuous observation, inspection, and adaptation, drives Agile success by enabling teams to respond effectively …
How effectively does an APS prepare a team to do a solid, professional Scrum?
Explains how Applied Professional Scrum (APS) helps teams master Scrum by focusing on fundamentals, removing unhelpful practices, and …
Unpacking the Scrum Master Myth: Why Servant Leadership is Key to Team Success
Explains why the Scrum Master is a servant leader, not an authority figure, and how this approach empowers teams, encourages autonomy, and …
Best Scrum advice you ever received?
Emphasises the importance of flexibility and pragmatism in Scrum, encouraging teams to adapt frameworks to their context rather than rigidly …
How do you select the most valuable items for the sprint backlog?
Learn how Agile teams collaboratively select high-value sprint backlog items by balancing business needs, technical priorities, and …
What is a Sprint Backlog?
Explains the Sprint Backlog as a transparent, flexible plan in Scrum, combining goals, tasks, and strategy to help teams stay focused, …
Mastering Sprint Planning: Key Principles for Agile Success
Learn essential principles for effective Sprint planning in Agile, including understanding the product backlog, setting clear goals, and …
What is the most common mistake in sprint planning?
Explains the sprint goal in Scrum as a clear, tactical objective for each sprint, guiding team focus, enabling actionable feedback, and …
What is Sprint Planning?
Sprint planning is a collaborative session where teams define and align on goals, tasks, and priorities for the next sprint, ensuring …
What is Scrum?
Scrum is a framework that helps teams organise and adapt to complex, changing tasks by enabling collaboration and shared goals in uncertain …
#1 tip for a new Scrum Master
New Scrum Masters should start by thoroughly reading the Scrum Guide to understand Scrum principles, roles, and practices, forming a strong …
Redefining the Scrum Master: From Misconceptions to Empowering Leadership
Explores common misconceptions about the Scrum Master role, highlighting the shift from tool admin to empowering leader who fosters team …
Beyond the Rituals: Embracing the Core Principles of Scrum for True Agile Success
Explores how focusing on Scrum’s core principles, empiricism, transparency, and value delivery, leads to true agile success, beyond just …
Unlocking Trust in Scrum: The Power of Openness and Transparency
Explores how openness and transparency in Scrum foster trust, clear communication, and a supportive team culture, essential for effective …