What do I need to consider when changing processes.
3 answers
In theory the update is straight forward: You take the process
specification XML from the template and copy it into your project area.
You also ensure that all needed process attachments are also copied from
the process template to the project area.
The theory translates into reality for all aspects of the process
specification with the exception of the work item configuration data.
The major issues that need to be taken care of are a) removal/renaming
of roles, b) workflow changes such as the removal of previously existing
workflow states, and c) the removal of work item types and their
associated editor presentations.
For a) you need to check whether any team area customization references
the removed/renamed roles and you need to update those that does.
b)is interesting as you might have work items in the removed state.
c) is interesting as you might have work items of this type that without
a presentation will be presented using the default editor presentation.
This might not give you access to fields you might want to access.
I let someone from the work item component comment on the specific
details how to handle b) and c).
Kai
Jazz Process Team
Aaron M. Cohen wrote:
specification XML from the template and copy it into your project area.
You also ensure that all needed process attachments are also copied from
the process template to the project area.
The theory translates into reality for all aspects of the process
specification with the exception of the work item configuration data.
The major issues that need to be taken care of are a) removal/renaming
of roles, b) workflow changes such as the removal of previously existing
workflow states, and c) the removal of work item types and their
associated editor presentations.
For a) you need to check whether any team area customization references
the removed/renamed roles and you need to update those that does.
b)is interesting as you might have work items in the removed state.
c) is interesting as you might have work items of this type that without
a presentation will be presented using the default editor presentation.
This might not give you access to fields you might want to access.
I let someone from the work item component comment on the specific
details how to handle b) and c).
Kai
Jazz Process Team
Aaron M. Cohen wrote:
I am planning on upgrading to Beta 3 and I want to change my current
project from Eclipse Way to Scrum. What is the best way to do this and
what considerations/preparations should I make prior?
Thanks!
Aaron, in addition to what Kai said, you basically need to create a
modified version of the Scrum template that uses all IDs for
enumerations, states etc. that were used by the Eclipse Way template.
You also need to merge in any customizations you did for your project
area, e.g. permissions, roles, custom attributes etc.
Once you are done with all changes, copy it over the existing project
configuration source and save the project area.
Some additional hints that may help you:
- The work item type 'Enhancement' is not part of the Scrum template.
You could decide to use it anyway and add the Enhancement type back, or
you could query for all enhancements and bulk-change them to Task or
maybe Story.
- Change the IDs for priority, severity etc.
Example:
In the Eclipse Way template, the high priority id was "4"
In the Scrum template, it is "priority.literal.l11"
So if you change the high priority ID in the Scrum template from
"priority.literal.l11" back to "4", all existing work items will show
the correct Scrum label "1 High".
For states and resolutions it is similar, but trickier. If a state
doesn't exist anymore in Scrum, you would have to change the state of
all work items that use it first, before applying the new process
configuration source. You may also choose to modify the workflow, so it
has the missing state again.
Please note also that the Scrum template was further improved over the
last couple of days and weeks, so it will be different in the next
build, and you may have to go through some of the work mentioned above
again.
HTH,
Patrick
Jazz Work Item Team
modified version of the Scrum template that uses all IDs for
enumerations, states etc. that were used by the Eclipse Way template.
You also need to merge in any customizations you did for your project
area, e.g. permissions, roles, custom attributes etc.
Once you are done with all changes, copy it over the existing project
configuration source and save the project area.
Some additional hints that may help you:
- The work item type 'Enhancement' is not part of the Scrum template.
You could decide to use it anyway and add the Enhancement type back, or
you could query for all enhancements and bulk-change them to Task or
maybe Story.
- Change the IDs for priority, severity etc.
Example:
In the Eclipse Way template, the high priority id was "4"
In the Scrum template, it is "priority.literal.l11"
So if you change the high priority ID in the Scrum template from
"priority.literal.l11" back to "4", all existing work items will show
the correct Scrum label "1 High".
For states and resolutions it is similar, but trickier. If a state
doesn't exist anymore in Scrum, you would have to change the state of
all work items that use it first, before applying the new process
configuration source. You may also choose to modify the workflow, so it
has the missing state again.
Please note also that the Scrum template was further improved over the
last couple of days and weeks, so it will be different in the next
build, and you may have to go through some of the work mentioned above
again.
HTH,
Patrick
Jazz Work Item Team
I will probably wait till the next build in order to use the latest
Scrum Process. I think this is a scenario that people may use come GA
where they go from one process to another. I am going to copy what you
and Kai suggested into Enhancement 57033.
Thanks!
Patrick Streule wrote:
Scrum Process. I think this is a scenario that people may use come GA
where they go from one process to another. I am going to copy what you
and Kai suggested into Enhancement 57033.
Thanks!
Patrick Streule wrote:
Aaron, in addition to what Kai said, you basically need to create a
modified version of the Scrum template that uses all IDs for
enumerations, states etc. that were used by the Eclipse Way template.
You also need to merge in any customizations you did for your project
area, e.g. permissions, roles, custom attributes etc.
Once you are done with all changes, copy it over the existing project
configuration source and save the project area.
Some additional hints that may help you:
- The work item type 'Enhancement' is not part of the Scrum template.
You could decide to use it anyway and add the Enhancement type back, or
you could query for all enhancements and bulk-change them to Task or
maybe Story.
- Change the IDs for priority, severity etc.
Example:
In the Eclipse Way template, the high priority id was "4"
In the Scrum template, it is "priority.literal.l11"
So if you change the high priority ID in the Scrum template from
"priority.literal.l11" back to "4", all existing work items will show
the correct Scrum label "1 High".
For states and resolutions it is similar, but trickier. If a state
doesn't exist anymore in Scrum, you would have to change the state of
all work items that use it first, before applying the new process
configuration source. You may also choose to modify the workflow, so it
has the missing state again.
Please note also that the Scrum template was further improved over the
last couple of days and weeks, so it will be different in the next
build, and you may have to go through some of the work mentioned above
again.
HTH,
Patrick
Jazz Work Item Team