Hi all,
trying to get my project ready for monthly reporting i m again annoyed about my actual workflow!
In our company we have to estimate the overall efforts in front of a project, based on a 80% backlog of user stories or other known requirements. As these projects are normally quite big (> 1000 MDs) we split them up in several epics which are more or less technical driven (GUI, logical layer, database etc.) as we feel better to evaluate this instead of approx. 100 user stories. For sure we estimate the user stories also in story points, but the team is often mixed up (external support e.g.) and therefor the velocity is no valid estimation (but used to double check when the velocity is settled).
Finally, there is an estimated effort on a high level and this effort has to be tracked during the project and also be visible in the JIRA charts (remaining estimates burndown; the green line), this has to be done in the early beginning of a project!
Right now we re estimating our sprint effort before each sprint very detailed, afterwards the project lead takes this values, does a summary on epic level and substracts it from the actual remaining effort of the according "budget epic".
Is there a way to do this in a way the system can support? All this stuff is done manually, what i m looking for is perhaps a workflow where the effort will be substracted from a parent by adding a subtask.
What do you think, how do you handle this?
Best regards,
Hans-Hermann
