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:
- does the burndown get calculated on 100h or 120h? Is it useful to track that the scope has expanded, or is this one of those things that really doesn't matter too much
- how do you handle an increase in requirements (not personally, but in terms of using jira/greenhopper) - is this a sensible approach, or is it better to be pedantic and start a separate sprint for the 20h
- is there a better way to look at allocation than switching to classic view? Tools like pivotal seem to make this much easier - it seems a bit naieve to be just throwing estimates in and seeing total time (rather than estimated work vs available resource hours)
thankyou!
