My Per Developer Timelines stretch across a wide range of dates. How can I steepen this slope?

|
0
|
|
|
|
|
5
|
There's an elephant in the room. It's very likely that you have one or more cases with a large estimate (over 40 hours). When we predict your ship dates, we run a bunch of simulations. An elephantine estimate injects a huge amount of variability into this process, because one thing matters more than everything else:
Here's a simplified example: Let's say you have two cases with estimates:
Let's say you have these two estimates in your history:
These two estimates translate into two velocities:
When we apply the first velocity to a case in EBS, we expect the case to take half as long as its estimate. When we pick the second, we expect it to take twice as long. Simulation 1
Simulation 2
So it's either going to take half a week or two full weeks. Now, let's break up that big case into five smaller cases, each representing a day of work.
Same number of total estimated hours. Different breakdown. Simulation 1
Simulation 2
This is a very simplified example, but as you can see, the spread between the high and low estimates is greatly reduced by breaking up cases into smaller increments. |
|||
|
|