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

Embed Size (px)

TRANSCRIPT

PowerPoint Presentation

Collaboration at Scale: Agile Roadmapping14-Sep-2016

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.

Produced by the Scrum Alliance and Conteneo, Inc., were proud of the many distinguished experts who will be joining our series.

3Common Scrum ChallengesTech DebtRelease PlanningRoadmapRetrosLiftoffsRefiningValue/ ROIPrioritiesDepend-enciesDone, DoneCI/CD

Agenda

Why Build a Roadmap?Sadly, Most Roadmaps are BrokenStrategy-Glue-TacticsAgile Roadmapping FormatBuilding Roadmaps at Scale4

Jason TannerLaura RichardsonLuke Hohmann

4

Do You Have a Roadmap?

We do not have a roadmap.

We have a roadmap but we pretty much ignore it.

Our roadmap is somewhat effective in guiding our team.

Our roadmap is very effective in guiding our team.

5POLL QUESTION

5

Why We Roadmap6

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

Execution refers to the set of actions we take to produce the results envisioned in the strategy.

Communicating strategic choicesenables effective execution

www.LukeHohmann.comCopyright (c) 2001-2003 by Luke Hohmann7

Agile Planning Time Horizons

DailySprintStrategyPortfolioProductReleaseExecPMDevTeam

1-4 wks2-9 mos1 3 yearsyearsmany yearsSprint BacklogPortfolio MapRelease PlanVision & RoadmapOrg levelPlanning levelTime HorizonArtifact

Estimates Are Less Precise When Time Horizons are Longer9

DailySprintStrategyPortfolioProductRelease

1 2 QTRS

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.

Most Roadmaps are Broken!

Why?10

I know exactly what should be on the roadmap!

Created Unilaterally

No Visible Logic

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

13

4/17/1

1/1Cust A

10/1GAQ2

R5.3/R6Project DeliveraryProject DesignR5.2Maintenance Release

Server & Apps

Storage+

Custom ProjectTarget DatesCust BGAQ1RAMay

GAAug

DBR5.1AnalysisRoadmap (from a Startup Board Presentation!)

Insufficient detail content, context and connection to SALES!14

4/17/1

1/1Cust A

10/1GAQ2

R5.3/R6Project DeliveraryProject DesignR5.2Maintenance Release

Server & Apps

Storage+

Custom ProjectTarget DatesCust BGAQ1RAMay

GAAug

DBR5.1AnalysisRoadmap (from a Startup Board Presentation!)

Insufficient detail content, context and connection to SALES!15

Q105

Objective: 5.1 Maintenance release

Product Highlights: Performance & 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

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)

Missing detail, logic and marketing16

Q105

Objective: 5.1 Maintenance release

Product Highlights: Performance & 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

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)

Missing detail, logic and marketing17

Poor input from Engineering, Marketing or Sales

Poor technical and market inputs: wrong people participating. Some from each department assigned, but mostly include junior or non-core members

18

Lack of buy-in

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

No plan for internal/external sharing: e.g. sales team shares early or internal versions with customers, then demands delivery on fixed schedule.

19

Outcome:Unable to Execute = Fail to Deliver

Roadmaps Bridge the Gap between

Visionand

Product Backlog

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

Benefits of a RoadmapRoadmaps match short-term plans and long-term strategic goals with specific technology solutions to help meet those goals.

Internally:Becomes the filter for prioritizing developmentGains consensus around directionEnsures the ship is headed in the right directionAvoids the last/loudest priority problem

Externally:Provides customers with access to near-term commitments and long term points of viewBinds customers to your company

www.enthiosys.com22

Roadmaps are Scary Forces you to articulate what you are not going to build

Motivates commitments to uncertain futures

www.enthiosys.com23

Where Roadmaps Fit into Scrum:

Strategy-Glue-Tactics forAgile Product Management24

25StrategyTacticsGlueLonger termHolisticShorter TermFocused ProductVisionProduct PurposeWhy

Roadmap

User Story map

Backlog

Release Plan

Lean CanvasBusiness Model Canvas

Business Drivers

Sprint

26StrategyTacticsGlueLonger termHolisticShorter TermFocused ProductVisionProduct PurposeWhy

Roadmap

User Story map

Backlog

Release Plan

Lean CanvasBusiness Model Canvas

Business Drivers

Sprint

FeatureUser storyBug FixEnhancementUser Story

Roadmaps and Backlogs Are Independent But Linked

releasereleaseInfiniteBacklog

28StrategyTacticsGlueLonger termHolisticShorter TermFocused ProductVisionProduct PurposeWhy

Roadmap

User Story map

Backlog

Release Plan

Lean CanvasBusiness Model Canvas

Business Drivers

Sprint

Prune The Product Tree

Speed Boat

Vision Box

Me and My Shadow

Start Your DayBuy a Feature

Whole Product

Agile Roadmap Format and Structure29http://bit.ly/roadmapping-patterns

A Good Roadmap Glues Strategy to TacticsWHOare my markets/market segments?

WHATfeatures and benefits will they pay for?

WHENand how frequently should I release?

HOWwill my technical architecture evolve?

WHATmarketing events will drive awareness/sales?

AREthere any external factors to address?

www.enthiosys.com30

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

Building Your Roadmap32

How was Your Roadmap Created?Select all that apply.

CEO/VP/Senior Leaders create our roadmap

Product Manager / Product Owner creates our roadmap

Customers are consulted in developing our roadmap

Architects/Engineering Leaders are consulted in developing our roadmap

33POLL QUESTION

33

34Gather DataPreparingEngagingOngoingUpdate Quarterly

One-day Roadmap Jam

2-4 weeks

FinalizeGet The Right PeopleProduct ManagementProduct MarketingEngineeringUpdate When MessyUpdate Upon ReleaseUpdate on Competitive Moves

Prune the Product Tree Can Help!Update for New Tech Opportunity

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

36Online Roadmapping

ReleaseNReleaseN+1Future

ReleaseNReleaseN+1

In-Person Roadmapping37

11 meters2 meters

Summary38

38

We Roadmap So Should YouRoadmaps communicate strategic intentions

Roadmaps provide the glue between strategy and tactics

Roadmaps enable organizations to have effective conversations with all stakeholders39

References and ResourcesRoadmapping Pattern Language: http://bit.ly/roadmapping-patterns

Prune the Product Tree: www.innovationgames.com/prune-the-product-tree

Scrum Alliance Roadmapping Case Study: http://bit.ly/1JGY8zz

40

40

Picking the Next Webinar41

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

Recommended

View more >