• Home

  • Documents

  • Scrum at a High Level · Scrum at a High Level 1. A team selects work to be done in 30 days (or...
47
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 done 3. 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

Scrum at a High Level · 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

  • Upload
    others

  • View
    1

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Scrum at a High Level · 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

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

Page 2: Scrum at a High Level · 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

• Commitment• Courage• Focus• Openness• Respect

Scrum Values

Page 3: Scrum at a High Level · 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
Page 4: Scrum at a High Level · 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
Page 5: Scrum at a High Level · 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
Page 6: Scrum at a High Level · 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

The Scrum Team

• Consists of a Product Owner, Development Team, and Scrum Master• Delivers products iteratively and incrementally

Page 7: Scrum at a High Level · 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

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

Page 8: Scrum at a High Level · 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

1 minProduct Owner

If there are four Scrum teams working on the same product, how many Product Owners should there be?

Page 9: Scrum at a High Level · 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

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

Page 10: Scrum at a High Level · 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

Cross-functional

A cross-functional team has all of the skills needed to accomplish its work

Page 11: Scrum at a High Level · 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

Self-organizing

Self-organizing teams choose how best to accomplish their work, rather than being directed

by others outside the team

Page 12: Scrum at a High Level · 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

1 minDevelopment Team

How many sub-teams can a Development Team have?

Page 13: Scrum at a High Level · 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

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

Page 14: Scrum at a High Level · 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

1 minScrum Master

If a Scrum Master is a servant leader, whom does he or she serve?

Page 15: Scrum at a High Level · 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
Page 16: Scrum at a High Level · 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
Page 17: Scrum at a High Level · 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

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

Page 18: Scrum at a High Level · 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

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

Page 19: Scrum at a High Level · 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

1 minProduct Backlog

Who estimates work on the Product Backlog?

Page 20: Scrum at a High Level · 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
Page 21: Scrum at a High Level · 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
Page 22: Scrum at a High Level · 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

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

Page 23: Scrum at a High Level · 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

1 minSprint

What factors should you take into account when determining the length of Sprints?

Page 24: Scrum at a High Level · 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

1 minSprint

Who is best equipped to determine the length of Sprints for a Scrum Team?

Page 25: Scrum at a High Level · 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

Time-boxes

• Maximum amount of time to be spent on an event• Provides focus• Typically proportionality shorter for Sprints shorter than

1 month

Page 26: Scrum at a High Level · 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
Page 27: Scrum at a High Level · 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
Page 28: Scrum at a High Level · 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

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?

Page 29: Scrum at a High Level · 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

1 minSprint Planning

What is created during Sprint Planning?

Page 30: Scrum at a High Level · 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

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

Page 31: Scrum at a High Level · 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

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

Page 32: Scrum at a High Level · 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
Page 33: Scrum at a High Level · 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
Page 34: Scrum at a High Level · 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

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

Page 35: Scrum at a High Level · 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
Page 36: Scrum at a High Level · 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
Page 37: Scrum at a High Level · 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

Increment

• The sum of all the Product Backlog items completed during a Sprint• Must be usable and potentially-releasable - ”Done”

Page 38: Scrum at a High Level · 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

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

Page 39: Scrum at a High Level · 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
Page 40: Scrum at a High Level · 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
Page 41: Scrum at a High Level · 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

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)

Page 42: Scrum at a High Level · 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

1 minSprint Review

Who ‘runs’ the Sprint Review?

Page 43: Scrum at a High Level · 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
Page 44: Scrum at a High Level · 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
Page 45: Scrum at a High Level · 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

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)

Page 46: Scrum at a High Level · 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

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

Page 47: Scrum at a High Level · 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

How To Survive Outsourcing? - CEO XSolve at Scrum Days 2016

How To Survive Outsourcing? - CEO XSolve at Scrum Days 2016

Small Business & Entrepreneurship
QuickBird - Amazon Web Servicescontent.satimagingcorp.com.s3.amazonaws.com/media/... · 2.4 days at 1 m GSD or less 5.9 days at 20° off-nadir or less 2.1 days at 1 m GSD or less

