Skip to main content

2 min read

Scrum Core Guide

Scrum in one view​

Scrum is a lightweight framework for solving complex problems through short, iterative cycles (sprints), transparency, and adaptation.

Read more at Atlassian: What is Scrum?

Roles (Accountabilities)​

  • Product Owner: maximizes product value and backlog clarity.
  • Scrum Master: improves team effectiveness and removes systemic blockers.
  • Developers: own delivery quality and sprint execution.

Read more at Atlassian: Scrum master

Artifacts and Commitments​

  • Product Backlog with Product Goal
  • Sprint Backlog with Sprint Goal
  • Increment with Definition of Done (DoD)

Good Scrum keeps these artifacts explicit and current, so planning and trade-offs are fast and evidence-based.

Read more at Atlassian: Scrum artifacts

Core Events (and why they matter)​

  • Sprint Planning: align on sprint goal and scope.
  • Daily Scrum (Standup): re-plan daily around sprint goal.
  • Sprint Review: inspect increment and collect stakeholder feedback.
  • Sprint Retrospective: inspect process and improve team system.
  • Backlog Refinement (ongoing): keep upcoming work ready and right-sized.

Read more at Atlassian: Scrum ceremonies

Sprint Mechanics that keep quality high​

  • Keep sprint goals specific and measurable.
  • Slice stories vertically (end-to-end value).
  • Enforce WIP discipline inside the sprint.
  • Make DoR/DoD explicit and visible.

Read more at Atlassian: Sprints

Scrum Metrics (Use, don't worship)​

  • Velocity: planning aid, not a productivity scoreboard.
  • Sprint burndown/burnup: progress trend, scope clarity.
  • Predictability: commitment vs completion over time.
  • Cycle/lead time signals: identify flow bottlenecks.
  • Defect escape and rework trends: protect quality.

Read more at Atlassian: Scrum metrics

Scrum vs Agile vs Kanban (quick distinction)​

  • Agile: umbrella mindset and principles.
  • Scrum: one Agile framework with timeboxes and prescribed events.
  • Kanban: flow method focused on throughput and WIP control.

Many teams blend Scrum and Kanban when it improves outcomes.

Read more at Atlassian: Agile vs. Scrum

Common Scrum failure modes​

  • Planning around utilization instead of outcomes.
  • Unstable sprint scope from unmanaged interrupts.
  • Retrospectives with no follow-through.
  • Weak backlog quality causing churn and carryover.
  • Treating Scrum Master as project admin instead of system coach.

Read more at Atlassian: Agile retrospectives

Pragmatic working agreements​

  • Single sprint goal; avoid unrelated work unless urgent and explicit.
  • Add an interrupt lane only when needed; cap its WIP.
  • Track retrospective actions in the sprint backlog.
  • Make stakeholder review participation a non-negotiable habit.

Read more at Atlassian: Scrum with Jira tutorial

Further reading on Atlassian​