Modifying process template through a project's lifetime
Hi, I'm working in a group that will be using RTC. We'd like to take an
agile approach to defining the process configuration :-) We'll define a single project area using the out-of-the-box 'agile process template'. To start we'll bring one or two teams on board. As we progress we expect to add in a new work item type, maybe slightly change the workflow of an existing work item type, and of course other modifications which I don't yet know about. Basically, the 'agile process teamplte' fits well, but we expect to need to modify it as we progress. I'm concerned about what happens to existing repository work item data after a process configuration change. Is there any guidance on what can and can't be done to the process configuration once the RTC repository is running with live data? (e.g. if I have work items in the state X and I remove that state, what happens to them?) And if a frowned-upon process configuration change is made, what should be done to ensure the data is coherent with the modified process configuration. Many thanks, Jeremy |
One answer
We still need to write a technote about this topic. Initial material for
that note can be found here: https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/60035 Kai Jazz Process Team Jeremy Hughes wrote: Hi, I'm working in a group that will be using RTC. We'd like to take an |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.