Upgrading the process on a live project in 2.0.0.2
Hi
Is there a way to upgrade the process on an existing project to a new process. For example, moving a project created using the original 2.0 Scrum process template to the process you would get from the shiny new 2.0.0.2 Scrum process template?
I know we could go and very carefully "adjust" the XML - I was hoping there was a more automated and safer way to do this.
thanks
anthony
Is there a way to upgrade the process on an existing project to a new process. For example, moving a project created using the original 2.0 Scrum process template to the process you would get from the shiny new 2.0.0.2 Scrum process template?
I know we could go and very carefully "adjust" the XML - I was hoping there was a more automated and safer way to do this.
thanks
anthony
6 answers
Hi Anthony,
The support here isn't tooled as well as it could be, but it's doable by hand. The following documents outline the steps:
https://jazz.net/wiki/bin/view/Main/ProcessUpdateForExistingProjectAreas
http://www-01.ibm.com/support/docview.wss?rs=3488&uid=swg21390698
Cheers,
Jean-Michel
The support here isn't tooled as well as it could be, but it's doable by hand. The following documents outline the steps:
https://jazz.net/wiki/bin/view/Main/ProcessUpdateForExistingProjectAreas
http://www-01.ibm.com/support/docview.wss?rs=3488&uid=swg21390698
Cheers,
Jean-Michel
On Wed, 06 Jan 2010 16:53:01 +0000, millarde wrote:
We are currently developing a tool which will automate the process of
upgrading an existing project area to the Scrum/OpenUP templates shipped
in RTC 2.0.0.2. The changes applied by the tool will be limited in scope
- it will just add any new features introduced in the latest templates
like new work item types and dashboard templates.
This work is being tracked in work item 96618: "Allow users to add
features from templates shipped with RTC 2.0 to project areas created
with templates shipped with RTC 1.0.1.1"
https://jazz.net/jazz/resource/itemName/
com.ibm.team.workitem.WorkItem/96618
When the tool is ready (hopefully in the next few weeks), it will include
documentation of exactly which features are added. Going from RTC 2.0 to
RTC 2.0.0.2, I don't think there will be much; probably just an estimate
validator that was added to Agile Planning.
--
Jared Burns
Jazz Process Team
jlemieuxwrote:
Hi Anthony,
The support here isn't tooled as well as it could be, but it's
doable by hand. The following documents outline the steps:
https://jazz.net/wiki/bin/view/Main/ProcessUpdateForExistingProjectAreas
http://www-01.ibm.com/support/docview.wss?rs=3488&uid=swg21390698
Cheers,
Jean-Michel
Any chance of getting the first reference updated with the changes for
2.0.0.2? It nicely lays out what's needed for 1.x -> 2.0 and 2.0.0.1,
but nothing about 2.0.0.2.
Any likelihood of getting better support for this? This is by far the
most frustrating part of using an otherwise fantastic tool.
Millard
We are currently developing a tool which will automate the process of
upgrading an existing project area to the Scrum/OpenUP templates shipped
in RTC 2.0.0.2. The changes applied by the tool will be limited in scope
- it will just add any new features introduced in the latest templates
like new work item types and dashboard templates.
This work is being tracked in work item 96618: "Allow users to add
features from templates shipped with RTC 2.0 to project areas created
with templates shipped with RTC 1.0.1.1"
https://jazz.net/jazz/resource/itemName/
com.ibm.team.workitem.WorkItem/96618
When the tool is ready (hopefully in the next few weeks), it will include
documentation of exactly which features are added. Going from RTC 2.0 to
RTC 2.0.0.2, I don't think there will be much; probably just an estimate
validator that was added to Agile Planning.
--
Jared Burns
Jazz Process Team
Hi Anthony,
The support here isn't tooled as well as it could be, but it's doable by hand. The following documents outline the steps:
https://jazz.net/wiki/bin/view/Main/ProcessUpdateForExistingProjectAreas
http://www-01.ibm.com/support/docview.wss?rs=3488&uid=swg21390698
Cheers,
Jean-Michel
Any chance of getting the first reference updated with the changes for 2.0.0.2? It nicely lays out what's needed for 1.x -> 2.0 and 2.0.0.1, but nothing about 2.0.0.2.
Any likelihood of getting better support for this? This is by far the most frustrating part of using an otherwise fantastic tool.
Millard
Yes, improved support in this area is planned for RTC-3.0.
See work item 95348 (and its parent and child work items) for details.
Cheers,
Geoff
millarde wrote:
See work item 95348 (and its parent and child work items) for details.
Cheers,
Geoff
millarde wrote:
jlemieuxwrote:
Hi Anthony,
The support here isn't tooled as well as it could be, but it's
doable by hand. The following documents outline the steps:
https://jazz.net/wiki/bin/view/Main/ProcessUpdateForExistingProjectAreas
http://www-01.ibm.com/support/docview.wss?rs=3488&uid=swg21390698
Cheers,
Jean-Michel
Any chance of getting the first reference updated with the changes for
2.0.0.2? It nicely lays out what's needed for 1.x -> 2.0 and
2.0.0.1, but nothing about 2.0.0.2.
Any likelihood of getting better support for this? This is by far the
most frustrating part of using an otherwise fantastic tool.
Millard
For an upgraded system, what is the effect of the new plan creation approach on existing plans? Is the wizard just better or is there something that would make the existing plans not work well with newly created plans? I wouldn't expect it to be a problem, but I'd like to know before I put in the effort to upgrade.
Thanks...Millard
Thanks...Millard
Thanks Jared.
To take advantage of the new 2.0.0.2 in your templates, most of the features are described in the N&N and are in the 2.0.0.2 demo. You can enable a backlog iteration and create a typed backlog plan. But this isn't auto-mergable into the process spec, because as Jared said, these are new features which get blended and someone has to decide how they fit into your existing process.
Cheers,
Jean-Michel
To take advantage of the new 2.0.0.2 in your templates, most of the features are described in the N&N and are in the 2.0.0.2 demo. You can enable a backlog iteration and create a typed backlog plan. But this isn't auto-mergable into the process spec, because as Jared said, these are new features which get blended and someone has to decide how they fit into your existing process.
Cheers,
Jean-Michel