Scrum in GIRAF¶

This page explains how GIRAF implements Scrum, framed through the three pillars of empiricism. For the complete Scrum framework definition, see the official Scrum Guide.

The Three Pillars of Empiricism¶

Scrum is founded on empiricism—making decisions based on observation and experience rather than upfront planning. Three pillars support this approach. For more details, see The Three Pillars of Empiricism on Scrum.org.

Transparency¶

All aspects of work must be visible to those responsible for the outcome.

How GIRAF implements transparency:

GitHub Issues and Projects provide visibility into all work items
Scrum of Scrums ensures information flows between PO/SM groups and development teams
Sprint Backlog is shared with all team members before Sprint Planning
Pull requests and code reviews make code changes visible to the entire team

Inspection¶

Scrum artifacts and progress must be frequently inspected to detect problems early.

How GIRAF implements inspection:

Sprint Planning: Teams inspect and estimate issues collaboratively
Sprint Review: Teams demonstrate completed work and gather feedback
Pull Request Reviews: Code is inspected before merging
PO group conducts usability testing to inspect product quality

Adaptation¶

When inspection reveals issues, the process or product must be adjusted promptly.

How GIRAF implements adaptation:

Sprint Retrospective: Teams reflect on what went well and what to improve
Process changes are communicated at the start of each Sprint Planning
Sprint Backlog can be adjusted based on Planning Poker outcomes
Teams can request additional issues if capacity allows

Learn More¶

Sprint Events — Detailed guide to Sprint Planning, Review, and Retrospective
Roles — PO, SM, and Developer responsibilities
Code Workflow — From issue to merged PR