QuickBird - Amazon Web Servicescontent.satimagingcorp.com.s3.amazonaws.com/media/... · 2.4 days at 1 m GSD or less 5.9 days at 20° off-nadir or less 2.1 days at 1 m GSD or less

Documents
Scrum im Bundestag? - Vortrag XP Days Karlsruhe 15.11.2013

Scrum im Bundestag? - Vortrag XP Days Karlsruhe 15.11.2013

Technology
Global Scrum Gathering® Prague 2015 SESSION DESCRIPTION ... · More with LeSS: Introduction to Large-Scale Scrum (LeSS) Bas Vodde Touch [Advanced] Congress I Silicon Gym - Workouts

Global Scrum Gathering® Prague 2015 SESSION DESCRIPTION ... · More with LeSS: Introduction to Large-Scale Scrum (LeSS) Bas Vodde Touch [Advanced] Congress I Silicon Gym - Workouts

Documents
Microsoft Tech Days 2010 Table ronde sur Agilité Scrum Xp

Microsoft Tech Days 2010 Table ronde sur Agilité Scrum Xp

Technology
The Days of the More Less)

The Days of the More Less)

Documents
Scrum, Creating Great Products & Critical Systems · Scrum process can be learned and used in less than 2 days. ... 10 10 100 Test OS more Identify 2nd OS Joe System communication

Scrum, Creating Great Products & Critical Systems · Scrum process can be learned and used in less than 2 days. ... 10 10 100 Test OS more Identify 2nd OS Joe System communication

Documents
Certified LeSS Basics · Large-Scale Scrum (LeSS) is a framework for scaling agile development to multiple teams. LeSS builds on top of the Scrum principles such as empiricism, cross-functional

Certified LeSS Basics · Large-Scale Scrum (LeSS) is a framework for scaling agile development to multiple teams. LeSS builds on top of the Scrum principles such as empiricism, cross-functional

Documents
Large Scale Scrum (LeSS) · Scrum Masters are responsible for a well-working LeSS adoption. Their focus is towards the Teams, Product Owner, organization, and development practices

Large Scale Scrum (LeSS) · Scrum Masters are responsible for a well-working LeSS adoption. Their focus is towards the Teams, Product Owner, organization, and development practices

Documents
Agile, uma odisséia no espaço - s3-sa-east-1.amazonaws.com · SCRUM OF SCRUMS INTERNALLY CREATED METHODS DISCIPLINED AGILE DELIVERY (DAD) LARGE SCALE SCRUM (LESS) ENTERPRISE SCRUM

Agile, uma odisséia no espaço - s3-sa-east-1.amazonaws.com · SCRUM OF SCRUMS INTERNALLY CREATED METHODS DISCIPLINED AGILE DELIVERY (DAD) LARGE SCALE SCRUM (LESS) ENTERPRISE SCRUM

Documents
Die Minecraft Challenge Scrum vs. PMI...•Scrum in Two Days –Workshop 2 Tage für bis zu 12 Teilnehmer •Scrum in Two Days inklusive CSM –3 Tage •Bericht erscheint 17.11. online

Die Minecraft Challenge Scrum vs. PMI...•Scrum in Two Days –Workshop 2 Tage für bis zu 12 Teilnehmer •Scrum in Two Days inklusive CSM –3 Tage •Bericht erscheint 17.11. online

Documents
Large Scale Scrum (LeSS) als Organisations-Design-Framework

Large Scale Scrum (LeSS) als Organisations-Design-Framework

Business
Surviving SOX with Scrum - XP Days

Surviving SOX with Scrum - XP Days

Documents
#lego4scrum with Large-Scale Scrum (LeSS)

#lego4scrum with Large-Scale Scrum (LeSS)

Business
International Scrum Master Certified 2 Days Classroom ... · PDF fileProfessional Development 3 Contents Scrum Master Certified (SMCTM) Contents Scrum at a Glance 4 The Scrum Team

International Scrum Master Certified 2 Days Classroom ... · PDF fileProfessional Development 3 Contents Scrum Master Certified (SMCTM) Contents Scrum at a Glance 4 The Scrum Team

