If you could teach just one thing about Scrum, what would it be?
I wouldn’t teach anything about Scrum if I only had one thing to teach, I would focus on the underlying principles that underpin scrum. Empiricism and navigating complexity effectively.
Empiricism.
When I’m delivering the APS course (Applying Professional Scrum) or talking to clients about how to effectively develop products in complex environments, I spend a great deal of time talking about the concept of empiricism, also known as Empirical Process Control.
Empiricism is built on three (3) pillars:
-
Inspection
-
Adaptation.
Transparency.
We make language, jargon, terms, and work transparent and we ensure it is visible to everyone relevant to the product. So, for example, if we use the term Minimum Viable Product, we ensure that everybody knows what that means, and what we, specifically, mean when we use that term.
So, a shared language and understanding is the first element of transparency.
The second element is making work transparent.
That may be:
-
Our working hypothesis.
-
What outcomes we are hoping to achieve.
-
What work is planned.
-
What criteria must be met before the work is considered complete.
-
What the flow of work throughout the system looks like.
-
What problems or impediments exist.
-
How the work is progressing.
-
What outcomes have been achieved.
And so forth.
Every element of the work is transparent and visible. Every element of our process and systems is transparent and visible. Every problem we experience and every impediment, large or small, is transparent and visible.
Inspection.
We frequently inspect our work.
In scrum, we have a daily scrum where the team inspect what has happened in the past 24 hours, discuss any impediments or problems that stand in the way, and articulate what is planned for the next 24 hours.
We inspect the work to ensure that we have met the definition of done. The criteria that must be met for the work to pass from one phase of development to another, or to be delivered to a client.
Our clients and product stakeholders inspect our working product near the end of each sprint and provide feedback and reviews. We also gather data through the sprint and inspect what the data is telling us about our processes, systems, and capabilities.
Finally, we inspect ourselves, as a team, and review our performance in the sprint retrospective with the objective of identifying what is working, what needs work, and how we are going to improve in the next sprint.
Frequent inspection with the purpose of gathering data, reviews, feedback, and evidence that we can learn from.
Adaptation.
This is the core of empiricism and agile.
The ability to adapt and respond, to opportunities and threats, to gaps in the market or disruption from competitors, from legislative disruption to international lockdowns for Covid.
Adapt and Respond. Adapt and Respond. Adapt and Respond.
The data we gather, the feedback and reviews we receive, and the evaluation / analysis we compile ourselves informs what needs to adapt. Informs what decisions we take moving forward. Informs what the next best step would be, given what we have learned and experienced.
These three things are the core elements of successfully navigating complexity and uncertainty.
Complexity
A key to understanding why agile is so successful at navigating complexity, is to understand what complexity is and why the traditional approaches don’t work in a complex space.
Traditional project management works just fine in a simple or complicated space because we have built the product hundreds of times before, and we have solved the problem some time ago, so we know that following a simple formula or pattern will deliver the outcome that we desire.
It’s known, tested, and proven.
In a complex space, we have never solved the problem or built the solution before. Added to this, there are so many unknown variables that could impact the success of our product or project, and we can’t possibly know what they are or where they will come from.
We don’t and can’t know what we don’t know.
Even if your brought the brightest, most experienced people in the organization into a room, they still wouldn’t know the answer. They still wouldn’t be guaranteed a positive outcome. These people would need to figure out the answer through trial and error.
They would need to design a hypothesis, run an experiment, validate what is true or untrue, and then design another hypothesis based on what they have learned. Small wins build momentum, and roadblocks encourage us to retreat to what we do know and develop a different hypothesis on how to progress from there.
Like a ship constantly correcting its course, in alignment with a compass, despite the changes in weather and currents. In agile, we have values and principles as guardrails, and we have a product vision and product goal and customer collaboration to guide us.
That is the primary difference between complicated and complex environments.
So, for me, this would be the primary skillset that a team need to acquire and develop. The ability to navigate complexity and uncertainty, using empiricism as a guide, to make the breakthroughs and solve the complex problems that they encounter.
Scrum is an agile framework that enables teams to do this, but it doesn’t solve the problem for you. In fact, scrum tends to reveal problems rather than solve them. It makes problems transparent and visible so that you can solve them and move forward.
If there was only one thing I could teach a product development team in a complex space, it would be this.
About NKD Agility
Naked Agility is an #agile consultancy that specializes in #scrumtraining, #agilecoaching and #agileconsulting to help teams evolve, integrate, and continuously improve.
We recognize the positive impact that a happy AND inspired workforce can have on customer experience, and we actively help organizations to tap into the power of creative, collaborative, and high-performing teams that is unique to #agile and #scrum environments.
If you are interested in #agiletraining, visit https://nkdagility.com/training/
If you have identified the need for #agilecoaching and #agileconsulting, visit https://nkdagility.com/agile-consulting-coaching/
We would love to work with you.
#scrum #agile #scrumteam #agileprojectmanagement #agileproductdevelopment #projectmanagement #productdevelopment #agilecoach #agileconsultant #agiletraining #scrumtraining #scrumorg
Smart Classifications
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.
What to read next
What is the most common Aha moment people have in a scrum course?
Most people in scrum courses realise the true value of empiricism and purpose behind scrum’s events and artefacts, shifting from rote …
What is the hardest part of working with a brand-new scrum team?
The biggest challenge with new scrum teams is overcoming misconceptions about scrum and shifting focus from process mechanics to core agile …
Why is Scrum so easy to understand but incredibly hard to master?
Explores why Scrum is challenging to master, highlighting cultural barriers, the importance of transparency, and the gap between …
Mastering Complexity in Scrum: Transform Your Team with Agile Product Strategy Insights
Learn how understanding complexity, empiricism, and key Scrum principles like transparency, inspection, and adaptation can boost Agile team …
What will you learn on the professional scrum master course?
Gain practical skills and deep understanding of the scrum master role, scrum theory, empiricism, team dynamics, and delivering value in …
Pragmatism crushes Dogma in the wild
Explores how practical use of Scrum fosters adaptability and resilience in teams, highlighting the value of flexibility over rigid rules in …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
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 …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
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 …
Kendall Guide - A System of Work for AI Adoption
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 …