Here is my scenario: I've added tasks, my team has reviewed and estimated time (we use time rather than points), we've allocated tasks and clicked "start" on the greenhopper sprint. Total time estimate is 100h. A few days in, we've had an influx of tasks that I need to add in, so I create an extra 20h of tasks.
Before I commit to doing this 20h, I need to look at capacity of my team. I switch to "classic" greenhopper to see existing work allocation per team member, and see that one person doesn't have much so OK to proceed. I add the tasks to the sprint.
My questions are:
No one seems to have an answer, but here are my findings so far
1. Does the burndown get calculated on 100h or 120h?
Burndown guide is just a line- there is no smarts to it. The actual red progress line will jump up to indicate
2. Separate sprint or combined?
I've been finding just add to the main sprint is easier- it is a hassle to maintain lots of smaller sprints for what is essentially a change request/scope change. I've never needed to track that separately
3. looking at allocation
I've created a google spreadsheet which pulls in all the sprints I'm interested in via XML, then I use google query to build a graph which causes grown developers to cry it is so beautiful.
As a Belgian, beer-lover and home brewer, beer is one of my great passions. I love the fact that with just a few ingredients (usually just water, hop and malt) you can create so many different tastes...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot