How to work with Tasks (story level) when it comes to sprint burndown

We are working with Epics, Stories and Subtasks. However, as far as I understand it, technical tasks (e.g. DB normalization) should not be user stories as there is no direct value visible to the customer and hence it should be marked as Task - if I understand, Task can be at the same level as story?

But if we start using Tasks, then the burndown will not reflect the reality as all stories might be done but technical tasks still in progress, which will not be visible.

Or is there a better way of working with technical tasks in SCRUM?

1 answer

0 votes

Technical tasks usually would be of type sub-task under a story. That is exactly why you see a default sub-task type called "Technical Task".

Stories would be estimated and will then be broken down into different types of sub-tasks by the assignees when they work on them. The most successful method I have seen is when stories are estimated in story points and the sub-tasks in hours. You will find a number of threads about that in this forum.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Jira

Looking for anyone who made the switch to Data Center

The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...

50 views 0 2
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you