Keeping sanity when moving to agile   austin 2013
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Keeping sanity when moving to agile austin 2013

  • 192 views
Uploaded on

Product Management challenges with Agile - presented at Product Camp Austin, 2/16/13

Product Management challenges with Agile - presented at Product Camp Austin, 2/16/13

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
192
On Slideshare
192
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
4
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. ProductCamp 2013Keeping your Product ManagementSanity when moving to AgileJohn Milburn jmilburn@pragmaticmarketing.com
  • 2. 3 EXECUTION EXECUTIONProblems Market STRATEGY STRATEGY
  • 3. EXECUTIONSTRATEGY User UI Design? Stories? User Use Cases? Acceptance? Functional Always Iteration Design? Available? Planning 4
  • 4. Working software is the measure of the team’sprogress It doesn’t mean “no documentation”“Design” may be expressed with prototypes It doesn’t mean “no design”Testing and quality are the responsibility of theteam It doesn’t mean “no QA” 5
  • 5. Requirements –> User StoriesMRD / MRT / PRD –> Backlog(s)Hours/Days/Weeks –> VelocityStatus Meetings –> Standups / ScrumsProject Status –> Burnups, BurndownsPM / Designer –> PM / PO / DesignerRelease Milestones –> Sprints / Iterations 6
  • 6. Greater flexibility to deal with changeWe know earlier when we are in troubleWe have a greater sense of accomplishmentGreater Product Management –Development TRUSTThe time commitment has increased dramatically 7
  • 7. Product Mgt is Accountable for Market Requirements Writing Grouping PrioritizingIt is impossible to prioritize 100’s of requirementsPrioritization is based on VALUE to the MarketPM owns the WHAT, Dev owns the HOW 8
  • 8. Market Problems define the productWe still must balance Scope vs. Time vs. MoneyWe need to release something sometimeWe need to make moneyPeople are involved 9
  • 9. Waterfall Planning 10 Marketing Launch Plan Plan Design SpecProduct BusinessRoadmap Plan Requirements LAUNCH Project System Build / Test Test Plan Business Start Release Gate Gate GateMaster Requirements List Goals / Themes Market Requirements Document Market Requirements Table
  • 10. Waterfall Planning - Accountability 11 -- Product Manager -- Development -- Product Marketing Manager Marketing Launch Plan Plan Design SpecProduct BusinessRoadmap Plan Requirements LAUNCH Project System Build / Test Test Plan Business Start Release Gate Gate GateMaster Requirements List Goals / Themes Market Requirements Document Market Requirements Table
  • 11. Agile Planning 12 Marketing Launch Plan Plan Arch /Design User Stories Burnups /Product Business BurndwnsRoadmap Plan LAUNCH Overall Project Sprint Sprint System Plan Build(s) Plan(s) Test(s) Test Business Start Release Gate Gate(s) Demo(s) GateProduct Backlog Release Backlog Sprint Backlogs
  • 12. Agile Planning - Accountability 13 -- Product Manager -- Product Owner -- Development -- Product Marketing Manager Marketing Launch Plan Plan Arch /Design User Stories Burnups / BurndwnsProduct BusinessRoadmap Plan LAUNCH Overall Project Sprint Sprint System Plan Build(s) Plan(s) Test(s) Test Business Start Release Gate Gate(s) Demo(s) GateProduct Backlog Release Backlog Sprint Backlogs
  • 13. UnderstaffingWaterfall management with Agile developmentStill must develop mutual trustDistributed teams make it harderWe must have time to communicate 14
  • 14. Thanks !jmilburn@pragmaticmarketing.com