a·gen·tic a·gil·i·ty class·i·fic·at·ion

Scrum: Empowering Teams to Deliver Value Through Empirical Adaptation

A framework enabling teams to collaboratively deliver adaptive solutions through empiricism, iterative delivery, continuous improvement, and value prioritisation.

Scrum is a a social technology for building adaptive solutions it focuses on delivering the highest business value in the shortest time. Scrum is a framework that helps teams work together. Much like a rugby team (where it gets its name) training for the big game, Scrum encourages teams to learn through experiences, self-organize while working on a problem, and reflect on their wins and losses to continuously improve.

Image
https://nkdagility.com/resources/scrum/
Subscribe

Overview

Scrum is a Framework and a social technology for delivering adaptive solutions in complex environments. It is built on empiricism—transparency, inspection, and adaptation—and is designed to help teams deliver value iteratively and incrementally. Scrum is a framework that helps teams work together to solve complex problems and deliver high-value products. Its about planning.

First Principals

  1. Empiricism: Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known.
  2. Self-Organization: Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team.
  3. Collaboration: Scrum promotes collaboration among all roles to deliver the highest value.
  4. Value-Based Prioritization: The Product Owner is responsible for maximizing the value of the product resulting from the work of the Development Team.
  5. Time-Boxing: Time-boxed events are used to create regularity and to minimize the need for meetings not defined in Scrum.
  6. Iterative Development: Scrum uses an iterative, incremental approach to optimize predictability and control risk.
  7. Incremental Delivery: Scrum delivers a potentially releasable product increment at the end of each Sprint.
  8. Continuous Improvement: Scrum Teams continuously improve through the use of the Scrum Events and by inspecting and adapting the product, processes, and practices.

Values

  1. Commitment: The Scrum Team commits to achieving the Sprint Goal.
  2. Focus: The Scrum Team focuses on the work of the Sprint and the goals of the Scrum Team.
  3. Openness: The Scrum Team and its stakeholders agree to be open about all the work and the challenges with performing the work.
  4. Respect: Scrum Team members respect each other to be capable, independent people.
  5. Courage: The Scrum Team has the courage to do the right thing and work on tough problems.

Accountabilities

  1. Scrum Team – Consists of a Product Owner, Developers, and a Scrum Master. The Scrum Team is self-managing and works collaboratively to deliver a usable Increment every Sprint.
  2. Product Owner : Accountable for maximising product value and managing the Product Backlog.
  3. Developers: Accountable for delivering usable Increments that meet the Definition of Done.
  4. Scrum Master : Accountable for Scrum effectiveness, causing the removal of impediments, and coaching the team.

Events

  1. Sprint: A fixed-length iteration (≤ 1 month) in which the team creates at least one usable Increment.
  2. Sprint Planning: Based on the Product Goal, the team plans the work for the Sprint.
  3. Daily Scrum: Based on the Sprint Goal the Developers plan work for the next 24 hours.
  4. Sprint Review: Based on the current state of the Product, current business conditions, and possible future business conduction the Scrum Team plans whats next.
  5. Sprint Retrospective: The Scrum Team plan on how they will change their system to improve the next Sprint.

Artifacts

  1. Commitments
    • Product Goal: The long-term vision for the product.
    • Sprint Goal: A tactical objective for the Sprint.
    • Definition of Done (DoD): A quality standard for completed work.

Key Accountabilities

Scrum is lightweight, but difficult to master. It is not a process or methodology but a framework that helps teams navigate complexity through empirical process control.

Views:
Subscribe
Scrum

Getting Started with the Definition of Done (DoD). Every team should define what is required, what criteria must be met, for a product increment to be …

Tags Tags (28)
Read more about Definition of Done
Scrum

Explains why true Scrum requires real team agency, not just self-management in name, and how lacking agency leads to ineffective, ritualistic Agile …

Blog Blog
Read more about The Role of Agency in Scrum: Why Self-Management Without Agency is a Lie
Scrum

The end of a Sprint is a checkpoint for review and adaptation, not a deadline. Focus on flow, learning, and continuous improvement over strict task …

Signals Signals
Read more about Stop treating the end of the Sprint like a finish line
Scrum

Maximise team alignment and adaptability with the Daily Scrum. Inspect progress, adapt plans, and ensure focus on the Sprint Goal.

Tags Tags (3)
Read more about Daily Scrum
Scrum

NKD Agility helped the Ghana Police Service drive organisational change using Scrum, enabling continuous improvement, transparency, and local …

