Resources · glossary
Scrum
A specific form of agile work: fixed cycles of a few weeks, three roles and four recurring meetings. It is the most popular one, so it is often confused with agile as a whole.
- Scrum framework
- Scrum methodology
- agile Scrum
- 01
Three roles
The product owner decides what matters more. The development team decides how to do it and how much fits into a cycle. The Scrum master looks after the process and removes obstacles, and is neither the project manager nor the team's boss.
- 02
Four meetings
Planning at the start of the cycle, a short daily check-in, a review of the results with the client, and a retrospective on the way of working itself. The last one tends to be dropped first, and that is usually when the process stops improving.
- 03
The client's role
Real and regular. Without someone on your side who sets priorities and signs off the results every two weeks, Scrum degenerates into a schedule with extra meetings.
- 04
When it is overkill
With a two-person team and a six-week project, the full ceremony costs more than the order it brings. A priority list and a weekly review are enough.
Related terms
- AgileAn approach in which a project is built in short cycles, each ending with something that works, instead of one release after six months. It assumes the requirements will change along the way.
- Product ownerThe person on the client's side who decides the order of work and signs off the results. One person with the authority to decide, not a committee.
15 minutes. No sales pitch.
A term in a proposal sounds foreign? In 15 minutes we explain what it means for your project.