Please enable JavaScript.

Coggle requires JavaScript to display documents.

Scrum Planning (Guide to economical sensible envisioning (Target…

- - - - We know precisely how many sprints we will have◄
        Specialized burn-up chart
        Burn-up chart with inverted PB◄
        Highest priorities at the bottom and lowest at the top◄
        Eliminate the problem of having to know the scope of the PBI in the release◄
    - - Input
        Product vision◄
        Product backlog◄
        Product road map◄
        Velocity◄
      - Output
        Release plan◄
      - Timing
        This is also not a one-time event◄
        3(or fewer) to 9 months◄
      - Participant
        Product Owner◄
        Internal Stakeholders◄
        Specialists in variety of areas(market research, business case development, UX design, and system architect)◄
      - Activities
        Product backlog grooming (Creating, estimating and prioritizing backlog items)◄
        Confirm the release constraints of scope, date and budget◄
        Release Constraints
        Scope◄
        Date◄
        Budget◄
        Sprint Mapping (PBI Slotting)
        Mapping PBI to sprints is known as sprint mapping or slotting◄
    - - Burn-down chart
        
        This is for fixed-scope release shows the total amount of unfinished work in the sprint◄
        At the end of the each sprint, the chart must be updated to see the remaining work amount◄
        Used to show sprint velocity◄
        Can shows projected outcomes◄
      - Burn-up chart
        
        Shows the total amount of Finished work as a goal and progress of each sprints towards ◄
        achieving that goal
        This chart shows the same three predictive lines indicating the likely number of sprints to◄
        achieve the target
      - Intro
        During this we need to calculate number of sprints required to deliver the fixed set of features◄
        Calculating Cost
        Identify team◄
        Determine the sprint length◄
        Based on team composition and sprint length decide personal cost of running sprints◄
        Multiply both the high and low number of sprints by the cost per sprint◄
        Communicating Progress
        The goal is how we are progressing toward completing that work for that we use burn up-down charts◄
  - - - Participant
        ►Product owner
        ►Internal Stakeholders
        ►Specialist in variety of areas(market research, business case development, UX design, system architect )
      - Timing
        ►Envisioning is not one-time event
        ► Up to many month or larger
      - Output
        ►High level features high level product backlog (Inputs to portfolio planning)
        ► Product vision (is product for what?)
        ►Road map
      - Input
        ► Initial data or pivoted data
        ►Planning horizon
        ►Completion date
        ►Budget, resource
        ►Confidence threshold
      - Activities
        
        ►Generate product vision
        ►Generate initial product backlog and read map