Case-Studies Case-Studies
Read more about Policing for the 21st Century: How NKD Agility Enabled Organisational Change in the Ghana Police Service
Scrum

Explains why consistent delivery of usable increments is essential in Scrum, highlighting the Scrum Master's accountability for ensuring transparency, …

Signals Signals
Read more about Scrum is built on empiricism—transparency, inspection, and adaptation
Scrum

The Scrum Team is a defined accountability within Scrum, composed of a Scrum Master, Product Owner, and Developers working together toward a shared …

Tags Tags (81)
Read more about Scrum Team
Scrum

Explains how true self-management in Scrum requires active, disciplined effort from Product Owners, Scrum Masters, and Developers, not chaos or lack …

Signals Signals
Read more about We hear self-managing teams so often it become a cliché
Scrum

Explores key qualities of an effective Scrum Master, focusing on team empowerment, backlog management, collaboration, and removing organisational …

Signals Signals
Read more about What Makes an Effective Scrum Master Beyond Meeting Facilitation
Scrum

Professional Scrum is a disciplined ethos of empiricism, accountability, and continuous improvement that transcends the Scrum framework.

Tags Tags (193)
Read more about Professional Scrum
Scrum

Inspecting and adapting the increment to ensure transparency and stakeholder feedback.

Tags Tags (10)
Read more about Sprint Review
Scrum

Explains how the Scrum Master is accountable for enabling effective product delivery, fostering team success, and ensuring each sprint produces a …

Blog Blog
Read more about The Scrum Master is accountable for Delivery
Scrum

Explains how a Scrum Master drives team improvement, removes obstacles, and leads organisational change, going far beyond basic facilitation or …

Signals Signals
Read more about The True Role of a Scrum Master Beyond Facilitation
Scrum

Explains how Scrum Masters are naturally chosen by teams based on trust, experience, and leadership, highlighting the importance of peer selection …

Signals Signals
Read more about How Top Scrum Masters Are Selected by Their Teams
Scrum

Commitment, courage, focus, openness, and respect as the foundation of Scrum.

Tags Tags (6)
Read more about Scrum Values
Scrum

Explains how Scrum reveals team dysfunctions by clarifying roles and accountability, highlighting its purpose to expose issues that hinder value …

Signals Signals
Read more about Scrum is not a process it is a social technology designed to expose dysfunction
Scrum

Explores how Product Owners can drive strategy, maximise value, and lead Scrum teams effectively, highlighting the need for empowerment beyond basic …

Signals Signals
Read more about Empowering Product Owners as Strategic Leaders in Scrum Teams
Product Development

The Product Owner is an accountability in Scrum, responsible for maximising product value through effective backlog management and stakeholder …

Tags Tags (54)
Read more about Product Owner
Scrum

A clear summary of Scrum’s framework, roles, events, artefacts, and values, explaining how teams use Scrum to deliver value and adapt to complex …

Guides Guides
Read more about The Scrum Guide
Scrum

Explains Scrum’s core values, roles, artifacts, and events, highlighting how they support teamwork, transparency, and adaptability in managing complex …

Videos Videos
Read more about Unlocking Scrum Success: A Comprehensive Guide to Values, Roles, Artifacts, and Events
Product Development

The Scrum Master is an accountability in Scrum, responsible for enabling the effectiveness of the Scrum Team and fostering continuous improvement …

Tags Tags (96)
Read more about Scrum Master
Scrum

Explains how Scrum supports continuous flow and agility by prioritising Sprint Goals, Done increments, CI/CD practices, and outcomes over rigid sprint …

Signals Signals
Read more about Scrum doesn’t stop you from optimising flow
Scrum

Explains how self-managing teams in Scrum need structure and leadership, clarifying the Scrum Master's role in maintaining clarity, alignment, and …

Signals Signals
Read more about “Teams are self-managing
Scrum

Explores Scrum Team effectiveness, emphasising that consistent delivery is essential and highlighting the Scrum Master's accountability for enabling …

Signals Signals
Read more about let-us be blunt—if a Scrum Team isn’t delivering, is it effective
Scrum

Scrum can drive organisational change, not just product features, by using backlogs, teams, and feedback to enable real, evidence-based agility across …

Signals Signals
Read more about Scrum isn’t limited to building features
Scrum

Answers common questions about integrating design and UX work into Scrum Sprints, clarifying why dedicated Design Sprints aren’t needed and how to …

