A question on Agile 6.4
I've read several pages from Atlasssian on the benefits of estimating using story points, but burning down using time (for example, this post).
I'm not sure how this works in JIRA Agile.
In my testing, I've configured a board to use Story Points as the estimation statistic, and Remaining Estimate and Time Spent for time tracking.
During planning, we assign story points to the sprints stories, and start the sprint (JIRA then complains some tickets don't have estimates on them - we've only estimated Story Points).
What is the workflow after that? We can't burn-down time, as there is no starting point for each task - we can only burn-down story points.
Any pointers appreciated,
As your tracking statistics is time (instead of story points), you MUST provide an original estimate (in units of time) to all your stories.
This original estimate will then be used by theburndown chart to create the burndown.
Developers will be expected to log time asthey progress and this will reflect in the burndown chart.
I suggest you play around with a test burndown chart to get familiarised with the concepts. there is a learning curve espicially if are using story points and time as estimation adn tracking statistic.
I am not attaching any links here as i assume you have already gone through the documentation on these concetps.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
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