Burndown taking multiple developers for estimation

When I put all my tasks into the sprint, and set the burn down to be based off time esitmates.

The chart just shows the total ammount of effort, and does not take into account the tasks will be assigned to muliple developers and some can be done simulanteously.

I've tried assigning the tasks to different developers, and this has no effect.

So a three week sprint, is actually coming out at 6 weeks, because we can't get the burndown to take into account the project has three developers.

2 answers

1 accepted

0 votes
Accepted answer

What i mean is I have New Feature A assigned to developer A, and New Feature B assigned to Developer B, however when doing the burndown it is as if these features will be implemented one after the other when in fact the reality is Feature A and B will be implemented at the same time.

0 votes
Timothy Chin Community Champion Jun 22, 2013

JIRA has never adopted the concept of an issue assigned to multiple people. So yea, what you're doing is not possible. If you have 2 developers at 2 story points each, then the issue must have 4 story points.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published yesterday in Agile

How Scrum works? It starts with training and education

To answer “How scrum works,” most of the teams I've worked with first addressed the question: “where to start?”  That question applies to both implementation and improvements on the Scrum framew...

142 views 3 5
Read article

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