Which 'denomination', or combination of, do I use. Out of Epics, Stories and sub-tasks.
When I have 2 stoies in a sprint, the Burndown chart only changes towards the end as the stories are set to "Done". I wish to split these stories in to smaller parts. It seems sub-taks don't have story points that are rolled up tp the story total (correct?). And Epics (with sub-stories) are probably too big for just one sprint (acording to Scrum guidelines). Any recomendations so I can track the burndown in smaller increments? Work is being done daily and 'jobs' finished, or rather features are ready to ready to release.
Another example, if there is one story in a sprint with 20 sub-tasks, the burndown chart only tracks when the story is set to "Done" not each of the sub-taks. Although there may be a sub-task completed daily.
I am favouring making the stories in to epics, and having sub-stories.
What is your advice?
I have the very same problem, and I'm looking for the answer, but I can't get one here or anywhere else.
PS. "It seems sub-taks don't have story points that are rolled up to the story total"
yes, that's correct.
Workaround for a shortfall in Jira is to make stories Epics, sub-tasks into stories.
Then you can allocate the ex-sub-tasks story points, and there is more granualrity in the burndown chart.
Poor countermeasure to a disappointing feature set in Jira.
Thank you for sharing - that's very helpful.
I have an additional issue, which may be resolved by using the Structure plugin...
That is, I'm unable visualize assignee name on the Scrum Board plan view (which is available in the Classic view).
...unless you know different.
We are using JIRA Cloud and this problem of not being able to track progress using story points is a very frustrating thing. You can enable story points to come up in sub-tasks at estimation time by enabling what issue types must have story-point. Go to Admin -> Custom fields -> Story Points -> Custom field.
Then select sub-task also as a issue type of Story Points.
But after doing all this we cannot track the progress. We cannot update the remaining story points for a sub-task nor it adds all the remaining story points in sub-tasks to the main user story. The way to do is to put work progress in hours and that is a stupid way.
We are actually thinking of moving away of JIRA mainly due to not being able to use the SCRUM process properly. It takes so much pain to just to get things configured and still it does not work. JIRA starting off as a issue tracking tool and now trying to incorporate Agile cos people demand it seems to mess up the whole software experience of JIRA.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Back in 2010 I hadn't been using the Atlassian tools (JIRA, Confluence, Bamboo) that long and I started searching online to see if I could chat to other users primarily about how they used the produc...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs