Learn Scrum the hard way by investigating real Agile dysfunctions.
Instead of memorizing Scrum theory, this project lets you solve investigative cases inspired by real situations that Scrum Masters and Agile teams face every day.
Analyze clues, spot anti-patterns, and discover what really went wrong in the Sprint.
Because Agile is not learned from slides, it is learned by recognizing dysfunctions in real teams.
Scrum Training App is an open‑source gamified learning platform designed to help people understand Scrum anti‑patterns and Agile team dysfunctions.
Each case works like a detective investigation:
🕵️ A Scrum team faces a mysterious problem
📂 Evidence is revealed step by step
🧠 The player analyzes the clues
✅ The solution reveals the real Agile anti‑pattern
The goal is to train critical thinking and observation, not memorization.
Most Scrum training focuses on rules of the framework.
But real teams rarely fail because they don't know Scrum.
They fail because of subtle dysfunctions such as:
• silent Product Owners
• stakeholder interference
• endless refinements
• fake Definition of Done
• cargo‑cult Scrum practices
• teams delivering output but not value
This project simulates real scenarios Scrum Masters encounter in real teams.
This project is an open‑source tribute to the brilliant game:
https://murderinthesprint.com/
created by Angelo Sala and Marco D'Andrea.
The goal is not to replicate the original work but to create a community‑extendable open platform where new Agile investigation cases can be created and shared.
Here are some examples of investigations you may encounter.
The Sprint Review ends in five minutes.
Stakeholders say nothing.
The Product Owner quickly accepts the Increment.
Everything looks fine... but something feels wrong.
Can you identify the real anti-pattern?
The team spends hours refining backlog items every week.
Stories become extremely detailed before development starts.
Developers feel safe.
But delivery is getting slower and slower.
What is the underlying dysfunction?
Every Sprint ends exactly as planned.
All stories are completed.
Velocity is stable.
But customers never notice any improvement.
Is this really a healthy Scrum team?
Playing the cases helps recognize common Agile problems:
• Product Owner anti‑patterns
• Scrum Master dysfunctions
• Sprint Review failures
• Refinement misunderstandings
• Delivery illusions
• team dynamics issues
Each investigation ends with a clear explanation of the root cause.
This repository includes an AGENTS.md file designed to help AI coding agents understand the project.
It provides structured guidance about:
• project architecture
• coding conventions
• project intent
• contribution rules
This allows tools like:
- Cursor
- GitHub Copilot
- Claude Code
- AI development agents
to interact with the repository safely and consistently.
Clone the repository:
git clone https://github.com/bigmoby/scrum-training-app.git
cd scrum-training-appInstall dependencies:
npm installRun the development server:
npm run devThe development server will typically be available at:
For full development and deployment documentation see:
➡️ DOC.md
This project is designed to be community‑extendable.
Possible contributions include:
• new investigation cases
• new Agile anti‑pattern scenarios
• UX improvements
• game mechanics
• translations
If you have an Agile story worth investigating...
turn it into a case.
This is an active open‑source project. We are always open to people who want to use the code or contribute to it.
Contribution guidelines are available here:
- silent Product Owners
- stakeholder interference
- endless refinements
- fake Definition of Done
- cargo-cult Scrum practices
- teams delivering output but not value
If you like the idea:
⭐ Star the repository
🧠 Suggest new investigation cases
🤝 Contribute improvements
Open source grows through community experimentation.
If you find this project useful and want to support its evolution:
Licensed under the Apache License Version 2.0