Collaboration at Scale: Managing Dependencies Across Large Teams Aug-10

Transcription

1 Collaboration at Scale: Managing Dependencies Across Large Teams 2016-Aug-10

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 CSPOs, ScrumMasters, and Scrum teams. Produced by the Scrum Alliance and Conteneo, Inc., we re proud of the many distinguished experts who will be joining our series.

3 Agenda 1 Dependencies and Collaborations Brent Barton 2 Understanding Dependencies 3 Strategies and Patterns for Creating and Managing High-Impact, Effective Dependencies Venkatesh Krishnamurthy Luke Hohmann 3

4 The Scrum Framework DAILY SCRUM MEETING (EVERY 24 HOURS) 2-4 WEEK SPRINT PRODUCT BACKLOG SPRINT BACKLOG POTENTIALLY SHIPABLE PRODUCT INCREMENT 4

5 Common Scrum Challenges Dependencies Roadmap Liftoffs Done, Done DAILY SCRUM MEETING (EVERY 24 HOURS) 2-4 WEEK SPRINT Refining CI/CD Retros Value/R OI PRODUCT BACKLOG Release Planning SPRINT BACKLOG Priorities Tech Debt POTENTIALLY SHIPABLE PRODUCT INCREMENT 5

6 Dependent A team who needs someone, another team, or something in order to complete their work. 6

7 We Have Lots of Dependencies Let me clarify this Backlog Item We can pair on this Component or Service Provider Consumer Product Owners Scrum Teams (Task Board) Society for Worldwide Interbank Financial Telecommunication 7

8 POLL QUESTION What dependencies are you trying to manage (please select all that apply)? Within the team / between team members Multi-Team Dependencies (such as teams in different time zones) Management Dependencies (such as approvals for requests) Business Process (such as approvals before releasing code) Technical Dependencies (you re a piece of a larger solution) Regulatory approvals or requirements Vendors or 3 rd party service providers 8

9 Collaboration = Positive Dependencies Collaboration is a recursive process where two or more people or organizations work together in an intersection of common goals for example, an intellectual endeavor that is creative in nature by sharing knowledge, learning and building consensus. Thanks, Wikipedia 9

10 We Don t Like It When Let me clarify this Backlog Item We can pair on this Component or Service Provider Consumer Product Owners Scrum Teams (Task Board) Society for Worldwide Interbank Financial Telecommunication 10

11 Organizational Engineering A first step towards dealing with dependencies is understanding explicit and implicit choices that create and sustain them. 11

12 Structural Dependency Outcome Dependency PRODUCT BACKLOG Process Dependency 12

13 Conway s Law Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure. 13

14 14

15 15

16 Designing Your Organization Some patterns and techniques for designing effective organizations. 16

17 POLL QUESTION Who manages dependencies in your teams? Scrum Master Product Owner Project Manager Program Manager Engineering Manager Team themselves 17

18 The Core of Scrum is the Team Product Owner Responsible for maximizing the value of the product and the work of the Development Team. Scrum Master Fulfills the duties of the Scrum Master as defined in The Scrum Guide (there are more than you think you remember!) Development Team The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of Done product at the end of each Sprint. 18

19 When You re Smaller / Simpler Deliver working code to a customer Deliver working code to a customer Deliver working code to a customer Customer Centric Feature Teams Customer Centric Feature Teams Customer Centric Feature Teams 19

20 When You Get a Bit Bigger Customer Centric Feature Teams Customer Centric Feature Teams Component Teams (Service Teams) Shared Shared Service or Shared Service or Component Shared Service or Component Service or Component Component 20

21 Managing Architectural Governance Virtual Architecture Team Architect Also Implements Customer Centric Feature Teams Component Teams 21

22 Visible Architecture 22

23 When in Doubt, Print it Out Which teams are working on what market-facing products? Which teams are working on what internal services? Which teams are working on what components? 23

24 When in Doubt, Print it Out Service Team Releases Which teams rely on what services and components? 24

25 Integration Stories à CI/CD Normal Backlog Item Integration Story 25

26 Summary 26

27 Design Your Dependencies All sorts of dependencies exist When they re healthy, we call them collaborations You can design your dependencies to be more effective

28 Picking the Next Webinar 28

29 POLL QUESTION What do you want for the Oct 2016 webinar? Identifying and Prioritizing Technical Debt Distributed Team Release Planning Impact Mapping Distributed Team Liftoffs / Kickoffs Creating Value-Based Backlogs Prioritizing Backlogs for Business Value Building Alignment and Empathy in Distributed Teams Building a ScrumMaster Community of Practice Agile Outside of IT/SW Development Organizations 29

30 30

31 Discussions 31

32 Brent Barton SolutionsIQ.com Venkatesh Krishnamurthy Luke Hohmann conteneo.co Thank you for attending Pick our next webinar: