Scrum in one sentence
A small team delivers an improved version of the product at fixed, short intervals — and learns from each cycle to improve the next one.
The three roles
The Product Owner
Carries the product vision and orders the backlog by value. They decide what, never how.
The Scrum Master
Guardian of the framework: protects the team from interruptions and removes blockers. Neither a project manager nor a boss — a facilitator.
The development team
Three to nine people, cross-functional, who collectively commit to the sprint's scope.
The events of the cycle
Sprint planning
At the start of each sprint: choose a goal and the tasks that serve it, based on past velocity. This is exactly what the FluidOps Scrum demo shows.
The daily stand-up
Fifteen minutes, standing, three questions: what did I finish? what's blocking me? what am I doing next?
The sprint review
Demo the result to stakeholders: real feedback, not reporting.
The retrospective
The team looks at how it works: one strength, one weakness, one improvement commitment.
The artifacts, or how Scrum makes work tangible
- The product backlog: all ideas and needs, ordered by value.
- The sprint backlog: the subset committed to for the current sprint.
- The increment: what's actually finished and delivered at the end of the sprint.
Velocity — effort points completed per sprint — becomes your forecast capacity, visible in FluidOps's sprints module.
Common pitfalls
Sprints that are too long (you lose the feedback loop), a backlog that's never re-prioritized, a retro that changes nothing. The fix fits in one sentence: rituals serve progress, not the other way around.