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. And it uses the Scrum Values, Pillars,and Artifactsas the weapons of the Self-Organizing Team. * In this training, Scrum is explained roughly in the format of Subject – Predicate – Object.
Outline • 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
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
Section 1: Overview of Scrum Guide Explained • 3-level Plan: • Portfolio Plan • Product Plan • Sprint Plan PO – Product Owner SM – ScrumMaster Sprint Review Sprint Plan Sprint Backlog Sprint Goal Product Increment Definition of Done Release Plan PBI for Next Sprint Monitor Progress (toward Sprint Goal) • A Container to include: • XP • 3 Pillars: • Inspect • Adapt • Transparency Retrospective Daily Scrum Team: Self-Organizing & Cross-Functional
(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.
Section 2: Self-Organizing Team and Its Weapons 3 Pillars • Inspect • Adapt • Transparency • 3 Important Artifacts • Sprint Goal • Product Increment • Definition of Done 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. • Scrum Values • Courage • Openness • Respect • Scrum Values • Focus • Commitment
Section 3.1 Weapon: Sprint Goal • 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.2Weapon: Product Increment • 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.3 Weapon: DoD • 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 4: Weapon Group 2: 3 Pillars and 3 Values of Scrum 3 Pillars • Inspect • Adapt • Transparency • 3 Important Artifacts • Sprint Goal • Product Increment • DoD Self-Organizing Team • Self-Organizing theory believes in and uses the intelligence of the crowd/team • Scrum Values • Courage • Openness • Respect • Scrum Values • Focus • Commitment
Section 4.1: Apply the 3 Pillars • 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 5.1: Tips for Self-Organizing – Use the intelligence of the crowd • 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.2: Tips for Self-Organizing– Scrum Team Daily Time Management • Make it visible. • Generate rhythm.
Recap: Self-Organizing Team and Its Weapons 3 Pillars • Inspect • Adapt • Transparency • 3 Important Artifacts • Sprint Goal • Product Increment • Definition of Done 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. • Scrum Values • Courage • Openness • Respect • Scrum Values • Focus • Commitment