Scrum
While studying for and becoming a Certified Professional Scrum Master through scrum.org, I did a bit of writing - here's some notes!
TLDR
Scrum is a "framework" with a few parts
- Theories & Values: The "why"
- A Team Description: 3 Roles
- Events: Things that happen (a few hours per week)
- Artifacts: 4 tangible objects
Scrum is intended to help teams and organizations create value incrementally in a complex environment.
There are just a few concrete details with lots of room to embody the theories & values that support the events, artifacts, and team structure. Transparency, Inspection, Adaptation, Respect, Courage, Empiricism, Lean Thinking... these things are so much more than Scrum, but without those things the implementation of Scrum can leave a room feeling deflated, powerless, annoyed, overburdened, and disinterested.
A Checklist For Implementing Scrum
An overview of the elements that are part of scrum
On Organizational Scrum Advocacy & Adoption
Ways to keep the values alive
The Artifacts
The Product Backlog, Sprint Backlog, Increment, and Definition of Done
The Ceremonies
The Sprint, Sprint Planning, Sprint Review, Sprint Retrospective and Daily Scrum
The Increment
The tool that can transform ideas into releasable content
The Scrum team
The 3 roles - Scrum Master, Product Owner, and Developers
Scrum Theories
Empiricism, Lean Thinking, Transparency, Inpsection and Adaptation keep Scrum honest
Scrum Values
Commitment, Respect, Courage, Opennes and Focus