scrum training: the scrum guide explained for the self-organizing team

16
Scrum Training: The Scrum Guide Explained for the Self-Organizing Team Glen Wang http://www.scrumalliance.org/community/profi le/gwang16

Upload: aricin

Post on 18-Jan-2016

39 views

Category:

Documents


0 download

DESCRIPTION

Scrum Training: The Scrum Guide Explained for the Self-Organizing Team. Glen Wang http://www.scrumalliance.org/community/profile/gwang16. This training is based on the Scrum Guide . It uses the Self-Organizing Team as the main thread. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Scrum Training: The Scrum Guide Explained for the Self-Organizing Team

Scrum Training:The Scrum Guide Explained for the Self-Organizing Team

Glen Wanghttp://www.scrumalliance.org/community/profile/gwang16

Page 2: Scrum Training: The Scrum Guide Explained for the Self-Organizing Team

2013-09-09 | Page 2

This training is based on the Scrum Guide.

It uses the Self-Organizing Team as the main thread.

And it uses the Scrum Values, Pillars, and Artifacts as the weapons of the Self-Organizing Team.

* In this training, Scrum is explained roughly in the format of Subject – Predicate – Object.

Page 3: Scrum Training: The Scrum Guide Explained for the Self-Organizing Team

2013-09-09 | Page 3

› Section 1: Overview of the Scrum Guide Explained› Section 2: The Self-Organizing Team and Its Weapons› Section 3: Weapon Group 1: 3 Artifacts and 2 Values of

Scrum› Section 4: Weapon Group 2: 3 Pillars and 3 Values of

Scrum› Section 5: Tips for the Self-Organizing Team

Outline

Page 4: Scrum Training: The Scrum Guide Explained for the Self-Organizing Team

2013-09-09 | Page 4

The next page is a summary of Scrum.

All components are divided into 4 groups:-Artifacts-Events & Pillars-Roles-Connections to outside the Scrum world

Page 5: Scrum Training: The Scrum Guide Explained for the Self-Organizing Team

2013-09-09 | Page 5

Sprint Backlog

Sprint Goal

Product Increment

Definition of Done

Release Plan

PBI for Next Sprint

Monitor Progress

(toward Sprint Goal)

PO – Product Owner SM – ScrumMaster

Sprint Plan Sprint Review

Daily Scrum Retrospective

3-level Plan:

•Portfolio Plan

•Product Plan

•Sprint Plan

A Container to include:

•XP

Team: Self-Organizing & Cross-Functional

3 Pillars:

•Inspect

•Adapt

•Transparency

Section 1: Overview of Scrum Guide Explained

Page 6: Scrum Training: The Scrum Guide Explained for the Self-Organizing Team

2013-09-09 | Page 6

(subject) The next page is the overview of the Self-Organizing team and its weapons.

(predicate) Self-Organizing uses the 3 Scrum Pillars, which are associated with the 3 Values behind Scrum.

(object) 3 Artifacts show the results of Self-Organizing. 2 other Scrum Values stand behind the 3 Artifacts.

Page 7: Scrum Training: The Scrum Guide Explained for the Self-Organizing Team

2013-09-09 | Page 7

Self-Organizing Team

•Self-Organizing theory believes in and uses the intelligence of the crowd/team.

•Self-Organizing itself is the drive and motivation.

•It’s about the right way of working.

3 Pillars

•Inspect

•Adapt

•Transparency

3 Important Artifacts

•Sprint Goal

•Product Increment

•Definition of Done

Scrum Values

•Courage

•Openness

•Respect

Scrum Values

•Focus

•Commitment

Section 2: Self-Organizing Team and Its Weapons

Page 8: Scrum Training: The Scrum Guide Explained for the Self-Organizing Team

2013-09-09 | Page 8

› The Sprint Goal connects all items in the Sprint Backlog. If some Sprint Backlog Item has no direct relationship to the Sprint Goal, it has higher potential to be dropped if we have to drop some items.

› It shows the values of Focus and Commitment.› It can be a technical milestone, e.g., Pass the 1st Call.› It can be a group of functionalities, e.g., Interactions with

Other Services.› It can be about people, e.g., Touching the CEO.› The purpose of setting the Sprint Goal is to improve the

