Timeline for Estimating Tasks which have been split from a User Story
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 7, 2021 at 17:41 | comment | added | reneton | If you use Tasks instead of Sub-Taska and you only esrimate the User Story, you will have unestimated items in the backlog and then the Jira reports are not accurate. | |
| Jun 7, 2021 at 9:42 | comment | added | reneton | So you don't use Sub-Tasks to break down the Story into "work tasks"? | |
| Jun 7, 2021 at 9:23 | comment | added | nvogel | OK. Glad I could help. Personally I use Jira Stories as stories and Jira Tasks as tasks but thanks for the clarification. | |
| Jun 7, 2021 at 9:14 | comment | added | reneton | Thank you @nvogel. I was referring with Stories and Tasks to Jira, so it was a little bit confusing. A Jira Task is at the same level as a Story. Therefore, if a Story is break down into "work tasks" it's better to use Jira Sub-Tasks and not Jira Tasks. Of course, when a Story is to big for a sprint, the Story is split into smaller Stories. After that the developers break down the story into "work tasks" (so called Sub-Tasks in Jira). | |
| Jun 7, 2021 at 9:13 | vote | accept | reneton | ||
| Jun 4, 2021 at 15:12 | history | answered | nvogel | CC BY-SA 4.0 |