Priorities and roadmaps   product camp
Upcoming SlideShare
Loading in...5
×
 

Priorities and roadmaps product camp

on

  • 310 views

Product Management 101: managing requirements, priorities and roadmaps...Austin ProductCamp June 2008.

Product Management 101: managing requirements, priorities and roadmaps...Austin ProductCamp June 2008.

Statistics

Views

Total Views
310
Views on SlideShare
310
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Priorities and roadmaps   product camp Priorities and roadmaps product camp Presentation Transcript

  • Priorities and RoadmapsGuiding the Successful BusinessPat Scherer patscherer@sbcglobal.netJune 14, 2008 © Copyright 2008 Pat Scherer 1
  • m Gather Prioritize AssignR– E– L – E-A – S – E- S © Copyright 2008 Pat Scherer 2
  • Gather Where do your requirements come from? © Copyright 2008 Pat Scherer 3
  • Gather Where do your requirements come from?Who? Accountable sourcesWhy? How much? Reward for delivery.What is required? Not how it should be implemented.When? Window of opportunity. © Copyright 2008 Pat Scherer 4
  • Organize Gather • By product/service • By parts affected • Duplicates, alternative and conflicting requirementsDocument• Source• Opportunity• Time constraints• Dependencies © Copyright 2008 Pat Scherer 5
  • Gather Anticipate where the opportunity will be, not where it’s been.“World-class marketects approach their task from a perspective of time that distinguishes them from those less skilled.Instead of listening to what customers want now, they extrapolate multiple streams of data, including current requests, to envision what customers will want 18 to 24 months in the future.” – Luke Hohman, Beyond Software Architecture © Copyright 2008 Pat Scherer 6
  • Prioritize What goals spell success for your business?If your company vision is to dominate a market by growing a loyal customer base,why would you use ROI as your sole criteria for prioritizing requirements? Market Leader ROI LTV Niche © Copyright 2008 Pat Scherer 7
  • Process Prioritize • Create a prioritized list • Revalidate opportunity • Review with stakeholdersRanking Systems• Break ties• Separate tactical urgency from strategic importance• ABC, A1, weighted numeric… Document new information surfaced during prioritization discussions. © Copyright 2008 Pat Scherer 8
  • Assign Roadmaps How far out should you plan? Delivery channels Product Release size and cycles complexity © Copyright 2008 Pat Scherer 9
  • Assign Enterprise Execution Product Line Organization Product Releases Framework Architecture Iterate Iterate Requirements Roadmap Iterate Release (3 mo) Iterate Measurement AB C D Plan Harden Design BuildRelease Iterate and Ship (2 wks) Req TestFramework Adapted with permission from work by R. Ritthaler, BMC Corp. 10
  • Process Assign • Estimate resources • Assign to releases • Adjust for dependencies/risk • Review with stakeholders • Manage change Release Content • Top priority “must haves”Document • Best effort additions• Assumptions• Task breakdown• Schedule and assignments• Risk (unknowns/size/complexity)• ROIs, as needed, for prioritization/pricing © Copyright 2008 Pat Scherer 11
  • m Gather Prioritize AssignR– E– L – E-A – S – E- S © Copyright 2008 Pat Scherer 12