Collaboration at Scale: 6 Tips for Effective Product Ownership at a Distance. 9-May-2018

Transcription

1 Collaboration at Scale: 6 Tips for Effective Product Ownership at a Distance 9-May-2018

2 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.

3 TODAY: Product Ownership at a Distance Common Scrum Challenges Dependencies Roadmap Liftoffs Done, Done DAILY SCRUM MEETING (EVERY 24 HOURS) 2-4 WEEK SPRINT Refining CI/CD Retros Value/ ROI PRODUCT BACKLOG Release Planning SPRINT BACKLOG Priorities Tech Debt POTENTIALLY SHIPABLE PRODUCT INCREMENT June 2018: Collaboration at Scale At Scale! 3

4 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 Kent McDonald Luke Hohmann 4

5 POLL QUESTION 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

6 Everyone Knows What And Why! 6

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

8 Opportunity Assessment 8

9 Clarify Responsibilities 9

10 Product Ownership Models Establish clear areas of responsibility for product and development 10

11 Traditional Scrum Cross-Functional Team Product Owner responsible for maximizing the value of the product resulting from work of the Development Team. Scrum Master responsible 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 Team consists of professionals who do the work of delivering a potentially releasable Increment of Done product at the end of each Sprint. 11

12 Complex, Modern Product Core Team Product Manager Responsible for product strategy: market needs, business model, roadmap. Collaborates on experience, understands tarchitecture. Technical Architect Ensures the long term technical architecture aligns to the emerging needs of the business. Customer / User Experience Envisions, develops, manages and optimizes how organizations interact with their customers. Dev Ops Responsible for increasing operational efficiencies, scale. Seeks to increase flow and remove overall bottlenecks. 12

13 Supporting Cast Product Owner Develops story maps, elaborates the backlog (but does not change strategic priorities), acts as proxy for PM on acceptance celebrations. Market Insights Leverages internal / external data sources to feed the team. Graphic Designers A modern SaaS company needs to create beautiful software. Business Analysts Helps manage details of complex business rules and infrastructure requirements / system dependencies. 13

14 Relationship to Dev Teams Extended Team User Story User Story nnn Dev Team 1 Product Core Team Bug Fix Enhanceme nt User Story nnn Backlog Dev Team 2 14

15 Multi-Select Poll QUESTION 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

16 Transparent Dependencies 16

17 Portfolio Alignment Wall Design a transparent view of your portfolio so your teams can identify and manage dependencies 17

18 Refine, Refine, Refine 18

19 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

20 Don t be Sloppy 20

21 Describe Backlog Items Describe backlog items so that you can prevent avoidable questions and clarifications Hand drawn sketches are good! 21

22 Adding Context Helps! 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. 22

23 Clarify Communications 23

24 POLL QUESTION 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 s 24

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

26 Summary 26

27 If you remember nothing else 27

28 References For more information about the techniques described in this webinar, go to To leverage the frameworks described in this webinar, go to: weave.conteneo.co 28

29 Kent McDonald kbp.media Luke Hohmann conteneo.co Thank you for attending Our next webinar will be 13- June-2018 Collaboration at Scale at Scale!