I'm sort of interested in how Tracs features can best support the following:
We currently do projects in a waterfall method, but hope to become more agile, most likely using more of a Scrum process. When a project completes, we use Kanban to manage our issues. As a result one application can have two different workflows depending on whether the issue is in development or is undergoing a maintenance type issue. I would envision something like this: New Development for a 1.0 release, issues tracked to ensure they are known and stamped out before deployment. Some issues may not be fixed and woudl be passed along as issues to maintenance. Waterfall -> Scrum (eventually). Maintenance issues get handled via Kanban; larger issues may accumulate for future large release (development) efforts to be passed back to a development process as above. I've been looking into Itteco or Agilo to provide the visualization for Kanban and Scrum (or Waterfall I guess for that matter). What I am unclear on is what would be a smart way to deploy and utilize Scrum given the two different workflows we are interested in... My initial inclination is that perhaps there would be two different instances of Trac and we woudl pass issues between them. sidenote: I am also interested in setting up some templates in the Trac wiki for the ReadySet templates at readyset.tigris.org anyone have some experience in setting up such a complex template set on Trac? Thanks for some general insights or opinions on this. Thanks! Paul PS - please cc replies to [email protected] as well as [email protected] -- 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.
