Scrum

What is Scrum?

Q: What is Scrum?

Scrum is the most widely used agile framework in the world for teams that need to deliver value incrementally in complex, uncertain environments. Scrum defines three accountabilities (Scrum Master, Product Owner and Developers), five events and three artifacts that sustain short cycles of inspection and continuous adaptation. It is lightweight to describe and difficult to master — and it is the foundation of the Scrum Alliance certifications K21 has been teaching since 2013.

Scrum is the most widely used agile framework in the world for teams that need to deliver value incrementally in complex, uncertain environments. Scrum defines three accountabilities (Scrum Master, Product Owner and Developers), five events and three artifacts that sustain short cycles of inspection and continuous adaptation. It is lightweight to describe and difficult to master — and it is the foundation of the Scrum Alliance certifications K21 has been teaching since 2013.

In practice

A Scrum team organizes its work in Sprints — fixed cycles of up to four weeks with a clear, measurable goal. Each Sprint, the team plans what to build, syncs daily in the Daily Scrum, delivers one or more product increments, gathers stakeholder feedback in the Sprint Review and improves its own process in the Sprint Retrospective. The Product Owner keeps the backlog ordered by business value, the Scrum Master makes sure the framework is actually applied, and the Developers turn backlog items into increments that are ready to use. The result is high predictability without losing the ability to change direction whenever needed.

What happens when it is missing

Without Scrum (or an equivalent empirical framework), teams deliver in long cycles with no intermediate feedback, discover problems too late, and depend on detailed plans made before the uncertainty is resolved. Replanning gets expensive, rework explodes, and the relationship with the business turns into a sequence of broken date promises. The absence of frequent inspection and adaptation is exactly what makes projects stall in fixed-scope mode.