Collaboration at Scale: 6 Tips for Effective Product Ownership at a Distance9-May-2018

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 will be joining our series.

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/ ROI

Priorities

Depend-encies

Done, Done

CI/CD

TODAY:Product Ownership at a Distance

June 2018:Collaboration at Scale – At Scale!

Agenda

1 Everyone Knows What – And Why!

2 Clarify Responsibilities

3 Transparent Dependencies

4 Refine, Refine, Refine

5 Don’t be Sloppy

6 Clarify Communications

4

Kent McDonald

Luke Hohmann

What best describes your current situation?

1. All of our product owners are collocated with our development teams.

2. All of our product owners are not collocated with our development teams.

3. Some of our product owners are collocated with our development teams, and some are remote.

4. We all work in different places

5

POLL QUESTION

Everyone Knows What – And Why!

6

Problem Statement

Build shared understanding so that everyone knows what they’re building and why they are building it!

Opportunity Assessment

8

Clarify Responsibilities

9

Product Ownership Models

10

Establish clear areas of responsibility for product and development

Traditional Scrum Cross-Functional Team

Product Ownerresponsible for maximizing the value of the product resulting from work of the Development Team.

Scrum Masterresponsible for promoting and supporting Scrum as defined in the Scrum Guide. Scrum Masters do this by helping everyone understand Scrum theory, practices, rules, and values.

Dev Teamconsists of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the end of each Sprint.

11

Product ManagerResponsible for product strategy: market needs, business model, roadmap. Collaborates on experience, understands tarchitecture.

Complex, Modern Product “Core” Team

Dev OpsResponsible for increasing operational efficiencies, scale. Seeks to increase flow and remove overall bottlenecks.

Technical ArchitectEnsures the long term technical architecture aligns to the emerging needs of the business.

Customer / User ExperienceEnvisions, develops, manages and optimizes how organizations interact with their customers.

12

Supporting Cast

Product OwnerDevelops story maps, elaborates the backlog (but does not change strategic priorities), acts as proxy for PM on acceptance celebrations.

Business AnalystsHelps manage details of complex business rules and infrastructure requirements / system dependencies.

Market InsightsLeverages internal / external data sources to feed the team.

Graphic Designers A modern SaaS company needs to create beautiful

software.

13

Relationship to Dev Teams

Product Core Team

Extended Team

User StoryUser Story

nnn

Bug FixEnhancementUser Story

nnn

Backlog

Dev Team1

Dev Team2

14

Which roles are in or used in your team? Select all that apply.

• Product Manager• Product Owner• Business Analyst• Technical Architect• Dev Ops• Customer / User Experience• Graphic Designer• Market Insights

15

Multi-Select Poll QUESTION

Transparent Dependencies

16

Portfolio Alignment Wall

Design a transparent view of your portfolio so your teams can identify and manage dependencies

17

Refine, Refine, Refine

18

Discovery Board

Create a clear backlog refinement process so that your teams know which backlog items are ready to work on and what’s coming up next

19

Don’t be Sloppy

20

Describe Backlog Items

Describe backlog items so that you can prevent avoidable questions and clarifications

21

Hand drawn sketches are good!

Adding Context Helps!

22

Example (from our Conteneo’s current Sprint):

Context: A lot of our customers use spreadsheets like Microsoft Excel or Google Sheets. They’re used to ”directly editing” items in the spreadsheet. Weavers can directly edit items in Buy a Feature. Let’s add this to Idea Engine!

Story: As a participant I want to edit the name and description of items in the List View without having to click on the item and go somewhere else. Of course, I can't edit the Region data - for that I have to move the item. But it would make Idea Engine a lot more natural and easier to use if I could edit the name and description in the List view.

Clarify Communications

23

What’s your biggest communication challenge?

• Keeping track of information about specific backlog items• Some members of the team are always left off important

discussions• Time dilation (split across several time zones)• Too many emails

24

POLL QUESTION

Working Agreements

Clarify your communication methods so your teams know how best to collaborate at a distance

25

Summary

26

If you remember nothing else…

27

References

For more information about the techniques described in this webinar, go to www.kbp.media/go/remote-po/

28

To leverage the frameworks described in this webinar, go to: weave.conteneo.co

Thank you for attending

Our next webinar will be 13-June-2018 Collaboration at Scale – at Scale!

Luke Hohmannconteneo.co

Kent McDonaldkbp.media