Scrum
Content to think better about AI, product, and technology.
Team
The fundamental unit of Scrum is a small team of people, a Scrum Team. The Scrum Team consists of a Scrum Master, a Product Owner, and the Developers
Team: Scrum Master
The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization
Scrum Pillars
You don't learn by thinking. You learn by doing and observing. Knowledge is information; learning is action.
Scrum Values
Scrum's success lies in your ability to implement it by opening yourself up to five values: commitment, focus, openness, respect, and courage. These values direct the work you do, the actions you take, and the behavior you display.
When To Use Scrum?
In this article, I want to invite you to review the context for which Scrum is most suitable.
Artifact: Product Backlog
The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team
Artifact: Sprint Backlog
The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how)
Artifact: Increment
An Increment is a concrete stepping stone toward the Product Goal.
Event: Sprint
The Sprint is a container for all other events… Sprints are the heartbeat of Scrum, where ideas are turned into value.
Event: Sprint Planning
The Sprint Planning initiates the Sprint by laying out the work to be performed for the Sprint
Team: Product Owner
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team
Event: Sprint Review
The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations