Scrum Flashcards
Scrum Pillars
Transparency, Inspection, Adaptation
Transparency - significant aspects of the practice must be visible to those responsible for the outcome. Transparency requires those aspects be defined by a common standard (Definition of Done)
Inspection - frequently review artifacts and progress toward a Sprint Goal (Daily Scrum, Sprint Review)
Adaptation - adjusting team process or product to minimize deviations. (Sprint Planning/Retrospective)
Scrum Framework
Scrum is a framework with guiding definition and rules applied to the following 3 main Scrum components: Artifacts, Roles & Events
Scrum Artifacts
Product Backlog, Sprint Backlog, Increment
Product Backlog (Scrum Artifact)
Prioritized list of items including features, fixes, enhancements, non-functional requirements
Collectively constitutes the product roadmap
Sprint Backlog (Scrum Artifact)
Set of Product Backlog items (PBIs) selected for the Sprint, further broken down to the task level
Collectively represents all the work to build the product increment and realizing the Sprint Goal
Increment (Scrum Artifact)
Sum of completed PBIs during the current Sprint
Includes the reviewed and realized the value of the increments of all previous Sprints
Scrum Framework Roles
PO - Product Owner
PO - Product Owner
The person responsible for managing the backlog so as to maximize the value of the project
represents all the stakeholders of the project
Scrum Framework Roles
Development team
Development team
Cross-functional/self-organizing group of people responsible for managing the Sprint Backlog and achieving sprint Goal
Have necessary skills to deliver each product increment
Scrum Framework Roles
SM - Scrum Master
The person responsible for Scrum Framework, its correct implementation, and the maximization of its benefits
The Scrum Master facilitates the removal of Sprint impediments
Scrum framework Events
Sprint Planning
Daily Scrum
Sprint Review
Sprint Retrospective
Sprint Planning
Timebox: 2-hrs/wk of Sprint to max 8 hrs
Split equally into 2 parts focusing on:
Product backlog & Sprint Goal
The What and Why - 1hr/wk of Sprint to max 4hrs
Sprint Backlog (Sprint task details/estimates) The How - 1hr/wk of Sprint to max 4 hrs
Daily Scrum
15 min or less
Synchronizes Sprint work/progress
Identifies any Sprint impediments
Sprint Review
Timebox: 1hr/wk of Sprint to max 4hrs
Occurs at the end of each Sprint
Product centric evaluation/improvement
Demonstrates Sprint Increment (potentially shippable/releasable product)
Sprint Retrospective
Timebox: 45min/wk of Sprint to max 3hrs
Occurs after Sprint Review and before next Sprint Planning
Process-centric evaluation/improvement areas
(to be considered for Subsequent Sprints)
What’s a Sprint?
A Sprint is a container for all Scrum activity
Contains all Scrum events (Sprint Planning, Daily Scrum, Sprint Review, Sprint retrospective)
What’s the Sprint timebox?
1 to 4 weeks to a max of 30 sequential calendar days
Sprints have consistent durations throughout a development effort
Sprint Guidelines
A Sprint begins with Sprint Planning (SP), followed by Daily Scrums (DS) and ends with the Sprint Review/retrospective (SRs)
There is no downtime in between Sprints; Sprints flow from a Sprint Retrospective meeting (end of the afternoon) into the next Sprint Planning (next morning)
Sprint Guidelines
Sprints continue until the Product Owner decides the product is ready for release. Each resulting Sprint Increment represents a ready potentially shippable/releasable product at Sprint end
Scrum embraces change but for the next Sprint; Team and Product Owner collaborate in the current Sprint (with Scrum Master support) to groom/refine the Product Backlog in preparation for future Sprints.
During the current Sprint, no new PBI (product backlog items) may be added allowing the Team to focus on a small, clear, and relatively stable Sprint Goal.
Sprint Perceptions
A correct perception and application of a Sprint is performing iterative work; doing a little bit of everything all the time resulting in a complete potentially shippable/releasable product increment
Performed by cross-functional/self-organizing team with necessary skills to realize Sprint Goal
PO - Product Owner
- Collects requirements and forms product vision
- Creates and updates the Product Backlog
- Ensures everyone has a common understanding of product vision and PBIs
- Prioritizes PBIs in order to maximize value/ROI
- Works with team to declare Sprint Goal
- Deals with Stakeholders
- Is a proxy for customer and steering committee
Scrum Team
- Do the work of delivering Sprint Increment
- Collectively accountable for achieving Sprint Goal
- Self-organizing/managing (optimally 7 to 9 members)
- Responsible for creating and maintaining Sprint Backlog including tracking of remaining Sprint effort
- Must participate at Daily Scrum meetings
- Prepares Sprint Review meeting demonstration
Scrum Master (SM)
- Ensures the understanding and correct use of Scrum rules and practices
- Keeps the team spirits up and helps resolve conflicts
- Addresses impediments
- keeps the team focused on committed Sprint Goal
- Facilitates Scrum meetings
- Protects the team from external noise/distraction
- Act as ‘Servant-leader’ to both Team and PO
