Scrum Alliance Collaboration at Scale Webinar: Agile Roadmapping

Download Scrum Alliance Collaboration at Scale Webinar: Agile Roadmapping

Post on 08-Jan-2017

103 views

Category:

Software

2 download

TRANSCRIPT

<p>PowerPoint Presentation</p> <p>Collaboration at Scale: Agile Roadmapping14-Sep-2016</p> <p>Collaboration at ScaleDesigned 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. </p> <p>Produced by the Scrum Alliance and Conteneo, Inc., were proud of the many distinguished experts who will be joining our series.</p> <p>3Common Scrum ChallengesTech DebtRelease PlanningRoadmapRetrosLiftoffsRefiningValue/ ROIPrioritiesDepend-enciesDone, DoneCI/CD</p> <p>Agenda</p> <p>Why Build a Roadmap?Sadly, Most Roadmaps are BrokenStrategy-Glue-TacticsAgile Roadmapping FormatBuilding Roadmaps at Scale4</p> <p>Jason TannerLaura RichardsonLuke Hohmann</p> <p>4</p> <p>Do You Have a Roadmap?</p> <p>We do not have a roadmap.</p> <p>We have a roadmap but we pretty much ignore it.</p> <p>Our roadmap is somewhat effective in guiding our team.</p> <p>Our roadmap is very effective in guiding our team.</p> <p>5POLL QUESTION</p> <p>5</p> <p>Why We Roadmap6</p> <p>Strategy vs. ExecutionStrategy is a way of thinking about the future that transcends a focus on the immediate. Youre generally not free to pursue any possible strategy (consider regulatory constraints)Prior actions constrain future strategies</p> <p>Execution refers to the set of actions we take to produce the results envisioned in the strategy.</p> <p>Communicating strategic choicesenables effective execution</p> <p>www.LukeHohmann.comCopyright (c) 2001-2003 by Luke Hohmann7</p> <p>Agile Planning Time Horizons</p> <p>DailySprintStrategyPortfolioProductReleaseExecPMDevTeam</p> <p>1-4 wks2-9 mos1 3 yearsyearsmany yearsSprint BacklogPortfolio MapRelease PlanVision &amp; RoadmapOrg levelPlanning levelTime HorizonArtifact</p> <p>Estimates Are Less Precise When Time Horizons are Longer9</p> <p>DailySprintStrategyPortfolioProductRelease</p> <p>1 2 QTRS</p> <p>1 2 Months1 2 DaysRoadmap Time Horizon? 1-2 yearsRelease Plan: 3 9 monsSprint: 3 wksNote that as the time horizon increases the precision of our projections decreases. We still plan. </p> <p>Most Roadmaps are Broken!</p> <p>Why?10</p> <p>I know exactly what should be on the roadmap!</p> <p>Created Unilaterally</p> <p>No Visible Logic</p> <p>No visible logic: presents only answers, so reader cant judge quality of decisions or identify trade-offs. Requires Product Manager (PM) to present roadmap personally, over and over and over again</p> <p>13</p> <p>4/17/1</p> <p>1/1Cust A</p> <p>10/1GAQ2</p> <p>R5.3/R6Project DeliveraryProject DesignR5.2Maintenance Release</p> <p>Server &amp; Apps</p> <p>Storage+</p> <p>Custom ProjectTarget DatesCust BGAQ1RAMay</p> <p>GAAug</p> <p>DBR5.1AnalysisRoadmap (from a Startup Board Presentation!)</p> <p>Insufficient detail content, context and connection to SALES!14</p> <p>4/17/1</p> <p>1/1Cust A</p> <p>10/1GAQ2</p> <p>R5.3/R6Project DeliveraryProject DesignR5.2Maintenance Release</p> <p>Server &amp; Apps</p> <p>Storage+</p> <p>Custom ProjectTarget DatesCust BGAQ1RAMay</p> <p>GAAug</p> <p>DBR5.1AnalysisRoadmap (from a Startup Board Presentation!)</p> <p>Insufficient detail content, context and connection to SALES!15</p> <p>Q105</p> <p>Objective: 5.1 Maintenance release</p> <p>Product Highlights: Performance &amp; securityDelivery Timeline: 5.1 GA 3/18Objective: 5.2 Server performanc monitoring (Phase 1)Product Highlights: Reporting and analysis for servers and applications Partner integrationDelivery Timeline: End Q2 GA Reporting End Q3 GA Analysis</p> <p>Objective: 5.3 Server performance monitoring (Phase 2)Product Highlights: More data sources Packaged applications Additional analysis models Optimization analytics Partner requirementsDelivery Timeline: Q4-Q1Q205Q305-Q106Product Roadmap (Basic Timeline)</p> <p>Missing detail, logic and marketing16</p> <p>Q105</p> <p>Objective: 5.1 Maintenance release</p> <p>Product Highlights: Performance &amp; securityDelivery Timeline: 5.1 GA 3/18Objective: 5.2 Server performanc monitoring (Phase 1)Product Highlights: Reporting and analysis for servers and applications Partner integrationDelivery Timeline: End Q2 GA Reporting End Q3 GA Analysis</p> <p>Objective: 5.3 Server performance monitoring (Phase 2)Product Highlights: More data sources Packaged applications Additional analysis models Optimization analytics Partner requirementsDelivery Timeline: Q4-Q1Q205Q305-Q106Product Roadmap (Basic Timeline)</p> <p>Missing detail, logic and marketing17</p> <p>Poor input from Engineering, Marketing or Sales</p> <p>Poor technical and market inputs: wrong people participating. Some from each department assigned, but mostly include junior or non-core members</p> <p>18</p> <p>Lack of buy-in</p> <p>Lack of organizational buy-in: Engineering doesnt believe roadmap, since resources are insufficient. Sales/Mktg doesnt believe roadmap, since it has been historically inaccurate. Dead on arrival</p> <p>No plan for internal/external sharing: e.g. sales team shares early or internal versions with customers, then demands delivery on fixed schedule. </p> <p>19</p> <p>Outcome:Unable to Execute = Fail to Deliver</p> <p>Roadmaps Bridge the Gap between</p> <p>Visionand</p> <p>Product Backlog</p> <p>The Gateshead Millennium Bridge is sometimes referred to as the 'Blinking Eye Bridge' or the 'Winking Eye Bridge' due to its shape and its tilting method. Its a pedestrian and cyclist tilt bridge spanning the River Tyne in England.21</p> <p>Benefits of a RoadmapRoadmaps match short-term plans and long-term strategic goals with specific technology solutions to help meet those goals.</p> <p>Internally:Becomes the filter for prioritizing developmentGains consensus around directionEnsures the ship is headed in the right directionAvoids the last/loudest priority problem</p> <p>Externally:Provides customers with access to near-term commitments and long term points of viewBinds customers to your company</p> <p>www.enthiosys.com22</p> <p>Roadmaps are Scary Forces you to articulate what you are not going to build</p> <p>Motivates commitments to uncertain futures</p> <p>www.enthiosys.com23</p> <p>Where Roadmaps Fit into Scrum:</p> <p>Strategy-Glue-Tactics forAgile Product Management24</p> <p>25StrategyTacticsGlueLonger termHolisticShorter TermFocused ProductVisionProduct PurposeWhy</p> <p>Roadmap</p> <p>User Story map</p> <p>Backlog</p> <p>Release Plan</p> <p>Lean CanvasBusiness Model Canvas</p> <p>Business Drivers</p> <p>Sprint</p> <p>26StrategyTacticsGlueLonger termHolisticShorter TermFocused ProductVisionProduct PurposeWhy</p> <p>Roadmap</p> <p>User Story map</p> <p>Backlog</p> <p>Release Plan</p> <p>Lean CanvasBusiness Model Canvas</p> <p>Business Drivers</p> <p>Sprint</p> <p>FeatureUser storyBug FixEnhancementUser Story</p> <p>Roadmaps and Backlogs Are Independent But Linked</p> <p>releasereleaseInfiniteBacklog</p> <p>28StrategyTacticsGlueLonger termHolisticShorter TermFocused ProductVisionProduct PurposeWhy</p> <p>Roadmap</p> <p>User Story map</p> <p>Backlog</p> <p>Release Plan</p> <p>Lean CanvasBusiness Model Canvas</p> <p>Business Drivers</p> <p>Sprint</p> <p>Prune The Product Tree</p> <p>Speed Boat</p> <p>Vision Box</p> <p>Me and My Shadow</p> <p>Start Your DayBuy a Feature</p> <p>Whole Product</p> <p>Agile Roadmap Format and Structure29http://bit.ly/roadmapping-patterns</p> <p>A Good Roadmap Glues Strategy to TacticsWHOare my markets/market segments? </p> <p>WHATfeatures and benefits will they pay for?</p> <p>WHENand how frequently should I release? </p> <p>HOWwill my technical architecture evolve?</p> <p>WHATmarketing events will drive awareness/sales?</p> <p>AREthere any external factors to address?</p> <p>www.enthiosys.com30</p> <p>Example Roadmap31Color Coded Feature CategoriesTechnical Team Unsure of How to Solve ProblemQ1Q2Q4Q1Parking LotBlocking ScheduleMarketing Not Sure When This Should Be DeliveredTarget Market Split into Two SegmentsQ3WHOWHYWHENHOW</p> <p>Building Your Roadmap32</p> <p>How was Your Roadmap Created?Select all that apply.</p> <p>CEO/VP/Senior Leaders create our roadmap</p> <p>Product Manager / Product Owner creates our roadmap</p> <p>Customers are consulted in developing our roadmap</p> <p>Architects/Engineering Leaders are consulted in developing our roadmap</p> <p>33POLL QUESTION</p> <p>33</p> <p>34Gather DataPreparingEngagingOngoingUpdate Quarterly</p> <p>One-day Roadmap Jam</p> <p>2-4 weeks</p> <p>FinalizeGet The Right PeopleProduct ManagementProduct MarketingEngineeringUpdate When MessyUpdate Upon ReleaseUpdate on Competitive Moves</p> <p>Prune the Product Tree Can Help!Update for New Tech Opportunity</p> <p>Online RoadmappingThe Scrum Alliance used Prune the Product Tree to capture ideas on how to grow the Scrum Alliance.5 Forums35 participants 100 potential apples81 unique applesEach forum lasted about ~1 hour</p> <p>36Online Roadmapping</p> <p>ReleaseNReleaseN+1Future</p> <p>ReleaseNReleaseN+1</p> <p>In-Person Roadmapping37</p> <p>11 meters2 meters</p> <p>Summary38</p> <p>38</p> <p>We Roadmap So Should YouRoadmaps communicate strategic intentions </p> <p>Roadmaps provide the glue between strategy and tactics</p> <p>Roadmaps enable organizations to have effective conversations with all stakeholders39</p> <p>References and ResourcesRoadmapping Pattern Language: http://bit.ly/roadmapping-patterns</p> <p>Prune the Product Tree: www.innovationgames.com/prune-the-product-tree</p> <p>Scrum Alliance Roadmapping Case Study: http://bit.ly/1JGY8zz</p> <p>40</p> <p>40</p> <p>Picking the Next Webinar41</p> <p>What do you want for the Nov 2016 webinar?Identifying and Prioritizing Technical Debt Distributed Team Release Planning Impact Mapping Distributed Team Liftoffs / KickoffsBacklog Refinement Building Alignment and EmpathyBuilding a ScrumMaster Community of Practice My desired topic isnt listed email luke.hohmann@conteneo.co</p> <p>42POLL QUESTION</p> <p>http://bit.ly/collab-at-scale43</p> <p>Discussions44</p> <p>Thank you for attending</p> <p>Pick our next webinar:</p> <p>http://bit.ly/collab-at-scale</p> <p>Luke Hohmannconteneo.co</p> <p>Jason Tannerappliedframeworks.com</p> <p>Laura Richardson conteneo.co</p>