Presented by: Linda Westfallwestfallteam.com/sites/default/files/webinars/Scrum... · Scrum 101 –...

Copyright © 2007-2019 Westfall Team, Inc.. All Rights Reserved.

Sponsored by:

Presented by: Linda Westfall

Logistics Attendees are on mute Type your questions into the Question area – Cathy will monitor those questions & I will answer them as we go and/or at the end of the presentation A recording & slides for this webinar will be available online at WestfallTeam.com starting tomorrow You will receive an email tomorrow: • Which is verification of attendance for RUs, PUs,

etc. • Telling you how to access the webinar’s recording

& slides

Scrum 101 – A Basic Overview of the Agile Scrum Process

Scrum Roles

Scrum Process

Scaling Scrum

Scrum Roles The Scrum Team consists of three primary roles:

Product Owner Development Team

Scrum Master

Other Scrum roles: • Management • Customer • Other Stakeholders

Product Owner The Product Owner is officially responsible for the

project by Representing project stakeholder interests Acquiring initial & on-going project funding Managing, controlling & making the Product Backlog visible Frequently helping prioritize & estimate the Product Backlog

[based on Schwaber-03]

Development Team The Development Team is:

Self-managing Self-organizing Cross-functional

The Development Team is collectively responsible for:

Turning the Sprint Backlog into a deliverable software increment The success of each iteration The project as a whole

[Schwaber-03]

Scrum Master

The Scrum process & acting as an agile coach Protecting the Development Team from outside distractions & interference Helping acquire resources & removing impediments Helping adopt, adapt & continuously improve the Scrum process to meet the needs of the Scrum Teams & the organization Facilitating the Sprint Planning Meetings, daily Scrum meetings, Sprint Review Meetings & Sprint Retrospective Meetings

The Scrum Master is more a coach than a project manager & is responsible for:

Scrum Master (cont.) Facilitating the gathering of team consensus, including agreements on how they will do their work Capturing empirical data for tracking progress & determining Development team’s velocity (the team’s overall ability to deliver work) during each Sprint

[Schwaber-03]


Scrum Roles

Scrum Process

Scaling Scrum

Scrum Process Overview

Selected Product Backlog

Product Backlog: emerging,

prioritized user stories & other

items

Starts Here

Increment of Functionality

Sprint Backlog

Sprint Planning Meeting

Vision: anticipated

ROI, releases,

milestones

Sprint Review Meeting

Delivered Functionality

End Project

?

No Yes End Here

Deliver?

No

Daily Scrum

Sprint (Iteration)

Backlog Refinement

Meetings

Issues, incomplete stories or

improvements

Newly identified & changed backlog

items

Yes Good

Issues & Incomplete stories

Improvements

Sprint Retrospective

Product Backlog The Product Backlog is a

prioritized list of functional, non-functional & enablement user stories/epics.




items

Starts Here

Vision: anticipated

ROI, releases,

milestones

Product Backlog

Story

Story

Story

Story

Epic

Epic

Story . . .

Product Backlog The Product Backlog is a

prioritized list of functional, non-functional & enablement user stories/epics.




items

Starts Here

Vision: anticipated

ROI, releases,

milestones

Product Backlog

Story

Story

Story

Story

Epic

Epic

Story . . .

Changes in the Product Backlog reflect:

Changing business needs Backlog refinement How quickly or slowly the team can transform backlog into working software.

User Stories User Story template:

As a <stakeholder(s)>, I can <feature/function>

in order to <reason or benefit> A large story (epic):

As a customer, I can purchase gas at the pump in order to make it faster and more convenient to buy gas

Broken into smaller stories: As a customer, I can scan my credit or debit card at the pump in order save time by not going inside to pay As a customer, I can enter my zip code for credit cards at the pump in order ensure the security of my card

User Stories (cont.) As a customer, I can enter my debit card PIN at the pump in order ensure the security of my card As a station owner, I can get each debit card and PIN validated prior to pumping gas in order to confirm payment is received for the gas purchase As a customer, I can select the type of gas pumped in order to pump the correct type of gas into my vehicle





items

Starts Here

Sprint Backlog

Scrum Planning Meeting

Vision: anticipated

ROI, releases,

milestones

Sprint Planning Meeting (cont.)