possibility of completion.

Section 3.1 Weapon: Sprint Goal

Page 9: Scrum Training: The Scrum Guide Explained for the Self-Organizing Team

2013-09-09 | Page 9

› Agile Value: Working software over comprehensive documentation.

› Agile Principle: Deliver working software frequently, from a couple of weeks to a couple of months, with a preference for to the shorter timescale.

› Agile Principle: Working software is the primary measure of progress.

› Agile Principle: Continuous attention to technical excellence and good design enhances agility.

› The feeling of Done 12 times (once per sprint) is better than Done once yearly.

Section 3.2 Weapon: Product Increment

Page 10: Scrum Training: The Scrum Guide Explained for the Self-Organizing Team

2013-09-09 | Page 10

› DoD is the team’s quality commitment. It shows the Scrum value of Commitment.

› It’s a checklist internalized and bought into by the team.› The management team can influence the DoD.› The team needs to continuously optimize the DoD. › Team learning/development objectives can also be

included in the DoD.

Section 3.3 Weapon: DoD

Page 11: Scrum Training: The Scrum Guide Explained for the Self-Organizing Team

2013-09-09 | Page 11

Section 3.3.1 DoD Example:

Page 12: Scrum Training: The Scrum Guide Explained for the Self-Organizing Team

2013-09-09 | Page 12

Self-Organizing Team

•Self-Organizing theory believes in and uses the intelligence of the crowd/team

3 Pillars

•Inspect

•Adapt

•Transparency

3 Important Artifacts

•Sprint Goal

•Product Increment

•DoD

Scrum Values

•Courage

•Openness

•Respect

Scrum Values

•Focus

•Commitment

Section 4: Weapon Group 2: 3 Pillars and 3 Values of Scrum

Page 13: Scrum Training: The Scrum Guide Explained for the Self-Organizing Team

2013-09-09 | Page 13

› In Sprint Planning, the individual is encouraged to express his/her opinion, not to hide.

› In the Daily Scrum, team members are encouraged to raise replanning needs if there are any.

› The team should review and groom the Release Plan.› The Sprint Review is a chance to Inspect & Adapt. It’s not

for team performance evaluation and celebration.› Show Courage, Openness, and Respect in the Sprint

Retrospective. Self-reflection and celebration can be part of the Sprint Retrospective.

Section 4.1: Apply the 3 Pillars

Page 14: Scrum Training: The Scrum Guide Explained for the Self-Organizing Team

2013-09-09 | Page 14

› At the end of a sprint, one cannot say, “I completed my tasks but Tom still has something to do.”

› Pair programming.› Collective code ownership.› The team dynamically pulls tasks from the Sprint backlog.› The PO focuses on what; the team focuses on how.› Open discussion: Any other tips and practices?

Section 5.1: Tips for Self-Organizing – Use the intelligence of the crowd

Page 15: Scrum Training: The Scrum Guide Explained for the Self-Organizing Team

2013-09-09 | Page 15

› Make it visible.› Generate rhythm.

Section 5.2: Tips for Self-Organizing – Scrum Team Daily Time Management

Time Name Time Range Purpose

Daily Stand-up 15 minutes For team synchronization, not for reporting and long discussion.

Team Hour 1 hour subsequent to the daily stand-up, same time of the day

For structured discussion or problem solving; for example, story grooming or solution design. It’s better if the topic is announced one day ahead. Only the related team members join.

Core Hours 4 hours: 2 in the morning and 2 in the afternoon

In the core hours, every team member should be reachable. Any instant discussion happens in core hours.

Non-Core Hours

To accommodate that some people come early or leave late. Also for individual work that requires focus.

Page 16: Scrum Training: The Scrum Guide Explained for the Self-Organizing Team

2013-09-09 | Page 16

Self-Organizing Team

•The Self-Organizing theory believes in and uses the intelligence of the crowd/team.

•Self-Organizing itself is the drive and motivation.

•It’s about the right way of working.

3 Pillars

•Inspect

•Adapt

•Transparency

3 Important Artifacts

•Sprint Goal

•Product Increment

•Definition of Done

Scrum Values

•Courage

•Openness

•Respect

Scrum Values

•Focus

•Commitment

Recap: Self-Organizing Team and Its Weapons