Learn the Scrum Framework
What Is Scrum?
Scrum is a lightweight framework for generating value through adaptive solutions to complex problems. It has been used since the 1990s and is now applied well beyond software development.
The framework is simple to understand, but applying it well requires transparency, inspection, adaptation, and disciplined collaboration.
Scrum (n): A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.
Scrum is:
- Lightweight
- Simple to understand
- Extremely difficult to master
How Does Scrum Work?
Scrum organizes work in Sprints of one month or less. Each Sprint includes Sprint Planning, Daily Scrums, a Sprint Review, and a Sprint Retrospective. The Scrum Team creates a usable Increment every Sprint and uses frequent feedback to adapt the Product Backlog, the plan, and the way the team works.
Scrum defines three accountabilities: Product Owner, Scrum Master, and Developers. It also defines three artifacts: the Product Backlog, Sprint Backlog, and Increment. Each artifact includes a commitment that improves focus and transparency.
- Scrum is built on five core values: focus, courage, commitment, openness, and respect.
- Scrum has three distinct accountabilities / roles: Scrum Master, Product Owner, and Developers.
- Scrum is not an artifact-heavy process, but three artifacts are crucial to success: Sprint Backlog, Product Backlog, and the Increment. Additionally, many teams still use Burndown Charts, even though they are not officially part of Scrum.
- Scrum is organized into four key activities that occur during every Sprint: Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Most teams also add Product Backlog Refinement, a form of continuous release planning, to each Sprint.
Implementing Scrum
Scrum is elegantly deceptive. It is one of the easiest frameworks to understand yet is one of the hardest frameworks to implement well. Scrum’s inherent simplicity can make it seem easy to do, when in reality it can take years to master. Why? Because implementing Scrum correctly requires teams and organizations to make changes in the way they work and think about work:
- Develop an understanding of Scrum’s underlying values
- Undergo a shift in mindset
- Plan for change to occur–and adapt when it does
- Deal with newly exposed or emerging issues
- Incorporate agile engineering practices, including XP
Read on to find out more about Scrum’s sprint cycle. Or to get a more in-depth look at Scrum, Agile, XP and more, consider attending a public or private course.