Skip to content
ScrumMastered logo
  • Corporate clients
    • Private Agile & Scrum Training
    • Agile Consulting
    • Case Studies
  • Courses
    • Upcoming live public classes
    • Jira for Scrum Masters
    • Scrum Master (PSM Iâ„¢) Exam Prep Certification Course
    • Fundamentals of Agile Course
  • Resources
    • Wiki
    • Start here
    • Freebies
    • The Agile Audit Podcast
    • Premium Downloads & Courses
  • Blog
  • About
  • Corporate clients
    • Private Agile & Scrum Training
    • Agile Consulting
    • Case Studies
  • Courses
    • Upcoming live public classes
    • Jira for Scrum Masters
    • Scrum Master (PSM Iâ„¢) Exam Prep Certification Course
    • Fundamentals of Agile Course
  • Resources
    • Wiki
    • Start here
    • Freebies
    • The Agile Audit Podcast
    • Premium Downloads & Courses
  • Blog
  • About
Shop

Scrum Framework Explained

  • Scrum Overview
  • Sprint Events
    • Sprint Retrospective
    • Sprint Review
    • Daily Scrum
    • Sprint Planning
  • Scrum Accountabilities / Roles
    • Scrum Master
    • Developers
    • Product Owner
  • Scrum Artifacts & Commitments
    • Sprint Goal
    • Sprint Backlog
    • Product Goal
    • Product Backlog
    • Definition of Done
    • Increment
  • Scrum Values
    • Value: Courage
    • Value: Respect
    • Value: Openness
    • Value: Focus
    • Value: Commitment
  • Pillars of Empiricism
    • Pillar: Adaptation
    • Pillar: Inspection
    • Pillar: Transparency

Useful Models

  • Use Kano Model to prioritize features
  • Psychological safety
  • Team Overestimating Their Knowledge – The Dunning-Kruger Effect
  • Cognitive Bias in Business
  • Shu-Ha-Ri Maturity Model
  • Tuckman’s Stages of Group Development
View Categories
  • Home
  • wiki
  • Scrum Framework Explained
  • Pillars of Empiricism
  • Pillar: Inspection

Pillar: Inspection

1 min read

💡 Once there is transparency, the team needs to inspect the information at hand frequently to make adjustments to their work. Inspection is just one side of the puzzle, as, without adaptation, inspection is a waste of time.

How do we inspect during each Scrum Event? #

Sprint Planning #

The team inspects their progress to date towards the Product Goal and the current Product Backlog. They inspect their Definition of Done as it gives a better understanding of the work to be done. They inspect the Product Backlog items that they want to bring into the next Sprint.

Daily Scrum #

Developers inspect progress towards the Sprint Goal since the previous Daily Scrum. They inspect impediments that have been identified and their tasks.

Sprint Review #

The team and stakeholders inspect the Increment created during the Sprint and how it contributed to the progress toward the Product Goal. They inspect the current Product Backlog, its order, and potential items that may be taken into the next Sprint to work on. The team inspects stakeholders’ feedback about the Increment.

Sprint Retrospective #

The team inspects how the last Sprint went. They inspect how effective they are when it comes to their interactions within the team and with people outside of the team, their tools and processes, their communication and relationships. They may also inspect the quality of the product through their Definition of Done.

Was this helpful?
Share This Article :
  • X
  • LinkedIn
Updated on April 4, 2024
Pillar: AdaptationPillar: Transparency

Powered by BetterDocs

Table of Contents
  • How do we inspect during each Scrum Event?
    • Sprint Planning
    • Daily Scrum
    • Sprint Review
    • Sprint Retrospective

Join 5000+ Agile practitioners around the world on their journey to building awesome teams.

ScrumMastered logo
Quick Links
  • Shop
  • Agile Consulting
  • Private Training
  • Scrum.org Classes
  • Blog
  • About & Contact
  • Terms & Conditions
  • Privacy Policy
Follow for More

All Rights Reserved by ScrumMastered © 2025