Scrum is a lightweight yet highly effective framework for complex problem solving. According to the Scrum Guide 2020:
“Scrum is a lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems.”
Scrum is founded on empiricism (decisions based on experience and observation) and lean thinking (focusing on essentials, maximizing value). While originating in software development, Scrum is now applied in many industries, including product design, marketing, and organizational development.
Empirical Pillars
· Transparency: Work and progress must be visible and understood by all.
· Inspection: Regular checks of artifacts and outcomes.
· Adaptation: Adjusting practices and plans based on inspection findings.
Scrum Team
The Scrum Team is cross-functional and self-managing, composed of three accountabilities:
· Product Owner – accountable for maximizing value and ordering the Product Backlog.
· Scrum Master – servant leader and coach, fostering understanding and effective use of Scrum.
· Developers – professionals who create a usable Increment every Sprint.
Recommended size: 10 or fewer people. Smaller teams communicate better and are more productive.
Scrum Events
Scrum organizes work in a Sprint (1–4 weeks). Each Sprint begins immediately after the previous one ends.
· Sprint: Container event for all others, goal: a potentially releasable Increment.
· Sprint Planning: Defines the Why (Sprint Goal), What (Product Backlog Items), and How (implementation plan). Timebox: up to 8 hours for a one-month Sprint.
· Daily Scrum: 15-minute meeting of Developers to inspect progress and adapt the plan for the next 24 hours.
· Sprint Review: Increment is presented, feedback is gathered, and the Product Backlog is adapted. Timebox: up to 4 hours. Not an acceptance meeting.
· Sprint Retrospective: Team reflects on collaboration, processes, and tools to drive continuous improvement. Timebox: up to 3 hours.
Scrum Artifacts
· Product Backlog – Commitment: Product Goal
· Sprint Backlog – Commitment: Sprint Goal
· Increment – Commitment: Definition of Done
Common Misconceptions
· Scrum is only for IT: Wrong – Scrum applies wherever complex problems need solving.
· Scrum is a method: Wrong – Scrum is a framework, deliberately incomplete.
· Scrum Master = Project Manager: Wrong – the Scrum Master has no project management authority.
Practical Relevance
Scrum provides short feedback loops, clarity of roles, and transparency, enabling continuous learning. It supports organizations in acting adaptively and customer-focused in volatile and complex environments.
CALADE Perspective
CALADE applies Scrum both in standalone teams and within scaled frameworks (SAFe, LeSS, Nexus). Our coaches help organizations understand Scrum beyond the textbook – as a lever for cultural change, leadership at eye level, and sustainable transformation.
Related Terms
· Product Owner
· Scrum Master
· Sprint
· Product Backlog
· Agile Manifesto
· Empiricism
← back to list