eam performance refers to the consistent ability of a team to deliver outcomes through its system of work. It reflects delivery capability over time, as measured by observable patterns in flow, responsiveness, and quality.
Performance emerges from the structure and constraints of the system the team operates within. It is influenced by team composition, collaboration habits, skill alignment, and clarity of purpose. This makes team performance a system-level capability, not an individual or cultural trait.
By evaluating team performance using flow metrics (e.g., throughput, cycle time), retrospectives, and empirical signals, organisations can identify whether teams are improving, stagnating, or constrained by external dependencies. High-performing teams show consistency and adaptability in delivery, even in the face of change.
Improving team performance is a matter of system design: limiting work in progress, refining collaboration patterns, and improving visibility into blockers. This systemic lens ensures improvements are sustainable and repeatable across the organisation.
The strongest work on Team Performance — 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 …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
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 …
Stop Building Silos. Start Building Systems
Explains how fragmented automation and tool silos harm software delivery, and advocates for unified engineering systems and platform …
Rethinking Capacity Planning
Explores how effective capacity planning shifts focus from individual hours to system-level flow, using Lean and Agile principles to improve …
Stop Hiding Behind Complexity and Start Delivering Continuously
Continuous delivery is achievable for any software, regardless of complexity. Success depends on investment in automation, quality, and …
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 …
Should You Use One Project to Rule Them All in Azure DevOps?
Explores when to use a single Azure DevOps project versus multiple projects, detailing impacts on flow, visibility, governance, and team …
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 …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Estimating Better in an Overloaded System Is a Poor Man’s Strategy
High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …
Are We Still Pretending Coding Was the Bottleneck?
AI exposes that coding was never the main bottleneck in software delivery; real constraints are in system flow, team practices, and …
Should You Use One Project to Rule Them All in Azure DevOps?
Explores when to use a single Azure DevOps project versus multiple projects, detailing impacts on flow, visibility, governance, and team …
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 …
Rethinking Capacity Planning
Explores how effective capacity planning shifts focus from individual hours to system-level flow, using Lean and Agile principles to improve …
Why “Done” Only Counts When It’s Live: Moving Beyond Fake Finishes to Real Value in Software Delivery
Discover why “done” means live in production, not just code complete. Learn to deliver real value, close feedback loops, and drive outcomes …
Special Sprints: Agile Banditry or Risk Management?
Explores why special sprints like Sprint Zero or hardening sprints undermine Agile by delaying work, increasing risk, and reducing …
The Crucial Role of Competence: How Knowledgeable Scrum Masters Drive Team Success
Scrum Masters with deep knowledge and competence enable teams to deliver better products, drive business outcomes, and foster real …
Stop Guessing: How to Make Work Visible and Drive Real Improvement with Azure DevOps Flow Metrics
Stop guessing, start making data-driven decisions in Azure DevOps. Discover tools, tips, and insights to make your work visible and your …
Legacy Systems Aren’t the Enemy, Friction Is: How to Unblock Innovation and Accelerate Agile Delivery
Is legacy tech slowing your team? Discover how removing friction unlocks agility, innovation, and faster delivery in your organisation.
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 …
How to Tackle Technical Debt Without Halting Progress: Smarter Ways to Keep Your Team Moving Forward
Struggling with technical debt? Discover practical ways to tackle legacy systems, boost team morale, and deliver value, without grinding to …
Why a Shared Definition of Done Is the Secret to Consistent, Predictable Quality in Agile Teams
Struggling with inconsistent delivery? Discover why a shared definition of done is key to predictable, high-quality results your teams, and …
Cloud Migration Without the Mayhem: How to Move Legacy Systems Safely and Set Your Teams Up for Success
Worried about cloud migration chaos? Discover why a hybrid approach beats “lift and shift” and how to align teams for a seamless, risk-free …
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 …
177 resources, newest first
What does a poor scrum team look, act and feel like?
Explores signs of a poor scrum team, including autocratic leadership, dysfunctional product ownership, lack of trust, and organisational …
How does the APS course help people apply scrum effectively?
Explains how the APS course uses practical exercises and simulations to help people understand, apply, and improve scrum practices in …
Unlocking Scrum Success: A Comprehensive Guide to Values, Roles, Artifacts, and Events
Explains Scrum’s core values, roles, artifacts, and events, highlighting how they support teamwork, transparency, and adaptability in …
Hiring a Professional Scrum Master
Covers key responsibilities, skills, and requirements for hiring a Scrum Master, including leadership, coaching, facilitation, and fostering …
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, …
Delivering Live Virtual Classes in Microsoft Teams and Mural
Guidance on running live virtual Scrum classes using Microsoft Teams and Mural, focusing on tech setup, safe collaboration, self-organising …
Rethinking Agile: Why Story Points, Team Sizes, and Emergent Architecture Need a Fresh Perspective
Explores the limitations of story points, optimal team sizes, and the benefits of emergent architecture for improving agile practices and …
Mastering Remote Work: Key Insights for Agile Teams to Thrive in a Digital World
Practical strategies for remote Agile teams, covering communication, tool selection, value delivery, team dynamics, gamification, and …
What is your perspective on collocation?
Explores the benefits and challenges of collocation in Scrum teams, comparing face-to-face collaboration with remote work, and offering …
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 …
How do you handle conflict in a Scrum Team?
Guidance on resolving conflict in Scrum Teams, including facilitation techniques, escalation steps, and the Scrum Master's role in fostering …
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 …
Transforming Chaos into Collaboration: How a Common Framework Can Revolutionise Your Team's Dynamics
Explores how adopting a shared framework and structured communication can turn team chaos into collaboration, boosting trust, engagement, …
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 …
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 …
Searching for self-organisation
Explores the challenges and benefits of self-organising teams, highlighting key factors like team accountability, identity, size, and …
Does your company culture resemble Survivor?
Explores how individualistic, competitive company cultures hinder collaboration and agility, and highlights the benefits of fostering …
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 …
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 …
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 …
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 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 …