Scrum at a High Level · Scrum at a High Level 1. A team selects work to be done in 30 days (or...
Transcript of Scrum at a High Level · Scrum at a High Level 1. A team selects work to be done in 30 days (or...
Scrum at a High Level
1. A team selects work to be done in 30 days (or less)2. A time is scheduled at the end of that 30 days (or less) to
review the work that is done3. The team builds an increment of the product 4. The team reviews what was done with stakeholders,
collects feedback, and uses that feedback to guide what to do next
5. Repeat
The Scrum Team
• Consists of a Product Owner, Development Team, and Scrum Master• Delivers products iteratively and incrementally
Product Owner
• Responsible for maximizing the value of the product• The sole person responsible for managing the Product
Backlog• Can have others manage the Product Backlog, but the
Product Owner remains accountable
1 minProduct Owner
If there are four Scrum teams working on the same product, how many Product Owners should there be?
Development Team
• Responsible for creating an Increment of product each Sprint• Each person on the team is considered a ‘developer’• Self-organizing and cross-functional
Self-organizing
Self-organizing teams choose how best to accomplish their work, rather than being directed
by others outside the team
Scrum Master
• Responsible for promoting and supporting Scrum as defined in the Scrum Guide• Helps everyone understand Scrum theory, practices,
rules, and values• Removes impediments that are slowing the Scrum
Team’s progress• Servant leader
Product Backlog
• Ordered list of everything that might be needed for a product• ‘Single source of truth’ for requirements and any
changes needed in the product• Product Owner is responsible for the Product Backlog• It’s never complete
An Example Product BacklogID Title Value Estimate Acceptance Criteria
27 I want to have an insurance expert contact me to review my insurance needs So that I know I am properly covered
21 13 - Only customers in specific states must be presented with the option to contact an advisor - The confirmation page must contain an option to contact anadvisor- Customers must be able to provide their contact information- Customer behavior must be tracked in Google Analytics
27.1 I want to know why I should set up a review of my insurance through so that I know the value of a review and can decide whether or not I should request one
2 1 - Insurance types must be visually represented - Auto, Homeowners, Renters, and Umbrella must always appear in that order - All insurance types on the website should also be listed in that order. These must be displayed in a mobile-friendly fashion.
27.2 As an insurance product manager, I want to allow only customers that reside in specific states to submit their contact for an insurance review from so that we do not get fined by other state governments for breaking their laws
13 5 - Allowed states (based on residence/home address): AZ, CO, IA, IL, IN, MN, MO, NY, TX, and WI- Any QnA customer that does not reside in the above states should not be shown the insurance review section of the application confirmation page
Sprint
• Container event for all other events in Scrum• 30 days or less• Purpose is to produce a done, usable, potentially-
releasable increment of product
Time-boxes
• Maximum amount of time to be spent on an event• Provides focus• Typically proportionality shorter for Sprints shorter than
1 month
Sprint Planning
• The work to be done during a Sprint is planned during Sprint Planning• Entire Scrum Team attends• 8 hour time-box for a 1 month Sprint (~4 hours for a 2
week Sprint)• 2 primary topics• What can be done this Sprint?• How will the chosen work get done?
Sprint Backlog
• The set of Product Backlog items selected for the Sprint plus the plan for completing them• Has enough detail for the Development Team to
understand how they will work together to accomplish the goal of the Sprint• Modified by the Development Team as more is learned
throughout the Sprint• Owned by the Development Team
Sprint Goal
• An objective that will be met within the Sprint through the implementation of the Product Backlog• Provides guidance to the Development Team on why it
is building the Increment• Created by the Scrum Team during Sprint Planning
Daily Scrum
• For the Development Team to synchronize activities and create a plan for the next 24 hours• 15 minute time-box• Not a status meeting• Development Team is responsible for conducting• Scrum Master is responsible for ensuring it occurs and
teaching the Development Team to keep it within the time-box
Increment
• The sum of all the Product Backlog items completed during a Sprint• Must be usable and potentially-releasable - ”Done”
Definition of “Done”
• A common definition of what it means for an Increment to be considered “done”• Provides the Development Team guidance in
understanding how many Product Backlog items to bring into a Sprint
Sprint Review
• Collaborative working session to inspect the Increment and adapt the Product Backlog as necessary• Development Team demonstrates the work it has
“Done” and answers questions• Attendees collaborate on the next things that could be
done to optimize value• Entire Scrum Team and stakeholders attend• 4 hour time-box for a 1 month Sprint (~2 hours for a 2
week Sprint)
Sprint Retrospective
• An opportunity for the Scrum Team to inspect itself and identify improvement items to put into practice• Scrum Team identifies actionable improvements to put
into place during the next Sprint• Entire Scrum Team participates• 3 hour time-box for a 1 month Sprint (~1.5 hours for a 2
week Sprint)
Product Backlog Refinement
• The act of adding detail, estimates, and order to items in the Product Backlog• Ongoing process in which the Product Owner and the
Development Team collaborate on the details of Product Backlog items• Usually consumes no more than 10% of the capacity of
the Development Team