🧱 Scrum

Scrum is an Agile framework designed to help teams deliver complex products through short, structured cycles of work called sprints. It provides clear roles, events, and artifacts so teams can inspect progress frequently and adapt quickly.

Core idea of Scrum

Scrum is built on three pillars:

Transparency — everyone sees the real state of the work
Inspection — frequent checks on progress and quality
Adaptation — adjust plans based on what is learned

It’s lightweight, but powerful when followed with discipline.

Scrum roles (the 3 accountabilities)

Product Owner — owns the product vision and prioritizes the backlog to maximize value.
Scrum Master — coaches the team, removes impediments, ensures Scrum is understood and applied.
Developers — build the product increment; cross‑functional and self‑managing.

These roles ensure clarity: what to build, how to build it, and how to improve the process.

Scrum events (the 5 ceremonies)

Sprint — 1–4 week cycle producing a usable increment.
Sprint Planning — team decides what to deliver and how to do it.
Daily Scrum — 15‑minute daily inspection of progress toward the Sprint Goal.
Sprint Review — stakeholders inspect the increment and give feedback.
Sprint Retrospective — team improves its process for the next sprint.

These events create a predictable rhythm of planning, building, checking, and improving.

Scrum artifacts (the 3 key deliverables)

Product Backlog — ordered list of everything the product needs.
Sprint Backlog — selected work for the sprint + plan to deliver it.
Increment — the working product output from the sprint.

Artifacts ensure transparency and alignment on what’s being built.

Why teams use Scrum

Delivers value early and often
Handles changing requirements gracefully
Encourages collaboration and ownership
Provides continuous feedback loops
Improves predictability through short cycles

Where Scrum struggles

Scrum can be challenging when:

Stakeholders cannot provide frequent feedback
Teams are not cross‑functional
The organization resists self‑management
Work is highly interrupt‑driven (support, ops)

Scrum = roles + events + artifacts working together inside short, iterative cycles to deliver value and continuously improve.