Collaboration at Scale: at Scale! 13-June-2018

Transcription

1 Collaboration at Scale: at Scale! 13-June-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. Luke Hohmann Produced by the Scrum Alliance and Conteneo, Inc., we re proud of the many distinguished experts who will be joining our series.

3 TODAY: How to Improve the Webinar 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 July 2018: Scrum in Government 3

4 We ve covered a lot! Enterprise Retrospectives 6 Tips for Effective Product Ownership at a Distance Managing Dependencies Across Large Teams Building Alignment and Empathy Advanced Roadmapping at Scale Defining Done, Ready, and NO for Distributed Teams Release Planning Tips and Techniques Collaborating with Thousands to Millions of Stakeholders to Prioritize City Budgets and Grow Communities Managing Technical Architectures How to Prioritize a Backlog Identifying Customer/Stakeholder Requirements Collaboration at Scale Kick Off Estimation and Story Points Backlog Refinement at Scale Creating Value-Based Backlogs Identifying and Prioritizing Technical Debt Distributed Team Release Planning Keeping Retrospectives Fresh Agile Roadmapping Budgeting and Agile Portfolio Management User Story Mapping at Scale Building a ScrumMaster Community of Practice Impact Mapping at Scale Problem Types and Strategies 4

5 We ve covered a lot! Enterprise Retrospectives 6 Tips for Effective Product Ownership at a Distance Managing Dependencies Across Large Teams Building Alignment and Empathy Advanced Roadmapping at Scale Defining Done, Ready, and NO for Distributed Teams Release Planning Tips and Techniques Collaborating with Thousands to Millions of Stakeholders to Prioritize City Budgets and Grow Communities Managing Technical Architectures How to Prioritize a Backlog Identifying Customer/Stakeholder Requirements Collaboration at Scale Kick Off Estimation and Story Points Backlog Refinement at Scale Creating Value-Based Backlogs Identifying and Prioritizing Technical Debt Distributed Team Release Planning Keeping Retrospectives Fresh What s Next? Agile Roadmapping Budgeting and Agile Portfolio Management User Story Mapping at Scale Building a ScrumMaster Community of Practice Impact Mapping at Scale Problem Types and Strategies 5

6 How do we improve collaboration in your organization? What knowledge, skills and experiences do you need? What are your impediments? What are your enablers? 6

7 How Big is a Team in Scrum? 3 9 people! Development Team Size Optimal Development Team size is small enough to remain nimble and large enough to complete significant work within a Sprint. Fewer than three Development Team members decrease interaction and results in smaller productivity gains. Smaller Development Teams may encounter skill constraints during the Sprint, causing the Development Team to be unable to deliver a potentially releasable Increment. Having more than nine members requires too much coordination. Large Development Teams generate too much complexity for an empirical process to be useful. 7

8 We ll organize today s forums the same way! Weave will automatically organize forums Some forums will have facilitators Webinar Participants Webinar Participants Organized into Forums

9 Join the forum in two steps 1 2 Weave creates a free trial account so that we can manage your data in a GDPR compliant manner. Enter your name and address. Don t worry you will NOT be charged anything and your data will NOT be shared with any outside services. 9

10 Drag these items on the image Chat with others 10

11 10 Forum Progression Start on the left and spend about 10 minutes exploring Knowledge, Skills and Experience. 10 Then spend about 10 minutes exploring impediments and enablers. 10 Spend 10 min exploring all ideas 11

12 Let s Join the Forums! 12

13 Next Steps 13

14 Making the Webinar Batter Forum results will be analyzed to identify patterns. We ll create new webinars to address common problems. We ll share key results with the community. 14

15 Luke Hohmann conteneo.co Thank you for attending Our next webinar will be Scaling Scrum for Cities!