Signals Signals
Read more about Design Sprints in Scrum: Common Questions and Practical Insights
Leadership

Argues that the Scrum Master role requires proven mastery and real-world experience, not entry-level skills or certifications, and should be earned …

Blog Blog
Read more about There Is No Such Thing as a "Junior" Scrum Master
Scrum

Scrum Masters are most effective when they combine leadership skills with technical, business, and organisational mastery to support teams, Product …

Blog Blog
Read more about Great Scrum Masters Need Technical, Business, and Organisational Mastery
Product Development

Scrum teams must deliver working software to real users every Sprint; true progress is measured by delivery to production, not just by completing …

Blog Blog
Read more about Delivery is the only Measure of Progress in Scrum
Scrum

Professional Scrum Teams prioritise software quality, accountability, and continuous improvement, ensuring each release is reliable, defect-free, and …

Blog Blog
Read more about Professional Scrum teams build software that works
Product Development

Explains the difference between subjective goals and the objective Definition of Done in Scrum, highlighting how clear, measurable criteria ensure …

Blog Blog
Read more about Definition of Done - Objective vs Subjective
Scrum

Covers key concepts of Sprint Reviews, interactive workshop delivery using Teams and Mural, technical challenges faced, participant feedback, and …

Videos Videos
Read more about Free Workshop 04: Introduction to Sprint Reviews [Review & Retrospective]
Product Development

Explains how Scrum teams can strategically allow unfinished work to flow across Sprint boundaries, enhancing throughput, responsiveness, and …

Blog Blog
Read more about Work can flow across the Sprint boundary
Scrum

Technical skills are not required to be a Scrum Master, but understanding technical, business, and organisational contexts helps Scrum Masters better …

Blog Blog
Read more about Are technical skills required to be a Scrum Master?
Scrum

Many Scrum Masters lack essential skills and experience, leading to poor agile outcomes. True competence requires deep knowledge, practical …

Videos Videos
Read more about The Competence Crisis in Scrum Master Roles: A Call for Excellence
Scrum

Explains how to create, apply, and improve a Definition of Done (DoD) in Scrum to ensure software quality, transparency, and consistent delivery of …

Blog Blog
Read more about Getting started with a Definition of Done (DoD)
Scrum

Explores how practical use of Scrum fosters adaptability and resilience in teams, highlighting the value of flexibility over rigid rules in complex …

Blog Blog
Read more about Pragmatism crushes Dogma in the wild
Scrum

Explains why regular backlog refinement is essential in Scrum, how to make backlog items ready for Sprint Planning, and ways to measure effective …

Blog Blog
Read more about If your backlog is not refined then you are doing it wrong
Scrum

Accountability in Scrum requires real agency; without the power to act, roles like Product Owner and Scrum Master become ineffective and …

Signals Signals
Read more about let-us be blunt
Scrum

Many agile transformations restrict team autonomy, leading to control and compliance instead of true ownership, adaptability, and meaningful …

Signals Signals
Read more about Here the dirty secret behind many agile transformations
Scrum

Intensive five-day course for software developers covering Scrum, Visual Studio 2010, .NET, and Agile practices through hands-on team sprints and …

Blog Blog
Read more about Professional Scrum Developer (.NET) Training in London
Scrum

Balancing backlog refinement prevents wasted effort and chaos. Aim for just enough detail so developers can plan sprints confidently without …

Signals Signals
Read more about Too much refinement wastes time
Scrum

Explores why team autonomy in Scrum must be balanced with alignment to strategic goals, highlighting the role of clear objectives and leadership in …

Signals Signals
Read more about Everyone loves to shout give teams autonomy
Scrum

Explains why a clear Definition of Done is vital in Agile and Scrum for quality delivery, transparency, and risk mitigation, with tips for team …

Videos Videos
Read more about Unlocking Success in Agile: Why Your Definition of Done is Essential for Quality Delivery
Product Development

Explains why rejecting individual backlog items at Sprint Review is a misconception, highlighting Scrum’s focus on learning, collaboration, and …

Blog Blog
Read more about The fallacy of the rejected backlog item
Scrum

The Definition of Done can evolve to improve quality but should not be weakened or vary per backlog item. Consistency ensures transparency and …

Blog Blog
Read more about Can the Definition of Done change per Sprint?
Scrum

Finding a skilled Scrum Master is challenging; true effectiveness requires deep Scrum knowledge, coaching ability, and alignment with your team's …

