Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
how_do_we_use_story_point_estimates_to_forecast [2019/01/21 09:14]
hpsamios [How Do We Scale Forecasting?]
how_do_we_use_story_point_estimates_to_forecast [2019/01/21 09:22] (current)
hpsamios Fixed to clarify
Line 48: Line 48:
 Similar thinking can be applied to Epics at the Portfolio level. Similar thinking can be applied to Epics at the Portfolio level.
  
-===== How Do We Deal with Carry-Over Features =====+===== How Do We Deal with Carry-Over Features=====
  
-If we are in the first quarterly increment (SAFe'​s Program Increment or PI) 1 and we find that we have not completed work on a Feature, what should we do with that Feature as we head into PI 2. In general, what we would like to do is determine whether it is better to work on new PI 2 features, or finish off the remaining amount of work on the Feature from PI 1. To do this "​correctly" ​this means that for the purposes of scheduling the carry-over Features, we need the “job size” to reflect remaining work when doing the WSJF calculation. This will have the natural effect of moving unfinished work higher because you'd expect it to be smaller. If we only have a couple of hours left on something and we get “all this value” then we should do this first.+If we are in the first quarterly increment (SAFe'​s Program Increment or PI) 1 and we find that we have not completed work on a Feature, what should we do with that Feature as we head into PI 2. In general, what we would like to do is determine whether it is better to work on new PI 2 Features, or finish off the remaining amount of work on the Feature from PI 1. To do this "​correctly" ​need to determine whether it it better to invest our capacity in the remaining work on the Feature or to stop and work on new Features. This meansfor the purposes of scheduling the carry-over Features, we need the “job size” to reflect remaining work when doing the WSJF calculation. This will have the natural effect of moving unfinished work higher because you'd expect it to be smaller. If we only have a couple of hours left on something and we get “all this value” then we should do this first.
  
-<WRAP Box>Question we are trying to answer is “what is the best use of our people’s time?</​WRAP>​+This thinking is really an example of: 
 +<WRAP Box> “what is the best use of our people’s time?"</​WRAP>​
  
-In reality ​this can be a lot of work and the end result is often "we need to finish the Features we have started." ​So most organizations end up saying that “we will treat Feature carry over work differently”. ​Lets say we have some uncompleted Features in the current PI, PI 1. Rather than re-estimating the feature ​for work that is carried over, we will simple treat carry-over work as “top priority” and assume that it will be scheduled first. These become the top items on the list for PI 2. Then the only thing we do a WSJF on is “new” PI 2 stuff that is coming out of the Program Backlog. ​+In reality ​re-estimating the Features ​can be a lot of work and the end result is often "we need to finish the Features we have started." ​Most organizations end up saying that “we will treat Feature carry over work differently”. ​Let'​s ​say we have some uncompleted Features in the current PI, PI 1. Rather than re-estimating the Feature ​for work that is carried over, we will simple treat carry-over work as “top priority” and assume that it will be scheduled first. These become the top items on the list for PI 2. Then the only thing we do a WSJF on is “new” PI 2 stuff that is coming out of the Program Backlog. ​
  
 If you do this process, you would want to do a quick review of the carry over work asking “have we learned something that would say we shouldn’t just finish the work of this feature in the PI?” You are looking for things that still have a lot work to complete. For example: If you do this process, you would want to do a quick review of the carry over work asking “have we learned something that would say we shouldn’t just finish the work of this feature in the PI?” You are looking for things that still have a lot work to complete. For example:
Line 67: Line 68:
 ===== How Do We Show Progress of Work for a Feature or Epic? ===== ===== How Do We Show Progress of Work for a Feature or Epic? =====
  
-Requirements typically are represented in an organization as a hierarchy: ​epics breaking down into a number of featuresfeatures ​into a number of stories:+Requirements typically are represented in an organization as a hierarchy: ​Epics breaking down into a number of FeaturesFeatures ​into a number of Stories:
  
 {{ agile_requirements_breakdown.jpg?​500 |}} {{ agile_requirements_breakdown.jpg?​500 |}}
  • /home/hpsamios/hanssamios.com/dokuwiki/data/pages/how_do_we_use_story_point_estimates_to_forecast.txt
  • Last modified: 2019/01/21 09:22
  • by hpsamios