1st Meeting: Identify the Sprint “goal” Prioritize backlog Answer remaining questions about Product Backlog Select one iteration’s worth of work Obtain the Development Team’s commitment to the Product Owner

A Sprint begins with a planning meeting.


1. _______ _________

2. _______ _________

3. _______ _________

2nd Meeting: Translate selected Product Backlog items into Sprint Backlog tasks Add additional tasks to Sprint Backlog needed to conduct the Sprint Estimate effort for each task

Sprint Backlog

1.1 _____________

1.2 _____________

1.3 _____________

2.1 _____________

2.2 _____________

3.1 _____________

4.0 _____________

Prioritize Product Backlog

Story

Story

Story

Story

Epic

Epic

Story . . .

Product Backlog

Prioritize Product Backlog

Story

Story

Story

Story

Epic

Epic

Story . . .

Product Backlog

Reprioritized Product Backlog


Story

Story

Story

Product Backlog


Story

Epic

Epic

Story . . .

Sprint Backlog

Story Story

Epic

Epic

Story

Product Backlog


Story

Story

Sprint Backlog

Task Task

Task Task

Task Task

. . .

Sprint Backlog

Story Story

Epic

Epic

Story

Product Backlog


Story

Story

Sprint Backlog

Task Task

Task Task

Task Task

. . . Task Task

Task Task

Sprint Backlog

Story Story

Epic

Epic

Story

Product Backlog


Story

Story

Sprint Backlog

Task Task

Task Task

Task Task

. . . Task Task

Task Task

Task Task

Task Task

Task

Task Boards & Task Selection

Story

Product Backlog


Story

Story

Sprint Backlog

Task

Task Task

Task Task

Task Task

Task Task

Task Task

Task

21

3

1 5

8

8 3

1 5

3 2

2

To Do In Progress Done

Task 8

Task 3

Task 13

Story

Epic

Epic

Story . . .

Backlog Refinement Meetings




items

Starts Here

Sprint Backlog


Vision: anticipated

ROI, releases,

milestones

Daily Scrum

Sprint (Iteration)

Backlog Refinement

Meetings

Backlog Refinement Meetings (cont.)

Story

Epic

Epic

Product Backlog

Story

Story

. . .

Story

If an epic is moving up high enough in priority that it will be addressed

in one of the next several Sprints.

It is further refined into stories Story

Story

Story

Backlog Refinement Meetings (cont.) Product Backlog

Story

Story

Story

Epic

. . .

Story

Story

Story

Story

If an epic is moving up high enough in priority that it will be addressed

in one of the next several Sprints.

It is further refined

into stories –

and those stories are prioritized back into the

Product Backlog

The Three C’s of User Stories Card: The artifact containing the User Story Conversation: A User Story is a reminder to discuss

the details of the requirements once the story has been selected for implementation

Confirmation: The conversation includes defining & documenting the acceptance criteria the Product Owner (and/or other stakeholders) will use to determine if the User Story has been successfully implemented

Conversation

Stories that are likely to be selected for the next few Sprints are discussed:

Ambiguous or unclear stories are defined Stories are refined into more detail Questions are answered A consensus is reached Acceptance criteria are established Refined items may be reprioritized

Definition of ready.

Story

Epic

Product Backlog

Story

Story

. . .

Story

Story

Story

Story

Conversation → Confirmation

If customer selects regular than regular is pumped If customer selects super than super is pumped If customer selects premium than premium is pumped If the customer selects one type & then another … If the customer selects two types at once … If the customer does not select a type … If the customer presses cancel … If the customer presses any other pump key … If the emergency all stop is pressed …

As a customer, I can select the type of gas pumped in order to pump the correct type of gas into my vehicle.

Scrum Skeleton


Sprint Backlog

Scrum employs an iterative, incremental flow known as the Scrum skeleton.

[Schwaber-03]

Daily Scrum

Sprint (Iteration)

Scrum Heart


Sprint Backlog

The heart of Scrum lies in the iteration.

Daily Scrum

Sprint (Iteration)

Daily Scrum Meetings




items

Starts Here

Sprint Backlog


Vision: anticipated

ROI, releases,

milestones

Daily Scrum

Sprint (Iteration)

Conducted by the Scrum Master (15 minute stand-up).