Signals Signals
Read more about Hiring a Scrum Master is hard
Scrum

Explains why Sprints are valuable even with continuous delivery, highlighting benefits for planning, feedback, communication, and predictability in …

Blog Blog
Read more about I do continuous deliver, why should I Sprint?
Leadership

Explores how Scrum Masters and Product Owners balance leadership, authority, and team autonomy to ensure accountability, effective self-management, …

Blog Blog
Read more about Balance of Leadership and Control in Scrum
Scrum

Explores why Product Owners’ authority is accepted while Scrum Masters’ is questioned, highlighting the need for clear authority to ensure team …

Signals Signals
Read more about No one questions a Product Owner authority
Scrum

Explores why Scrum Masters need authority, not just influence, to enforce Agile practices, remove blockers, and ensure teams follow Scrum for true …

Signals Signals
Read more about Scrum Masters: Why Influence Alone May Not Be Enough
Scrum

Guidance for running effective Daily Scrum meetings, focusing on collaboration, transparency, and actionable planning to help teams achieve their …

Recipes Recipes
Read more about Daily Scrum Recipe
Scrum

A real-world account of guiding a new Scrum team through their first sprint, covering estimation, story points, sprint planning, and handling …

Blog Blog
Read more about My first Scrum team in the wild
Scrum

UX is integrated into Scrum, not handled separately. Design and validation happen within Sprints and backlog refinement, supporting continuous, …

Signals Signals
Read more about In Scrum, we don’t do UX separately
Scrum

Explores common misconceptions about Scrum Masters, clarifies their true accountabilities, and highlights the importance of principles, competence, …

Videos Videos
Read more about Unpacking the Scrum Master Role: Moving Beyond Misconceptions to True Accountability
Scrum

Guides a 160-minute Sprint Review workshop using Liberating Structures to inspect product progress, gather feedback, and plan next steps for Scrum …

Workshops Workshops
Read more about Sprint Review #1
Scrum

Learn how to customise Azure DevOps to support Scrum teams, manage backlogs, plan sprints, and improve agile workflows with practical setup and …

Videos Videos
Read more about Maximise Your Scrum Process: Leveraging Azure DevOps for Agile Success
Scrum

Explains how a Product Owner can manage Sprint Planning across multiple Scrum teams in Nexus by delegating, using area or team owners, and maintaining …

Blog Blog
Read more about In Nexus with 5 Scrum teams, how can the Product Owner attend all Sprint Planning events?
Scrum

Explains when a Scrum Master should remove impediments, focusing on team self-sufficiency, true impediments, and supporting team growth within Scrum …

Blog Blog
Read more about Should the Scrum Master always remove impediments?
Scrum

Explores and corrects common misconceptions about Scrum, clarifying its true principles, events, planning, and governance to help teams adopt Agile …

Videos Videos
Read more about Debunking the Top 5 Myths About Scrum: Unlocking Agile Success in Your Organisation

Our Happy Clients​

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.​

CR2

NIT A/S

Lockheed Martin Logo

Lockheed Martin

Ericson Logo

Ericson

Cognizant Microsoft Business Group (MBG) Logo

Cognizant Microsoft Business Group (MBG)

Slaughter and May Logo

Slaughter and May

Teleplan Logo

Teleplan

Higher Education Statistics Agency Logo

Higher Education Statistics Agency

Hubtel Ghana Logo

Hubtel Ghana

Capita Secure Information Solutions Ltd Logo

Capita Secure Information Solutions Ltd

Brandes Investment Partners L.P. Logo

Brandes Investment Partners L.P.

Jack Links Logo

Jack Links

Philips Logo

Philips

Qualco Logo

Qualco

Boeing Logo

Boeing

Slicedbread Logo

Slicedbread

Deliotte Logo

Deliotte

Healthgrades Logo

Healthgrades

Department of Work and Pensions (UK) Logo

Department of Work and Pensions (UK)

Nottingham County Council Logo

Nottingham County Council

Washington Department of Enterprise Services Logo

Washington Department of Enterprise Services

Washington Department of Transport Logo

Washington Department of Transport

Ghana Police Service Logo

Ghana Police Service

Royal Air Force Logo

Royal Air Force

Bistech Logo

Bistech

Brandes Investment Partners L.P. Logo

Brandes Investment Partners L.P.

Workday Logo

Workday

Freadom Logo

Freadom

Boeing Logo

Boeing

Qualco Logo

Qualco