Scrum gathering vegas   agile program and portfolio management
Upcoming SlideShare
Loading in...5
×
 

Scrum gathering vegas agile program and portfolio management

on

  • 4,644 views

 

Statistics

Views

Total Views
4,644
Views on SlideShare
2,105
Embed Views
2,539

Actions

Likes
2
Downloads
103
Comments
0

10 Embeds 2,539

http://www.leadingagile.com 2042
http://agile.dzone.com 477
http://www.newsblur.com 7
http://newsblur.com 5
http://feeds.feedburner.com 2
http://www.1agile.com 2
http://www.dzone.com 1
https://twitter.com 1
http://webcache.googleusercontent.com 1
http://feedspot.com 1
More...

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

    Scrum gathering vegas   agile program and portfolio management Scrum gathering vegas agile program and portfolio management Presentation Transcript

    • Agile Program and PortfolioManagement with ScrumWednesday, May 8, 13
    • Agile Program and PortfolioManagement with ScrumWhere does well groomed prioritized backlogcome from... at scale?Wednesday, May 8, 13
    • Mike Cottmeyermike@leadingagile.com404.312.1471www.leadingagile.comtwitter.com/mcottmeyerfacebook.com/leadingagilelinkedin.com/in/cottmeyerWednesday, May 8, 13
    • Why Scrum?Wednesday, May 8, 13
    • C-SuiteValue Proposition• Predictability• Quality• Early ROI• Cost SavingsWednesday, May 8, 13
    • C-SuiteValue Proposition•Predictability• Quality• Early ROI• Cost SavingsWednesday, May 8, 13
    • C-SuiteValue Proposition• Predictability•Quality• Early ROI• Cost SavingsWednesday, May 8, 13
    • C-SuiteValue Proposition• Predictability• Quality•Early ROI• Cost SavingsWednesday, May 8, 13
    • C-SuiteValue Proposition• Predictability• Quality• Early ROI•Cost SavingsWednesday, May 8, 13
    • Competing Delivery Goals• Emergence• ConvergenceWednesday, May 8, 13
    • Competing Delivery Goals•Emergence• ConvergenceWednesday, May 8, 13
    • Competing Delivery Goals• Emergence•ConvergenceWednesday, May 8, 13
    • Projects, Programs, PortfoliosWednesday, May 8, 13
    • Agile Project ManagementScrumTeamScrumTeamScrumTeamScrumTeamWednesday, May 8, 13
    • Agile Program ManagementScrumTeamProductTeamScrumTeamScrumTeamScrumTeamProductTeamWednesday, May 8, 13
    • Agile Portfolio ManagementScrumTeamProductTeamScrumTeamScrumTeamScrumTeamProductTeamPortfolioTeamWednesday, May 8, 13
    • Enterprise Portfolio ManagementScrumTeamProductTeamScrumTeamScrumTeamScrumTeamProductTeamStrategyTeamSupportTeamPortfolioTeamWednesday, May 8, 13
    • Foundational Stuff...Anatomy of a Scrum TeamWednesday, May 8, 13
    • ScrumTeamWednesday, May 8, 13
    • ScrumTeam DevelopersWednesday, May 8, 13
    • ScrumTeam DevelopersTestersWednesday, May 8, 13
    • ScrumTeam DevelopersTestersAnalystsWednesday, May 8, 13
    • ScrumTeam DevelopersTestersAnalystsLeadWednesday, May 8, 13
    • ScrumTeam DevelopersTestersAnalystsScrumMasterLeadWednesday, May 8, 13
    • ScrumTeam DevelopersTestersAnalystsScrumMasterProduct OwnerLeadWednesday, May 8, 13
    • Teams at Every LevelScrumTeamProductTeamScrumTeamScrumTeamScrumTeamProductTeamStrategyTeamSupportTeamPortfolioTeamWednesday, May 8, 13
    • Scrum Teams• Clarity• Accountability• MeasurableprogressWednesday, May 8, 13
    • Scrum Teams• Clarity• Accountability• MeasurableprogressWednesday, May 8, 13
    • Scrum Teams• Clarity• Accountability• MeasurableprogressWednesday, May 8, 13
    • Scrum Teams• Clarity• Accountability• MeasurableprogressWednesday, May 8, 13
    • Foundational Stuff...Time, Cost, and ScopeWednesday, May 8, 13
    • ScopeCostTimeWednesday, May 8, 13
    • ScopeCostTimeWednesday, May 8, 13
    • CostTimeValueScopeWednesday, May 8, 13
    • ManagingVariable ScopeHow to deal with making commitments when scope isconstantly changingWednesday, May 8, 13
    • Story MapsWednesday, May 8, 13
    • EpicEpics  collec*ons  of  features,  typically  1-­‐3  months  in  dura*on.    Epics  span  releases.    Epics  can  span  more  than  one  team.    These  are  the  things  senior  leadership  cares  about.  Wednesday, May 8, 13
    • EpicFeatureEpics  collec*ons  of  features,  typically  1-­‐3  months  in  dura*on.    Epics  span  releases.    Epics  can  span  more  than  one  team.    These  are  the  things  senior  leadership  cares  about.  Features  are  smaller  than  epics,  typically  2-­‐4  weeks  in  dura*on.    Features  are  contained  within  releases.    Features  are  contained  within  a  team.    These  are  what  the  Product  Owner  Cares  about.    Wednesday, May 8, 13
    • EpicFeatureUser  StoryEpics  collec*ons  of  features,  typically  1-­‐3  months  in  dura*on.    Epics  span  releases.    Epics  can  span  more  than  one  team.    These  are  the  things  senior  leadership  cares  about.  Features  are  smaller  than  epics,  typically  2-­‐4  weeks  in  dura*on.    Features  are  contained  within  releases.    Features  are  contained  within  a  team.    These  are  what  the  Product  Owner  Cares  about.    User  Stories  are  the  smallest  increment  of  value,  typically  less  than  a  week.    User  Stories  are  contained  within  sprint.    These  are  the  things  Engineering  Management  Cares  about.  Wednesday, May 8, 13
    • EpicFeatureUser  StoryFeature Feature FeatureUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryStory  Maps  visually  show  the  rela*onship  between  User  Stories  and  Business  ValueWednesday, May 8, 13
    • EpicStory  Maps  start  with  the  iden*fica*on  of  larger,  more  strategic  organiza*onal  goalsWednesday, May 8, 13
    • EpicFeatureEpics  are  decomposed  into  Features  that  describe  the  value  added  into  the  productWednesday, May 8, 13
    • EpicFeature FeatureEpics  are  decomposed  into  Features  that  describe  the  value  added  into  the  productWednesday, May 8, 13
    • EpicFeature Feature FeatureEpics  are  decomposed  into  Features  that  describe  the  value  added  into  the  productWednesday, May 8, 13
    • EpicFeature Feature Feature FeatureEpics  are  decomposed  into  Features  that  describe  the  value  added  into  the  productWednesday, May 8, 13
    • EpicFeatureUser  StoryFeature Feature FeatureUser  StoryUser  StoryUser  StoryFeatures  are  decomposed  into  User  Stories  that  are  thin  slices  of  value  added  into  the  systemWednesday, May 8, 13
    • EpicFeatureUser  StoryFeature Feature FeatureUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryFeatures  are  decomposed  into  User  Stories  that  are  thin  slices  of  value  added  into  the  systemWednesday, May 8, 13
    • EpicFeatureUser  StoryFeature Feature FeatureUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryFeatures  are  decomposed  into  User  Stories  that  are  thin  slices  of  value  added  into  the  systemWednesday, May 8, 13
    • EpicFeatureUser  StoryFeature Feature FeatureUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryFeatures  are  decomposed  into  User  Stories  that  are  thin  slices  of  value  added  into  the  systemWednesday, May 8, 13
    • Minimally MarketableFeaturesWednesday, May 8, 13
    • EpicFeatureUser  StoryFeature Feature FeatureUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  Story3251132125321322User  Stories  are  es*mated  in  rela*ve  units  of  measure  called  Story  PointsWednesday, May 8, 13
    • EpicFeatureUser  StoryFeature Feature FeatureUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  Story325113212532132211 7 12 8Story  Points  can  be  added  up  to  size  FeaturesWednesday, May 8, 13
    • EpicFeatureUser  StoryFeature Feature FeatureUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  Story325113212532132211 7 12 838 Feature  Points  can  be  added  up  to  size  EpicsWednesday, May 8, 13
    • EpicFeatureUser  StoryFeature Feature FeatureUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  Story325113212532132211 7 12 838 Our  Goal  is  to  build  the  smallest  system  possible  to  deliver  the  value  in  the  EpicWednesday, May 8, 13
    • EpicFeatureUser  StoryFeature Feature FeatureUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  Story325113212532132211 7 12 838 We  con*nuously  evaluate  the  Story  Map  to  determine  the  Minimally  Marketable  FeatureWednesday, May 8, 13
    • User  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  Story User  StoryUser  StoryUser  StoryEpicFeature Feature Feature FeatureUser  Story User  Story User  Story11 7 12 8383251132125321322We  con*nuously  evaluate  the  Story  Map  to  determine  the  Minimally  Marketable  FeatureWednesday, May 8, 13
    • User  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  Story User  StoryUser  StoryUser  StoryEpicFeature Feature Feature FeatureUser  Story User  Story User  Story10 4 5 7263251132125321322When  we  focus  on  Minimally  Marketable  Features,  we  deliver  Business  Value  earlyWednesday, May 8, 13
    • EssentialView #1Velocity & BurndownWednesday, May 8, 13
    • SprintingWednesday, May 8, 13
    • Story  Backlog Task  Backlog In  Process Task  Done Story  DoneMinimally  Marketable  Features  feed  the  priori*za*on  of  our  Sprint  PlanningWednesday, May 8, 13
    • Story  Backlog Task  Backlog In  Process Task  Done Story  DoneIden*fy  the  User  Story  most  likely  to  contribute  to  the  MMF  and  build  that  one  firstWednesday, May 8, 13
    • Story  Backlog Task  Backlog In  Process Task  Done Story  DoneUser  Story3Iden*fy  the  User  Story  most  likely  to  contribute  to  the  MMF  and  build  that  one  firstWednesday, May 8, 13
    • Story  Backlog Task  Backlog In  Process Task  Done Story  DoneUser  Story3Pull  User  Stories  in  priority  order  focusing  on  delivering  complete  MMFsWednesday, May 8, 13
    • Story  Backlog Task  Backlog In  Process Task  Done Story  DoneUser  StoryUser  Story32Pull  User  Stories  in  priority  order  focusing  on  delivering  complete  MMFsWednesday, May 8, 13
    • Story  Backlog Task  Backlog In  Process Task  Done Story  DoneUser  StoryUser  Story32It’s  okay  to  work  User  Stories  across  MMFs  if  that  is  what  the  Product  Owner  needsWednesday, May 8, 13
    • Story  Backlog Task  Backlog In  Process Task  Done Story  DoneUser  StoryUser  StoryUser  Story321It’s  okay  to  work  User  Stories  across  MMFs  if  that  is  what  the  Product  Owner  needsWednesday, May 8, 13
    • Story  Backlog Task  Backlog In  Process Task  Done Story  DoneUser  StoryUser  StoryUser  Story321Planned  Team  Velocity  =  6  pointsThe  team  uses  its  past  velocity  to  determine  how  many  stories  go  in  the  SprintWednesday, May 8, 13
    • Story  Backlog Task  Backlog In  Process Task  Done Story  DoneUser  StoryUser  StoryUser  StoryTaskTaskTask321Planned  Team  Velocity  =  6  pointsThe  Team  breaks  each  User  Story  down  into  TasksWednesday, May 8, 13
    • Story  Backlog Task  Backlog In  Process Task  Done Story  DoneUser  StoryUser  StoryUser  StoryTaskTaskTask321Task TaskTaskTaskPlanned  Team  Velocity  =  6  pointsThe  Team  breaks  each  User  Story  down  into  TasksWednesday, May 8, 13
    • Story  Backlog Task  Backlog In  Process Task  Done Story  DoneUser  StoryUser  StoryUser  StoryTaskTaskTaskTask TaskTaskTask TaskTask Task321TaskPlanned  Team  Velocity  =  6  pointsThe  Team  breaks  each  User  Story  down  into  TasksWednesday, May 8, 13
    • Story  Backlog Task  Backlog In  Process Task  Done Story  DoneUser  StoryUser  StoryUser  StoryTaskTaskTaskTask TaskTaskTask TaskTask Task321Task8 168Planned  Team  Velocity  =  6  pointsAnd  es*mates  each  Task  in  Real  Hours  so  they  can  assess  if  they  can  make  a  solid  Commitment  to  DeliverWednesday, May 8, 13
    • Story  Backlog Task  Backlog In  Process Task  Done Story  DoneUser  StoryUser  StoryUser  StoryTaskTaskTaskTask TaskTaskTask TaskTask Task321Task8 16816 248Planned  Team  Velocity  =  6  pointsAnd  es*mates  each  Task  in  Real  Hours  so  they  can  assess  if  they  can  make  a  solid  Commitment  to  DeliverWednesday, May 8, 13
    • Story  Backlog Task  Backlog In  Process Task  Done Story  DoneUser  StoryUser  StoryUser  StoryTaskTaskTaskTask TaskTaskTask TaskTask Task321Task8 16816 2488 416 8Planned  Team  Velocity  =  6  pointsPlanned  Es*mated  Hours  =  98  hoursAnd  es*mates  each  Task  in  Real  Hours  so  they  can  assess  if  they  can  make  a  solid  Commitment  to  DeliverWednesday, May 8, 13
    • Story  Backlog Task  Backlog In  Process Task  Done Story  DoneUser  StoryUser  StoryUser  StoryTaskTask TaskTaskTask TaskTask Task321Task816 2488 416 8Planned  Team  Velocity  =  6  pointsPlanned  Es*mated  Hours  =  98  hoursTask8Task16At  the  beginning  of  the  Sprint,  The  Team  pulls  Tasks  from  the  top  of  the  Task  BacklogWednesday, May 8, 13
    • Story  Backlog Task  Backlog In  Process Task  Done Story  DoneUser  StoryUser  StoryUser  StoryTaskTask TaskTaskTask TaskTask Task321Task816 2488 416 8Planned  Team  Velocity  =  6  pointsPlanned  Es*mated  Hours  =  98  hoursTask8Task16Tasks  move  across  the  Story  Board  un*l  there  is  a  completed  User  Story.    Wednesday, May 8, 13
    • Story  Backlog Task  Backlog In  Process Task  Done Story  DoneUser  StoryUser  StoryTaskTask TaskTaskTask TaskTaskTask21Task816 2488 4168Planned  Team  Velocity  =  6  pointsPlanned  Es*mated  Hours  =  98  hoursTask8Task16User  Story3Tasks  move  across  the  Story  Board  un*l  there  is  a  completed  User  Story.    Wednesday, May 8, 13
    • Story  Backlog Task  Backlog In  Process Task  Done Story  DoneUser  StoryUser  StoryUser  StoryTaskTask TaskTaskTask TaskTaskTask321Task816 2488 4168Planned  Team  Velocity  =  6  pointsPlanned  Es*mated  Hours  =  98  hoursTask8Task16Tasks  move  across  the  Story  Board  un*l  there  is  a  completed  User  Story.    Wednesday, May 8, 13
    • Story  Backlog Task  Backlog In  Process Task  Done Story  DoneUser  StoryUser  StoryTaskTask TaskTaskTask TaskTaskTask31Task816 2488 4168Planned  Team  Velocity  =  6  pointsPlanned  Es*mated  Hours  =  98  hoursTask8Task16User  Story2The  Team  works  from  the  top  of  the  Story  Board,  Swarming  to  get    User  Stories  across  the  board  as  fast  as  possible  .    Wednesday, May 8, 13
    • Story  Backlog Task  Backlog In  Process Task  Done Story  DoneUser  StoryUser  StoryUser  StoryTaskTask TaskTaskTask TaskTaskTask321Task816 2488 4168Planned  Team  Velocity  =  6  pointsPlanned  Es*mated  Hours  =  98  hoursTask8Task16The  Team  works  from  the  top  of  the  Story  Board,  Swarming  to  get    User  Stories  across  the  board  as  fast  as  possible  .    Wednesday, May 8, 13
    • Story  Backlog Task  Backlog In  Process Task  Done Story  DoneUser  StoryUser  StoryTaskTask TaskTaskTask TaskTask Task32Task816 2488 4168Planned  Team  Velocity  =  6  pointsPlanned  Es*mated  Hours  =  98  hoursTask8Task16User  Story1The  Team  works  from  the  top  of  the  Story  Board,  Swarming  to  get    User  Stories  across  the  board  as  fast  as  possible  .    Wednesday, May 8, 13
    • Story  Backlog Task  Backlog In  Process Task  Done Story  DoneUser  StoryUser  StoryUser  StoryTaskTask TaskTaskTask TaskTask Task321Task816 2488 4168Planned  Team  Velocity  =  6  pointsPlanned  Es*mated  Hours  =  98  hoursTask8Task16Un*l  the  en*re  Sprint  has  been  delivered  to  the  Product  Owner.    Wednesday, May 8, 13
    • Measuring ProgressWednesday, May 8, 13
    • Release  Burndown38Sprint  Burndown96Velocity  Trend6From  a  Metrics  perspec*ve,  we  Burn  Down  hours  to  make  sure  the  sprint  is  on  trackWednesday, May 8, 13
    • Release  Burndown38Sprint  Burndown96Velocity  Trend6From  a  Metrics  perspec*ve,  we  Burn  Down  hours  to  make  sure  the  sprint  is  on  trackWednesday, May 8, 13
    • Release  Burndown38Sprint  Burndown96Velocity  Trend6From  a  Metrics  perspec*ve,  we  Burn  Down  hours  to  make  sure  the  sprint  is  on  trackWednesday, May 8, 13
    • Release  Burndown38Sprint  Burndown96Velocity  Trend6From  a  Metrics  perspec*ve,  we  Burn  Down  hours  to  make  sure  the  sprint  is  on  trackWednesday, May 8, 13
    • Release  Burndown38Sprint  Burndown96Velocity  Trend6From  a  Metrics  perspec*ve,  we  Burn  Down  hours  to  make  sure  the  sprint  is  on  trackWednesday, May 8, 13
    • Release  Burndown38Sprint  Burndown96Velocity  Trend6From  a  Metrics  perspec*ve,  we  Burn  Down  hours  to  make  sure  the  sprint  is  on  trackWednesday, May 8, 13
    • Release  Burndown38Sprint  Burndown96Velocity  Trend6From  a  Metrics  perspec*ve,  we  Burn  Down  hours  to  make  sure  the  sprint  is  on  trackWednesday, May 8, 13
    • Release  Burndown38Sprint  Burndown96Velocity  Trend6From  a  Metrics  perspec*ve,  we  Burn  Down  hours  to  make  sure  the  sprint  is  on  trackWednesday, May 8, 13
    • Release  Burndown38Sprint  Burndown96Velocity  Trend6From  a  Metrics  perspec*ve,  we  Burn  Down  hours  to  make  sure  the  sprint  is  on  trackWednesday, May 8, 13
    • Release  Burndown38Sprint  Burndown96Velocity  Trend66From  a  Metrics  perspec*ve,  we  Burn  Down  points  to  make  sure  the  Release  is  on  trackWednesday, May 8, 13
    • Release  Burndown38Sprint  Burndown96Velocity  Trend668From  a  Metrics  perspec*ve,  we  Burn  Down  points  to  make  sure  the  Release  is  on  trackWednesday, May 8, 13
    • Release  Burndown38Sprint  Burndown96Velocity  Trend6685We  track  Velocity  Trend  to  make  sure  the  team  is  delivering  in  a  Predictable  mannerWednesday, May 8, 13
    • Release  Burndown38Sprint  Burndown96Velocity  Trend6685When  the  Release  is  ready  to  deliver,  The  Team  has  completed  the  highest  priority  User  Stories,  against  the  highest  priority  Features  ,against  the  highest  priority  Epics.    Wednesday, May 8, 13
    • Release  Burndown38Sprint  Burndown96Velocity  Trend6685When  the  Release  is  ready  to  deliver,  The  Team  has  completed  the  highest  priority  User  Stories,  against  the  highest  priority  Features  ,against  the  highest  priority  Epics.    Everyone  is  focused  on  delivering  value  early  and  oen!Wednesday, May 8, 13
    • EssentialView #2Roadmap Over TimeWednesday, May 8, 13
    • Road-mappingWednesday, May 8, 13
    • EpicQ1 Q2 Q3 Q4Wednesday, May 8, 13
    • Epic EpicQ1 Q2 Q3 Q4Wednesday, May 8, 13
    • Epic Epic EpicQ1 Q2 Q3 Q4Wednesday, May 8, 13
    • Epic Epic Epic EpicQ1 Q2 Q3 Q4Wednesday, May 8, 13
    • Epic Epic Epic Epic EpicQ1 Q2 Q3 Q4Wednesday, May 8, 13
    • Epic Epic Epic Epic Epic EpicQ1 Q2 Q3 Q4Wednesday, May 8, 13
    • Epic Epic Epic Epic Epic Epic EpicQ1 Q2 Q3 Q4Wednesday, May 8, 13
    • Epic Epic Epic Epic Epic Epic Epic EpicQ1 Q2 Q3 Q4Wednesday, May 8, 13
    • Epic Epic Epic Epic Epic Epic Epic EpicQ1 Q2 Q3 Q4Arch Arch Arch Arch Arch Arch Arch ArchWednesday, May 8, 13
    • Arch Arch Arch Arch Arch Arch Arch ArchEpic Epic Epic Epic Epic Epic Epic EpicQ1 Q2 Q3 Q4Wednesday, May 8, 13
    • Progressive ElaborationWednesday, May 8, 13
    • Arch Arch Arch Arch Arch Arch Arch ArchEpicFeatureEpicFeatureEpic Epic Epic Epic Epic EpicQ1 Q2 Q3 Q4Wednesday, May 8, 13
    • Arch Arch Arch Arch Arch Arch Arch ArchEpicFeatureEpicFeatureEpicFeatureEpicFeatureEpic Epic Epic EpicQ1 Q2 Q3 Q4Wednesday, May 8, 13
    • Arch Arch Arch Arch Arch Arch Arch ArchEpicFeatureEpicFeatureEpicFeatureEpicFeatureEpic Epic Epic EpicQ1 Q2 Q3 Q4Feature FeatureWednesday, May 8, 13
    • Arch Arch Arch Arch Arch Arch Arch ArchEpicFeatureEpicFeatureEpicFeatureEpicFeatureEpic Epic Epic EpicQ1 Q2 Q3 Q4Feature Feature FeatureWednesday, May 8, 13
    • Arch Arch Arch Arch Arch Arch Arch ArchEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryUser  StoryEpicFeatureEpicFeatureEpicFeatureEpicFeatureEpic EpicQ1 Q2 Q3 Q4FeatureWednesday, May 8, 13
    • Arch Arch Arch Arch Arch Arch Arch ArchEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryEpicFeatureEpicFeatureEpic EpicQ1 Q2 Q3 Q4FeatureWednesday, May 8, 13
    • Managing RiskWednesday, May 8, 13
    • Arch Arch Arch Arch Arch Arch Arch ArchEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryEpicFeatureEpicFeatureEpic EpicQ1 Q2 Q3 Q4FeatureRisk RiskWednesday, May 8, 13
    • Arch Arch Arch Arch Arch Arch Arch ArchEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryEpicFeatureEpicFeatureEpic EpicQ1 Q2 Q3 Q4FeatureRisk RiskUser  Story User  StoryWednesday, May 8, 13
    • Arch Arch Arch Arch Arch Arch Arch ArchEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryEpicFeatureUser  StoryEpicFeatureUser  StoryEpic EpicRisk Risk Risk RiskQ1 Q2 Q3 Q4FeatureWednesday, May 8, 13
    • Q1 Q2 Q3 Q4Arch Arch Arch Arch Arch Arch Arch ArchEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryEpicFeatureUser  StoryEpicFeatureEpic EpicRisk Risk Risk RiskFeatureUser  StoryUser  StoryWednesday, May 8, 13
    • Q1 Q2 Q3 Q4Arch Arch Arch Arch Arch Arch Arch ArchEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryEpicFeatureUser  StoryEpicFeatureEpic EpicRisk Risk Risk RiskFeatureUser  StoryRiskUser  StoryWednesday, May 8, 13
    • Release SpikesWednesday, May 8, 13
    • Q1 Q2 Q3 Q4Arch Arch Arch Arch Arch Arch Arch ArchEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryEpicFeatureUser  StoryEpicFeatureEpic EpicRisk Risk Risk RiskFeatureUser  StoryRiskSpike SpikeUser  StoryWednesday, May 8, 13
    • Q1 Q2 Q3 Q4Arch Arch Arch Arch Arch Arch Arch ArchEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryEpicFeatureUser  StoryEpicFeatureEpic EpicRisk Risk Risk RiskFeatureUser  StoryRiskSpike SpikeSpikeUser  StoryWednesday, May 8, 13
    • Budgeting vs. EstimatingWednesday, May 8, 13
    • Q1 Q2 Q3 Q4Arch Arch Arch Arch Arch Arch Arch ArchEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryEpicFeatureUser  StoryEpicFeatureEpic EpicRisk Risk Risk RiskFeatureUser  StoryRiskSpike SpikeSpikeUser  StoryWednesday, May 8, 13
    • EssentialView #3FlowWednesday, May 8, 13
    • Key Concepts• Flow• Value Streams• Small Batches• WIP LimitsWednesday, May 8, 13
    • Key Concepts• Flow• Value Streams• Small Batches• WIP LimitsWednesday, May 8, 13
    • Key Concepts• Flow• Value Streams• Small Batches• WIP LimitsWednesday, May 8, 13
    • Key Concepts• Flow• Value Streams• Small Batches• WIP LimitsWednesday, May 8, 13
    • Key Concepts• Flow• Value Streams• Small Batches• WIP LimitsWednesday, May 8, 13
    • n-Tier ModelWednesday, May 8, 13
    • ScrumTeamProductTeamScrumTeamScrumTeamScrumTeamProductTeamStrategyTeamSupportTeamPortfolioTeamn-Tier ModelWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story DoneTier 1 - ScrumWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story DoneAnalysis Design Build Test DeployTier 1 - ScrumTier 2 - KanbanWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story DoneAnalysis Design Build Test DeployInception Elaboration Construction TransitionTier 1 - ScrumTier 2 - KanbanTier 3 - KanbanWednesday, May 8, 13
    • EpicFeatureUser  StoryFeature Feature FeatureUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryUser  StoryWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story DoneAnalysis Design Build Test DeployInception Elaboration Construction TransitionTier 1 - ScrumTier 2 - KanbanTier 3 - KanbanUser StoryWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story DoneAnalysis Design Build Test DeployInception Elaboration Construction TransitionTier 1 - ScrumTier 2 - KanbanTier 3 - KanbanFeatureUser StoryWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story DoneAnalysis Design Build Test DeployInception Elaboration Construction TransitionTier 1 - ScrumTier 2 - KanbanTier 3 - KanbanEpicFeatureUser StoryWednesday, May 8, 13
    • Kanban creates a Pull Systemacross the entire portfolio that islimited by your Actual CapacityWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicEpicWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicEpicWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicEpicWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicEpicFeatureFeatureWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicEpicFeatureFeatureWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicEpicFeatureFeatureWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicEpicFeatureSpikeFeatureWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicEpicFeatureUser StoryUser StorySpikeFeatureWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicEpicFeatureUser StoryUser StorySpikeFeatureWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicEpicFeatureUser StoryUser StorySpikeTaskTaskTask8 168FeatureWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionFeatureUser StoryUser StorySpikeTaskTaskTask8 168FeatureEpicEpicWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeatureUser StoryUser StorySpikeTaskTaskTask8 168FeatureEpicWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeatureUser StoryUser StorySpikeTaskTaskTask8 168FeatureEpicEpicWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeatureUser StoryUser StorySpikeTaskTaskTask8 168FeatureEpicEpicFeatureWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeatureUser StoryUser StorySpikeTaskTaskTask8168FeatureEpicEpicFeatureWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeatureUser StoryUser StorySpikeTaskTaskTask8168FeatureEpicEpicFeatureWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeatureUser StoryUser StoryTaskTaskTask8168EpicSpikeFeatureFeatureWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeatureUser StoryUser StorySpikeTaskTaskTask8168EpicFeatureFeatureWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeatureUser StoryUser StoryTaskTaskTask8168SpikeEpicFeatureFeatureWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeatureTaskTaskTask8168 User StorySpike User StoryEpicFeatureFeatureWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeatureTaskTaskTask8168 User StorySpike User StoryEpicFeatureFeatureWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeatureFeatureTaskTaskTask8168 User StorySpike User StoryEpicFeatureWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeatureFeatureTaskTaskTask8168 User StorySpike User StoryEpicFeatureWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeatureFeatureTaskTaskTask8168 User StorySpike User StoryEpicFeatureFeatureWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeature FeatureTaskTaskTask8168User StoryUser StorySpikeEpicEpicFeature FeatureWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeature FeatureTaskTaskTask8168User StoryUser StorySpikeEpicEpicFeatureFeatureWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeature FeatureTaskTaskTask8168User StoryUser StorySpikeEpicEpicFeatureFeatureWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeature FeatureTaskTaskTask8168User StoryUser StorySpikeEpicEpicFeatureFeatureWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeature FeatureTaskTaskTask8168User StoryUser StorySpikeEpicEpicFeatureFeatureWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeature FeatureTaskTaskTask8168User StoryUser StorySpikeEpicEpicFeatureFeatureWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicEpicFeatureFeatureTaskTaskTask8168User StorySpikeUser StoryEpicFeatureFeatureFeatureUser StoryUser StorySpikeTaskTaskTask88Wednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicEpicFeatureFeatureTaskTaskTask8168User StorySpikeUser StoryEpicFeatureUser StoryUser StorySpikeFeatureFeatureWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeatureFeatureEpic EpicUser StoryUser StorySpikeTaskTaskTask88FeatureFeatureFeature8Wednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeatureFeatureEpic EpicUser StoryUser StorySpikeTaskTask88FeatureFeatureFeatureTask8Wednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeatureFeatureEpic EpicUser StoryUser StorySpikeTaskTask88FeatureFeatureFeatureTask8Wednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeatureFeatureEpic EpicUser StoryTaskTask88FeatureFeatureFeatureTask8User StorySpikeWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeatureFeatureEpic EpicUser StoryTaskTask88FeatureFeatureFeatureTask8User StorySpikeWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeatureFeatureEpic EpicUser StoryTaskTask88FeatureFeatureFeatureTask8User StorySpikeWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeatureFeatureEpic EpicUser StoryTaskTask88FeatureFeatureFeatureTask8User StorySpikeWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeatureFeatureEpicEpicUser StoryTaskTask88FeatureFeatureFeatureTask8User StorySpikeWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeatureFeatureEpic EpicUser StoryTaskTask88FeatureFeatureFeatureTask8User StorySpikeEpicFeatureUser Story User StorySpikeTaskTaskTask88Task8Task8Wednesday, May 8, 13
    • Bottlenecks &DependenciesWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story BacklogAnalysis Design Build Test DeployInception Elaboration Construction TransitionEpicFeatureFeatureEpic EpicUser StoryTaskTask88FeatureFeatureFeatureTask8User StorySpikeEpicFeatureUser Story User StorySpikeTaskTaskTask88Task8Task8Wednesday, May 8, 13
    • EssentialView #4ProgressWednesday, May 8, 13
    • Assessing ProgressHow do we visualize progress to the rest of theorganization• Start• End• Budget• SWAG• Estimate• Actual• % CompleteWednesday, May 8, 13
    • Planned PlannedProgress Budget Estimate Detail Start EndWednesday, May 8, 13
    • EpicPlanned PlannedProgress Budget Estimate Detail Start End300 280 325 Sprint 1 Sprint 5Wednesday, May 8, 13
    • EpicFeaturePlanned PlannedProgress Budget Estimate Detail Start End300162801932521Sprint 1Sprint 2Sprint 5Sprint 4Wednesday, May 8, 13
    • EpicFeaturePlanned PlannedProgress Budget Estimate Detail Start EndUser  Story300165280198325218Sprint 1Sprint 2Sprint 2Sprint 5Sprint 4Sprint 2Wednesday, May 8, 13
    • EpicFeaturePlanned PlannedProgress Budget Estimate Detail Start EndUser  StoryUser  Story300165328019833252185Sprint 1Sprint 2Sprint 2Sprint 3Sprint 5Sprint 4Sprint 2Sprint 3Wednesday, May 8, 13
    • EpicFeaturePlanned PlannedProgress Budget Estimate Detail Start EndUser  StoryUser  StoryUser  Story300165382801988332521858Sprint 1Sprint 2Sprint 2Sprint 3Sprint 4Sprint 5Sprint 4Sprint 2Sprint 3Sprint 4Wednesday, May 8, 13
    • EpicFeaturePlanned PlannedProgress Budget Estimate Detail Start EndUser  StoryUser  StoryUser  Story300165382801988332521858Sprint 1Sprint 2Sprint 2Sprint 3Sprint 4Sprint 5Sprint 4Sprint 2Sprint 3Sprint 4Wednesday, May 8, 13
    • EpicFeaturePlanned PlannedProgress Budget Estimate Detail Start EndUser  StoryUser  StoryUser  Story300165382801988332521858Sprint 1Sprint 2Sprint 2Sprint 3Sprint 4Sprint 5Sprint 4Sprint 2Sprint 3Sprint 4Wednesday, May 8, 13
    • EpicFeaturePlanned PlannedProgress Budget Estimate Detail Start EndUser  StoryUser  StoryUser  Story300165382801988332521858Sprint 1Sprint 2Sprint 2Sprint 3Sprint 4Sprint 5Sprint 4Sprint 2Sprint 3Sprint 4Wednesday, May 8, 13
    • EpicFeaturePlanned PlannedProgress Budget Estimate Detail Start EndUser  StoryUser  StoryUser  Story300165382801988332521858Sprint 1Sprint 2Sprint 2Sprint 3Sprint 4Sprint 5Sprint 4Sprint 2Sprint 3Sprint 4Wednesday, May 8, 13
    • EpicFeaturePlanned PlannedProgress Budget Estimate Detail Start EndUser  StoryUser  StoryUser  Story300165382801988332521858Sprint 1Sprint 2Sprint 2Sprint 3Sprint 4Sprint 5Sprint 4Sprint 2Sprint 3Sprint 4Wednesday, May 8, 13
    • Pulling it all togetherWednesday, May 8, 13
    • Release  Burndown38Sprint  Burndown96Velocity  Trend6685Wednesday, May 8, 13
    • Q1 Q2 Q3 Q4Arch Arch Arch Arch Arch Arch Arch ArchEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryUser  StoryEpicFeatureUser  StoryEpicFeatureUser  StoryEpicFeatureEpic EpicRisk Risk Risk RiskFeatureUser  StoryRiskSpike SpikeSpikeUser  StoryWednesday, May 8, 13
    • Story Backlog Task Backlog In Process Task Done Story DoneAnalysis Design Build Test DeployInception Elaboration Construction TransitionTier 1 - ScrumTier 2 - KanbanTier 3 - KanbanEpicFeatureUser StoryWednesday, May 8, 13
    • EpicFeaturePlanned PlannedProgress Budget Estimate Detail Start EndUser  StoryUser  StoryUser  Story300165382801988332521858Sprint 1Sprint 2Sprint 2Sprint 3Sprint 4Sprint 5Sprint 4Sprint 2Sprint 3Sprint 4Wednesday, May 8, 13
    • Done  Develop    and  Test  Ready  To  Build  Detailed  Planning  Release  Targe6ng  Feasibility  Study  Market  Research  New  Concept  Development FlowFeature  Complete  Integra6on  Tes6ng  Develop  and  Test  Story  Review  Story    Mapping  Feature  Breakdown  Story    Done  Task  Done  Task  In  Process  Task  Ready  Story  Backlog  KANBAN  FEATURE  STORY  EPICS  KANBAN  SCRUM  
    • The Epic Tier•  Idea  list  genera<on  from  mul<ple  data  feeds  and  sources  •  Market  Research  •  Customer  Research  •  Field  Feedback  •  Business  Case  &  ROI  •  Compe<<ve  Analysis  •  High  Level  Es<ma<on  •  Solu<on  Cost  •  High  Level  Architecture    •  Risk  Analysis  •  Feasibility  •  Detailed  Architecture  •  Feature  Mapping  •  Acceptance  Criteria  •  Es<ma<on  •  Backlog  •  All  features  are  done  •  Regression  tests  are  completed    •  Release  Criteria  are  met  •  Forced  Priority  •  Certainty    Curve  Done  Develop    and  Test  Ready  To  Build  Detailed  Planning  Release  Targe6ng  Feasibility  Study  Market  Research  New  Concept  
    • Epic Tier OwnershipR  A  C  I    Product  Management  Product  Management  Customer  Advocate  PorLolio  Team    R  A  C  I    Product  Owner  Team  Product  Owner  Team  Engineering  PorLolio  Team    R  A  C  I    Product  Owner  Team  Product  Owner  Team  Engineering  PorLolio  Team    R  A  C  I    Engineering  Product  Owner  Team  Customer  Advocate  PorLolio  Team    PorLolio  Team  R  A  C  I    Product  Management  Product  Management  Customer  Advocate  Product  Owner  Team  R  A  C  I    Product  Management  Product  Management  Customer  Advocate  Product  Owner  Team  •  Responsible  -­‐  Those  who  do  the  work  to  achieve  the  task.  •  Accountable  -­‐  The  one  ul<mately  answerable  for  the  correct  and  thorough  comple<on  of  the  deliverable.  •  Consulted  -­‐  Those  whose  opinions  are  sought,  typically  subject  maRer  experts;  and  with  whom  there  is  two-­‐way  communica<on.  •  Informed  -­‐  Those  who  are  kept  up-­‐to-­‐date  on  progress,  oUen  only  on  comple<on  of  the  task  or  deliverable.  GATE  RESPONSIBLITY  Done  Develop    and  Test  Ready  To  Build  Detailed  Planning  Release  Targe6ng  Feasibility  Study  Market  Research  New  Concept  
    • The Feature Tier•  Feature  List  for  the  Parent  Epic  •  Story  Wri<ng  •  MMF  •  Es<ma<ng  •  High  Level  Design  •  UX  Mockups  •  Es<mate  Sanity  Check  •  Spike  Iden<fica<on  •  Review  for  Feasibility  •  Review  of  Acceptance  Criteria  •  Story  Spanning  •  Story  Tasking  •  Feature  Tes<ng  Non-­‐Func<onal  •  Valida<on  of  Automated  Tests  •  Detailed  Design  •  Code  •  Unit  Test  •  Code  Review  •  Func<onal  Test  •  User  Story    •  Product  Owner  Acceptance  Feature  Complete  Integra6on  Tes6ng  Develop  and  Test  Story  Review  Story    Mapping  Feature  Breakdown  •  All  Stories  are  done  •  Feature  Level  tes<ng  is  completed  •  Defect  criteria  are  met  •  Feature  Check  list    from  RDS  template  •  Performance  and  Sizing  Complete  * Stand alone features must have these acceptance criteria (x, x, x)
    • Feature Tier Ownership•  Responsible  -­‐  Those  who  do  the  work  to  achieve  the  task.  •  Accountable  -­‐  The  one  ul<mately  answerable  for  the  correct  and  thorough  comple<on  of  the  deliverable.  •  Consulted  -­‐  Those  whose  opinions  are  sought,  typically  subject  maRer  experts;  and  with  whom  there  is  two-­‐way  communica<on.  •  Informed  -­‐  Those  who  are  kept  up-­‐to-­‐date  on  progress,  oUen  only  on  comple<on  of  the  task  or  deliverable.  R  A  C  I    Product  Owner  Team  Product  Owner  Team  Customer  Advocate  Engineering  R  A  C  I    Engineering    Product  Owner  Team  Product  Owner  Team  Product  Owner  Team    R  A  C  I    Engineering    Engineering    Product  Owner  Team  Product  Owner  Team  R  A  C  I    Engineering  Engineering    Product  Owner  Team  Product  Owner  Team    R  A  C  I    Product  Owner  Team  Product  Owner  Team  Engineering  Engineering  R  A  C  I    Product  Owner  Team  Product  Owner  Team  Engineering  PorLolio  Product  Owner  Team  GATE  RESPONSIBLITY  Engineering  Team  GATE  RESPONSIBLITY  Engineering  Team  GATE  RESPONSIBLITY  Product  Owner  Team  GATE  RESPONSIBLITY  Feature  Complete  Integra6on  Tes6ng  Develop  and  Test  Story  Review  Story    Mapping  Feature  Breakdown  
    • The Story TierStory    Done  Task  Done  Task  In  Process  Task  Ready  Story  Backlog  •  Story  List  for  the  Parent  Feature  •  Approved  task  of  8  hours  or  less  •  SCRUM  team  completes  the  task  •  Task  is  done  and  communicated  in  the  standup      Documented  • The  User  Story    • Acceptance  Criteria  • Conversa<ons    • Level  of  Value  • Level  of  Effort  • Design  Assump<ons  • Design  Documented  (op<onal)    • UI  Documented  (op<onal)          Coded  • Checked  Into  integrated  build  • Simple  Design    • Documented  with  Comments  • Automated  Tests  for  New  Features      Tested  • Tes<ng  is  complete    • Defect  Criteria  Met    • Automated  Tes<ng  Passed    Approved  • Feature  Complete  (Scrum  Master)  • Test  Complete  (QA  Lead)  • Accepted  (Product  Owner)    * Stand alone stories must have these acceptance criteria (x, x, x)
    • Story Tier Ownership•  Responsible  -­‐  Those  who  do  the  work  to  achieve  the  task.  •  Accountable  -­‐  The  one  ul<mately  answerable  for  the  correct  and  thorough  comple<on  of  the  deliverable.  •  Consulted  -­‐  Those  whose  opinions  are  sought,  typically  subject  maRer  experts;  and  with  whom  there  is  two-­‐way  communica<on.  •  Informed  -­‐  Those  who  are  kept  up-­‐to-­‐date  on  progress,  oUen  only  on  comple<on  of  the  task  or  deliverable.  R  A  C  I    Product  Owner  Product  Owner  Customer  Advocate  Engineering  R  A  C  I    Engineering  Engineering  Engineering  Engineering  R  A  C  I    Engineering    Engineering    Engineering  Engineering  R  A  C  I    Engineering  Product  Owner  Engineering    Engineering  R  A  C  I    Engineering  Engineering  Engineering  Engineering  Story    Done  Task  Done  Task  In  Process  Task  Ready  Story  Backlog