Each member of the Development Team answers:

“What have you done since the last Scrum? What will you do between now & the next Scrum? What got in your way of doing work?”

1st Daily Scrum Meeting

Story


Story

Story

Sprint Backlog

Task

Task Task

Task Task

Task Task

Task Task

Task Task

Task

21

3

1 5

8

8 3

1 5

3 2

2


Task Task

Task

8

3

13


Story


Story

Story

Sprint Backlog

Task

Task Task

Task Task

Task Task

Task Task

Task

21

Task

Task

3

1 5

8

8 3

1 5

3 2

2


Task

Task 3

13 Task

8 6 /


Story


Story

Story

Sprint Backlog

Task

Task Task

Task Task

Task Task

Task Task

Task

21

5

8

8 3

1 5

3 2

2


Task Task

Task

8

3

6 /

Task

Task

3

1

5 13 / 10


Story


Story

Story

Sprint Backlog

Task Task

Task Task

Task Task

Task Task

Task

21

Task 5

8

8 3

1 5

3 2

2


Task Task 8 5 13 6 /

Task

Task

3

1

/ 10

Task 3 / 3


Story


Story

Story

Sprint Backlog

Task

Task Task

Task Task

Task Task

Task Task

Task

21

5

8

8 3

1 5

3 2

2


Task Task

Task

8

3

5 13 6 /

Task

Task

3

1

/ 10

/ 3

Task


Story


Story

Story

Sprint Backlog

Task

Task Task

Task Task

Task Task

Task Task

Task

21

5

8

8 3

1 5

3 2

2


Task Task

Task

8

3

5 13 6 /

Task

Task

3

1

/ 10

/ 3

Task 8

At End of 2nd Daily Scrum Meeting

Story


Story

Story

Sprint Backlog

Task Task

Task Task

Task Task

Task

8 3

1 5

3 2

2


Task

Task

8

3

6 /

/ 3

Task 8

Task Task 21 8

Task 5

Task 13

Task

Task

3

1

/ 15

3

5 1

/

/ /

At End of Sprint

Story


Story

Story

Sprint Backlog


Task

Task Task

Task Task

Task Task

Task Task

Task

21

5

8

8 3

1 5

3 2 2

Task Task

Task

8

3

13 6 /

Task

Task

3

1

/ 15

/ 3 Task

8 3 9

5 1

8 37

7 4

3 2

2 5

/ /

/ /

/ /

/ /

/ /

/ /

2 /

0

20

40

60

80

100

120

1 2 3 4 5 6 7 8 9 10Days

# S

tory

Poi

nts

Com

plet

ed

Original EstimateActuals

Velocity (Burn-Up Chart) – Example

New Stories & Epics




items

Starts Here

Sprint Backlog


Vision: anticipated

ROI, releases,

milestones

Daily Scrum

Sprint (Iteration)

Backlog Refinement

Meetings Newly identified backlog items

All Change → Product Backlog Product Backlog

Story

Epic

Epic

Story

Story

. . .

Story

During the Sprint – All change happens on the

Product Backlog.

That way the Scrum Team can stay focused

on its Sprint goal.

All Change → Product Backlog Product Backlog

Story

Epic

Story

Epic

Story . . .

Story

During the Sprint – All change happens on the

Product Backlog.

That way the Scrum Team can stay focused

on its Sprint goal. Epic

“Refinements,” Not “Changes”


Learning always occurs during a Sprint. We almost always start without full knowledge Some level of clarification or refinement can be expected

However, in an extreme circumstance, if significant change is required:

Terminate the Sprint Return to the prior Sprint’s baseline Plan & initiate a new Sprint

But this should be an infrequent occurrence.





items

Starts Here


Sprint Backlog


Vision: anticipated

ROI, releases,

milestones


Daily Scrum

Sprint (Iteration)

Backlog Refinement

Meetings

Newly identified backlog items

Issues, incomplete stories


Potential Delivery




items

Starts Here


Sprint Backlog


Vision: anticipated

ROI, releases,

milestones



Deliver?

Daily Scrum

Sprint (Iteration)

Yes

Good

Backlog Refinement

Meetings


Issues, incomplete stories


Scrum Release Scrum can have different release cadences:

