| Project | Pert Calculator | Status |
| ||||||||||
| Release Planned Date |
| ||||||||||||
| Release Actual Date |
|
Summary
- We have added a much needed feature that allows PERT estimations to be registered for Scrum stories and be reflected on burn down charts. Now when you estimate a sub-task, it will add the estimates of all subtasks and assign that total as the original estimate of the story.
- The PERT calculator popup now displays the issue key and summary for easier trasability
- We have added a text area where an explanation can be given about the estimation entered
- Minor bug fixes such as time denomination was not marked when decimals were used.
Release details
| Type | Issue | Summary | Description | ||||
|---|---|---|---|---|---|---|---|
| 1 | Feature | PC-17 | Rollup total to parent task | Add a configuration option that will allow the user to enable or disable it. When enabled, if a user estimates a subtask using PERT, the total estimations of all the subtasks will be assigned to the story. This allows for the correct estimation of the story so that it can be used in the Scrum burndown chart. | 2 | 3 | 4 |
Story
| |||
| Feature | PC-20 | Add issue key and summary at the top of the popup | The PERT calculator popup will now include more information about the issue being estimated so that the user does not have to close the popup |
to see which issue he/she is estimating. This extra information includes the issue key and issue summary.
| |
| Feature | PC-22 |
| Add a comment box on the PERT calculator | As a PERT calculator user, I would like to be able to write a justification for the estimation provided, so that other people can better understand why the best, probable and worst case scenario estimations were provided. Display a comment icon on the PERT calculator panel to indicate that there is a comment on this estimation.
| |
| Bug |
| PC-21 |
| No denomination added when decimals are used | When I enter an estimation such as 0.5, the PERT calculator does not convert it to 30m, and just displays 0.5. It should always have the proper format.
|