Documents
2 LeSS - Willkommen · Large-Scale Scrum, also Scrum im Großen, nachdenkt. LeSS Siehe Kapitel Einführung, S. 61 LeSS ist Scrum – Large Scale Scrum (LeSS)2 ist kein neues und verbes-sertes

2 LeSS - Willkommen · Large-Scale Scrum, also Scrum im Großen, nachdenkt. LeSS Siehe Kapitel Einführung, S. 61 LeSS ist Scrum – Large Scale Scrum (LeSS)2 ist kein neues und verbes-sertes

Documents
Scrum introduction XP Days 2010. Agenda Introduction The Scrum process – roles, ceremonies and artifacts Backlog management Conclusions and questions

Scrum introduction XP Days 2010. Agenda Introduction The Scrum process – roles, ceremonies and artifacts Backlog management Conclusions and questions

Documents
Descaling through LeSS (Large-Scale Scrum)

Descaling through LeSS (Large-Scale Scrum)

Software
Large Scale Scrum - DasScrumTeam · PDF fileThe LeSS (Large Scale Scrum) framework is a way to scale the work of multiple teams doing Scrum. LeSS applies to products with 2 - 8 teams

Large Scale Scrum - DasScrumTeam · PDF fileThe LeSS (Large Scale Scrum) framework is a way to scale the work of multiple teams doing Scrum. LeSS applies to products with 2 - 8 teams

Documents
Overview of Large Scale Scrum (LeSS)...2020/06/06  · Overview of Large Scale Scrum (LeSS) @ Johnson & Johnson Agile CoP Gene Gendel, Certified Enterprise & Team Coach (CEC-CTC),

Overview of Large Scale Scrum (LeSS)...2020/06/06  · Overview of Large Scale Scrum (LeSS) @ Johnson & Johnson Agile CoP Gene Gendel, Certified Enterprise & Team Coach (CEC-CTC),

Documents
Scrum days 2014 stevie borne

Scrum days 2014 stevie borne

Software
Scrum days 2016_scrum_bei_festo_frank-m.hoyer_nadine.kärcher

Scrum days 2016_scrum_bei_festo_frank-m.hoyer_nadine.kärcher

Presentations & Public Speaking
LeSS is Scrum - Naveen S @ CMBAgileCon 2016

LeSS is Scrum - Naveen S @ CMBAgileCon 2016

Software
Illuminating the potential of Scrum by comparing LeSS with SAFe

Illuminating the potential of Scrum by comparing LeSS with SAFe

Leadership & Management
WWII in 3 days or less

WWII in 3 days or less

Documents
Large-Scale Scrum: More with LeSS - pearsoncmg.comptgmedia.pearsoncmg.com/images/9780321985712/samplepages/9780321985… · Large-Scale Scrum More with LeSS Craig Larman Bas Vodde

Large-Scale Scrum: More with LeSS - pearsoncmg.comptgmedia.pearsoncmg.com/images/9780321985712/samplepages/9780321985… · Large-Scale Scrum More with LeSS Craig Larman Bas Vodde

Documents
Why Large Scale Scrum (LeSS)?

Why Large Scale Scrum (LeSS)?

Leadership & Management
Large Scale Scrum...Large Scale Scrum overview Gene Gendel, Certified Enterprise Coach LeSS is Scrum Gene Gendel, Certified Enterprise Coach LeSS Values (verb ) …

Large Scale Scrum...Large Scale Scrum overview Gene Gendel, Certified Enterprise Coach LeSS is Scrum Gene Gendel, Certified Enterprise Coach LeSS Values (verb ) …

Documents
LeSS (Large-Scale Scrum) Rulesscrumtrainingseries.com/LeSS-and-LeSS-Huge-rules-card.pdf · LeSS (Large-Scale Scrum) Rules from as of April 2017 LeSS Structure The LeSS framework applies

LeSS (Large-Scale Scrum) Rulesscrumtrainingseries.com/LeSS-and-LeSS-Huge-rules-card.pdf · LeSS (Large-Scale Scrum) Rules from as of April 2017 LeSS Structure The LeSS framework applies

Documents
Short Introduction to Large Scale Scrum LeSS

Short Introduction to Large Scale Scrum LeSS

Business