I tried Agilo a while back, hoping I could "massage" it into a waterfall methodology, and had limited success.
I find the Itteco Module more flexible and if I were to try it again, I would start with that as a base. However, Trac's workflow fits well into waterfall, and if you add MasterTickets and TypedTicketWorkflow, you can complete your V model pretty easily. The TypedTicketWorkflow would be your best bet if you wanted to "handoff" to your maintenance model without sending the ticket to a new Trac instance as well. Once a Ticket becomes "maintenance" type, you move it to "new" and if follows a separate workflow, or you could use the triage feature at that point to split the workflow. Aglio works well out of the box for scrum right from the get go. I suspect the KanBan style reporting can be done with custom workflow either way. Assuming 3 sub stages in each hand-off stage, you just happen to have a 9 step workflow: code_ToDo->code_Doing->code_DOMG->val_ToDo->val_Doing.... The hard part would be if you really wanted to do something when each bucket was "full" to prevent moving a task along the line. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Paul Boos Sent: Thursday, December 10, 2009 9:10 AM To: Trac Users Cc: [email protected] Subject: [Trac] Workflow - Project question 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. ______________________________________________________________________ CAUTION: This message was sent via the Public Internet and its authenticity cannot be guaranteed. ************************************************ The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email. ************************************************ Smiths Medical is the Medical division of Smiths Group plc. The Head Office of Smiths Medical is located at 1265 Grey Fox Road, St Paul, Minnesota, USA. -- 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.
