Empiricism
Sprint Planning – Why
How does a Product Owner facilitate discussion on the value needed from the upcoming Sprint?
Agile IQ®
Inspect & Adapt
Influencing Behaviour. Secondary Factor.
Overview
Inspect and adapt are actions at the heart of empiricism. In practice, this means working in a fact-based, experience-based, and evidence-based manner, instead of making decisions based on only documentation of a solution or a plan.
Scrum implements an empirical process where progress is based on observations of specific artefacts, not assumptions about plans and future tasks, specifically:
- Product Backlog: Represents the state of development of a product or service toward strategic goals. Teams inspect it at Sprint Planning and create (adapt) a Sprint Backlog.
- Sprint Backlog: The state of delivery of value in the Sprint, the plan, and progress toward the Goal.
- Increment: Work that is of sufficient quality (meets the Definition of Done) to potentially hand over to the customer. Teams inspect Increments at the Sprint Review and elicit feedback from customers which is documented in the Product Backlog.
Levels of empiricism
Each layer of an agile organisation has the opportunity apply empiricism – to inspect real progress, pivot to change, and adapt future delivery plans, based on evidence.
- Portfolio Backlog: Yearly planning, quarterly review.
- Program Backlog: Quarterly planning, quarterly review.
- Team Backlog: 2-weekly planning, 2-weekly review.
Agile Events & Empiricism
Empiricism
Sprint Planning – What
How does a team decide on what items will become part of their Sprint?
Empiricism
Daily Scrum
Inspecting progress toward the Sprint Goal empowers a team to adapt its Sprint Backlog
Empiricism
Sprint Review
Go beyond a demo and inspect the increment to get feedback on the direction for the next Sprint
Empiricism
Retrospective
Inspect the team – people, process and tools – and decide on improvement actions
Empiricism
Sprint Planning – How
How does a team decide on what items will become part of their Sprint?
Empiricism
Mastering Agile Events
Learn how to get the most out of inspecting and adapting using Scrum’s 5 key events.
Empiricism
Sprint Planning Basics
What are the essential parts of Sprint Planning and how do you make it effective?
Tools for empiricism: OKRs
OKRs provide Product Managers a powerful mechanism to inspect value-based metrics in order to understand:
- Investment in existing products
- Investment in new products and services
- Investment in capability – improved pivot, decreased costs, more throughput
Learning Areas on EBM
EBM
Using Evidence Based Management (EBM) for Reporting
Agile KPIs and OKRs created through using EBM help focus people on value-based metrics, impacts and outcomes.
EBM
EBM and Agile Product Management
More than ever, organisations must focus on their investments and efforts. EBM is designed to drive decisions for agile product management.
EBM
Video: Making OKRs better with EBM
Objectives and Key Results (OKRs) are a powerful tool for setting and measuring goals, but like all power tools, they can come with great responsibili
EBM
Using EBM to measure steps toward the Product Goal
Alignment to strategic outcomes is critical for any organisation. EBM helps leaders measure steps toward these goals.
EBM
Working with the Product Goal
Product Goals are an important part of creating a tangible relationship between the work we do today and the business strategy.
Backlog Management
Objectives vs Deliverables
Start setting objectives over thinking about fixed deliverables and requirements
