On Fri, 19 Oct 2007 14:57:23 -0400, Doug Douglass <[EMAIL PROTECTED]> wrote:
> Steve, > > Maybe not quite what you're after but after working with the scrum > burndown > plugin and the gaant chart plugin and the time and estimation plugin > here's > where we are currently: > * how much time are we spending on production support vs. development > task (yeah, we've got some legacy systems) Doug, Thanks for the great explanation of how you are using Trac. I'm contemplating using a combination of trac + a scrum worksheet I downloaded from scrumalliance.org to do what you have mentioned. Alternately, I may just ask our development team to add hours each day to their tasks and also update the 'estimated hours' field in the ticket with the understanding that estimated hours = hours spent + how many hours they think are left. In that manner I could use the timing/estimation and burndown plugins as-is. This is not trac-related, but I'm curious to know how you incorporate production support into your sprints. Our organization spends a LOT of time on unplanned production support issues, and I'm trying to think of the best way to incorporate this into our sprints. Two options: 1. Set aside production support as a Backlog item (Trac task) with a set number of hours each sprint. 2. Add production support tasks as they come up during a sprint, and drop sprint backlog tasks if necessary from the sprint. Scrum/Trac users - what are your thoughts? thanks, Steve --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
