Collaboration at Scale: Building a ScrumMaster Community of Practice10-May-2017

Collaboration at Scale

Designed for Scrum-centric organizations with more than 10 Scrum teams, the Collaboration at Scale webinar series provides focused, outcome-driven solutions to collaboration problems faced by Product Owners, ScrumMasters, and Development Teams.

Produced by the Scrum Alliance and Conteneo, Inc., we’re proud of the many distinguished experts who share their wisdom in our series.

Luke Hohmann

2

LisetteSutherland

Zubin Irani

2-4 WEEK SPRINT

DAILY SCRUM MEETING

(EVERY 24 HOURS)

POTENTIALLY SHIPABLE PRODUCT INCREMENT

SPRINT BACKLOGPRODUCT BACKLOG

3

Common Scrum Challenges

Tech Debt

Release Planning

Roadmap

Retros

Liftoffs

Refining

Value-Based

Backlogs

Priorities

Depend-encies

Done, Done

CI/CD

TODAY:Building a ScrumMaster Community of Practice

June 2017: Estimation And Story

Points

How many Scrum Masters / Agile Coaches are in your org?

• None• 1 - 2• 3 - 5• 6 - 10• More than 10• I don’t know

4

POLL QUESTION

Agenda

1 What’s a Community of Practice and Why Should We Create one?

2 Preparing to Launch3 Infrastructure and Frameworks4 Ongoing Operations

5

What’s a Community of Practice?

6

What’s a Community of Practice (CoP)?

A group of people who share a craft and/or a profession.

A group of Scrum Masters who desire to Improve organizational agility.

7

Lave & Wenger, 1991

Why Create a Scrum Master CoP?

Strong relationships among peers increase job satisfaction and retention of employees.

Crowd-sourced problem solving increases learning.

High-impact practices are more broadly shared while low-impact practices are identified.

8

The Scrum Master serves the organization in several ways, including working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization.

-- The Scrum Guide

Overall Plan

9

Preparing

Getting Started

• Establish Goals and Secure Executive Sponsorship• Identify the Tribe• Establish Affinity Groups

• Introduce the Tribe to Each Other• Review Infrastructure and Core Frameworks• Identify First Mission & Meeting Rhythms

• Identify organizational impediments• Share best practices

Ongoing

Preparing to Launch

10

Establish Goals and Executive Support

Step 1: Identify problems to solve• Inconsistent Scrum practices and degrees of success

• Teams with handoff/integration friction because of incompatible DoDs• Teams will unreliable estimates• Teams who spend too much/too little time in Sprint Planning• Teams who skip Daily Standups or make them too long

Step 2: Promote the CoP as a means to solve them!• The CoP will identify and share high-impact practices• The CoP will provide peer support to Scrum Masters

11

Create a Local Mapping Of Teams and Scrum Masters à This is Your Tribe

12

18

22

5

42

2

CRM and Back Office SystemsFraud Management

Create Affinity Based on Business Units or Shared Areas of Functionality

13

Who Leads the Tribe?

Decide what type of leadership is likely to work best for the organization and people...

• Organizer of group (like a Meetup)• Facilitator of meetings• Collector of “best practices”• Servant Leader• Leader by virtue of expertise• Leader as management function

Identify leaders(s)• By grass roots: Find volunteers• By function: Is there a PMO or other structure that could serve as an

obvious home for the activity? Is there any obvious person to drive?

14

Infrastructure and Tools

15

If you’re a Scrum Master / Agile Coach, how frequently do you meet with your peers?

• Less than once per year• Less than once per quarter• At least once per quarter• Monthly• Weekly

16

POLL QUESTION

Regular Online Teleconferences

17

Asynchronous Groups

18

Hot Seats / Learning Canvas

19http://www.learning30.co/resources

Virtual Conferences

20

Good old fashioned in person meetings

21

Ongoing Operation of the Community

22

Modify and Update Goals

23

Improve Through Retrospectives

24

Start Your Day

Speed Boat

4 box

Remember the Future

(aka Futurespective)

Backpacking

Going Well Retro

Let the Champions Emerge!

25

Share Resources Generously

26

Make it easy and infuse fun

27

Summary

28

Large, Distributed Teams Need CoPs!

Socially: Keeps high-valued employees

Technically: Shares knowledge and skills

High-Impact Practices: Retains “what works here”

Economics: Low-cost, low-risk, high reward

29

Resources / References

Video conferencing: Google Hangouts, Zoom, BlueJeans, Meetup.com, GoToMeeting, WebEx, etc.

Group Instant Messaging: Slack, Hipchat, Spark, Jabber, etc.

Social Media: Facebook, LinkedIn, etc

Virtual co-working: Sococo, Telepresence

Collaborative Frameworks: Weave

30

What do you want for the July 2017 webinar?

• Impact Mapping • Distributed Team Liftoffs / Kickoffs• Building Alignment and Empathy Within Teams• Managing Technical Architectures• Buyer and User Personas• Facilitating Online Meetings• Understanding Problem Types and Problem Solving Strategies• How To Implement Lean Coffee at Scale• My desired topic isn’t listed – email luke.hohmann@conteneo.co

31

POLL QUESTION

Discussions

32

Thank you for attending.

Our next webinar is 14-June-2017 on Estimation and Story Points.

Luke Hohmannconteneo.co

Lisette Sutherlandlisettesutherland.com

Zubin Iranicprime.com