How much is the backlog of your product (product backlog)?
Usually , the product backlog (or its part) is estimated by the sum of the planned laboriousness of the wishes (user story) included in it. This figure is interesting because with its help it is possible to estimate the period through which these wishes will be realized by the team.
1. Classics of the genre here : the sum of the laboriousness / (team size * working hours per day) * focus factor = gives a very inaccurate prediction, because it does not take into account historical data.
2. To increase the accuracy , we take the average development speed of the team (velocity) in this release or iteration, take into account the error of underestimating wishes and the average time spent on correcting errors - and counting with these parameters = we get a much more accurate result, say 5 days for some set of wishes.
')
However, often the business order (with the resource model) and the team bosses (fixed-price model) are interested in evaluating the implementation of a set of wishes in the units to which they are accustomed - in money.
3. We set the cost of the participant’s work , we take into account the load of all team members, including the project manager, and now - 5 days of work of the whole team at the specified scope of work will cost about 120 thousand rubles.
The predicted calculation taking into account statistical information (point 2) in the project management system DEVPROM was already a long time ago, and now the cost of the entire backlog or any part of it is calculated :
Do you think this functionality would be useful for you in your project management system?
PS DEVPROM appeared on Twitter, join!
1. Classics of the genre here : the sum of the laboriousness / (team size * working hours per day) * focus factor = gives a very inaccurate prediction, because it does not take into account historical data.
2. To increase the accuracy , we take the average development speed of the team (velocity) in this release or iteration, take into account the error of underestimating wishes and the average time spent on correcting errors - and counting with these parameters = we get a much more accurate result, say 5 days for some set of wishes.
')
However, often the business order (with the resource model) and the team bosses (fixed-price model) are interested in evaluating the implementation of a set of wishes in the units to which they are accustomed - in money.
3. We set the cost of the participant’s work , we take into account the load of all team members, including the project manager, and now - 5 days of work of the whole team at the specified scope of work will cost about 120 thousand rubles.
The predicted calculation taking into account statistical information (point 2) in the project management system DEVPROM was already a long time ago, and now the cost of the entire backlog or any part of it is calculated :
- Go to the project budgeting settings, set the Use budgeting checkbox. Choose the desired currency and payment model (hourly, monthly). If it is necessary to hide from the team and the customer who gets what, how much, we set the Hide cost of the participant’s work.
- In the profile of each project participant we set the cost of his work for one hour or one month, depending on the chosen payment model.
- We put the preliminary estimates of the complexity of the wishes, choose the necessary skoup (release wish log, or a set of wishes, united by some tag) and get the necessary statistics:
Do you think this functionality would be useful for you in your project management system?
PS DEVPROM appeared on Twitter, join!
Source: https://habr.com/ru/post/64477/
All Articles