Scrum
- Resources
- First introduced in
The New New Product Development Game | Harvard Business Review
in 1986
- Built-in instability
- Self-organizing teams
- Overlapping development phases
- Multi-learning
- Subtle control
- Organizational transfer of learning
Note
Agile vs. Scrum Agile is the foundational philosophy and mindset, Scrum is the framework that brings Agile philosophy to life.
Concepts
Three Pillars of Scrum Empiricism
- Transparency: Make the most significant aspects of our work visible to those responsible for the outcome.
- Inspection: Conducting timely checks towards the outcome of a Sprint goal to detect undesirable variances.
- Adaptation: Adjusting project, product, or process to minimize any further deviation or issues.
Five Values of Scrum
- Commitment
- Courage
- Focus
- Openness
- Respect
-
Mission and Product Vision
-
Product Backlog: the single authoritative source for things that a team works on to achieve the project goal.
- Product features
- Product requirements
- Activities associated with product deliverables
-
Sprint: A time-boxed iteration in Scrum where work is done.
-
Daily Scrum: A meeting of 15 or fewer minutes everyday of the Sprint.
Roles
Characteristics of a Great Scrum Team | InfoQ
Scrum Master
- Build the thing right
- Duties
- Coaching the team members in self-management and cross-functionality
- Helping the Scrum Team focus on creating high-value Increments that meet the Definition of Done (an agreed upon set of items that must be completed before a project or user story can be considered complete)
- Causing the removal of impediments to the Scrum Team’s progress
- Ensuring that all Scrum events take place and are positive, productive, and kept within the timebox (a Scrum concept that refers to the estimated duration for an event)
- Traits
- Organizational skills
- Supportive leaders
- Facilitate productivity and collaboration
- Coach team members
- Great communicators
Product Owner
- Product Owner - Build the right thing
- Duties
- Developing and explicitly communicating the Product Goal
- Creating and clearly communicating Product Backlog items (The Product Backlog contains all of the features, requirements, and activities associated with deliverables to achieve the goal of the project.)
- Ensuring that the Product Backlog is transparent, visible, and understood
Development Team
- Build the thing right
- Duties
- Creating a plan for the Sprint, the Sprint Backlog (the set of Product Backlog items that are selected to be completed during the upcoming Sprint)
- Instilling quality by adhering to a Definition of Done
- Adapting their plan each day toward the Sprint Goal
- Holding each other accountable as professionals
- Executing sprints by designing, building, and testing Product Backlog items in increments
Product Backlog
Product Backlog | Scrum Guides
- Key features
- Living artifact
- Owned and adjusted by the product owner
- Prioritized list of features
- Attributes
- Description
- Value
- Order
- Estimate
- User Stories
- Backlog Refinement = prioritize and estimate
Scrum Events
- Sprint
- The Sprint | Scrum Guides
- Time-boxes, 1 to 4 weeks
- Sprint Planning
- Definition of Done
- Sprint Backlog, a subset of Product Backlog
- Daily Scrum
- 15 minutes daily stand-up meetings
- What to do today? What did you do yesterday?
- Sprint Review
- Which items are finished and which are not?
- Fun and uplifting
- Determine Product Increment and what is Releasable.
- Sprint Retrospective
- Blamelessness
- Participation is the key!
- Balance the negative with the positive.
- Act on it!
- Some concepts
- Product Increment
- Potentially Releasable Product
- Minimum Viable Product
Scrum Tools
- Burndown Chart
- Velocity (story points per Sprint), should not be used as a performance metric!
- Kanban Board
- project-management-tools