Make a decision after one or more Sprints (iterations) Release after each feature meets its “done” criteria Do release planning that looks forward through the releases of the product

Sprint #1 Sprint #2 Sprint #3 Sprint #4 Sprint #5 Sprint #6



OPER

ATION

S

Release #1

Release #2

Release #3

Sprint #n1 Sprint #n2 Sprint #n3 Sprint #n4 Sprint #n5 Sprint #n6 Release #n

…

Sprint Retrospective Meeting




items

Starts Here


Sprint Backlog


Vision: anticipated

ROI, releases,

milestones




Deliver?

No

Daily Scrum

Sprint (Iteration)

Yes

Good

Backlog Refinement

Meetings


Issues, incomplete stories or

Improvements

Improvements


Sprint Retrospective Meeting (cont.) After the completion of the Sprint, there is a Sprint

Retrospective Meeting. This meeting includes:

Reviewing “what went well” & “what could be improved” Prioritizing improvement actions to make the Scrum process more efficient, effective & team-friendly Adding improvement tasks to the Product Backlog

What do we want to “start, stop and continue doing?” [Schwaber-07]

End the Scrum Project




items

Starts Here


Sprint Backlog


Vision: anticipated

ROI, releases,

milestones




End Project

?

Yes End Here

Deliver?

No

Daily Scrum

Sprint (Iteration)

Yes

Good

Backlog Refinement

Meetings


No

Issues, incomplete backlog items or

improvement

Improvements



Scrum Roles

Scrum Process

Scaling Scrum

Nexus Overview



items

Sprint Backlog

Nexus Sprint Planning

Nexus Sprint Review

No

Nexus Daily

Scrum

Yes

Backlog Refinement

Meetings

Nexus Scrum Team

Scrum Team

Scrum Team

Scrum Team

3-9 Scrum Teams


Deliver?


Integrated work

Nexus Integration

Team

Nexus Sprint Retrospective

Nexus

Scrum Team

Scrum Team

Scrum Team

Scrum Team

Nexus

[scrum.org/resources/nexus-guide]

Scaled Agile Framework (SAFe®)

[scaledagileframework.com]

https://www.scaledagileframework.com/

References: Cohn-09: Mike Cohn, Succeeding with Agile: Software Development Using Scrum, Addison-Wesley, 2009. Rubin-12: Kenneth Rubin, Essential Scrum: A Practical Guide to the Most Popular Agile Process, Addison-Wesley, 2012. Schwaber-03: Ken Schwaber, Agile Project Management with Scrum, Microsoft Press, 2003.

Websites: Nexus Guide: https://www.scrum.org/resources/nexus-guide Scaled Agile Framework (SAFe®): https://www.scaledagileframework.com/ Scrum Alliance: http://www.scrumalliance.org Scrum Guides: http://www.scrumguides.org/scrum-guide.html Scrum Training Series: http://www.scrumtrainingseries.com/

https://www.scaledagileframework.com/

http://www.scrumalliance.org/

http://www.scrumguides.org/scrum-guide.html

Reminders A recording & slides of this webinar will be available online You will receive an email tomorrow: • Which is verification of attendance for RUs, PUs,

etc. • Telling you how to access the recording & slides

Presenter: Linda Westfall More than 40 years in software:

President of The Westfall Team Sr. Manager of Quality Metrics & Analysis, Manager of Production Software, software process engineer, software engineer & systems analyst

Active professionally: ASQ Software Division past chair, ASQ Certification Board, PMBOK® contributor P.E., ASQ Fellow, CSQE, CMQ/OE, CBA & CQA, PMI PMP, Lean Six-Sigma Master Black Belt, Certified Scrum Master & Product Owner, SAFe SA, SASM, POPM Author: The Certified Software Quality Engineer Handbook , 2nd Edition

Contact Information

Linda Westfall 3000 Custer Road

Suite 270, PMB 101 Plano, TX 75075-4499

phone: (972) 867-1172

email: [email protected]

www.westfallteam.com

Presented by: Linda Westfallwestfallteam.com/sites/default/files/webinars/Scrum... · Scrum 101 –...

Documents

Transcript of Presented by: Linda Westfallwestfallteam.com/sites/default/files/webinars/Scrum... · Scrum 101 –...