Yes, Mark there is a real possibility that the unchanged configuration will not work if you have existing data (such as work items) that has been migrated from a previous of RTC.

If there are specific features you want to start using from the 2.0 version of the template, it may be more feasible to bring only those features into your project area. I am working on instructions for using some of the new reports and the new work item types, for example.

Are there specific features of the 2.0 template that you want to use in your project areas? If so, what are they?

Thanks,
Martha

@kesterto - agreed that I wouldn't want the upgrade process to just trounce all over my nicely customized process template, but we need a real story for how to incorporate these improvements to existing projects. It's a real barrier to upgrade, largely because people _should_ be constantly tweaking their process to reflect changes the team has agreed to -- and we don't want them afraid to upgrade to a newer version of the product.

@mandrew - thanks for the extra links and insights. Do you think it is the case that the "unchanged configuration" is in danger of not working based on the workflow concerns you note? We are fortunate enough to be very early in the process for our next release, so I can probably get away with a swap on the source (there have been no revisions so far) unless that case is in danger of not working also.

Thanks to both of you for sticking with this thread and helping me get this worked out. This will likely affect many teams using RTC (and working to move to 2.0) in my organization.

mandrew wrote:

Yes, Mark there is a real possibility that the unchanged configuration
will not work if you have existing data (such as work items) that has
been migrated from a previous of RTC.

If there are specific features you want to start using from the 2.0
version of the template, it may be more feasible to bring only those
features into your project area. I am working on instructions for
using some of the new reports and the new work item types, for
example.

Are there specific features of the 2.0 template that you want to use
in your project areas? If so, what are they?

Thanks,
Martha

Martha,

We tried to go that route. We began to create a list of 2.0 features we
wanted to add into our modified Scrum 1.0 template. The problem is that
our list soon became 95% of the Scrum 2.0 feature list.

What we ended up doing was this. We re-created all of our Scrum 1.0
modifications in a Scrum 2.0 template, and then applied the template to
our existing databases.

As you know, that left us with databases with many work items with
states and resolution codes which were now invalid. We developed a
program to find work items with these invalid states, and then map the
invalid states to new ones.

I know that there is a way to deal with invalid data with queries and
temporary template changes to the workflows, but this method is not
practical if you have dozens or hundreds of projects to upgrade to 2.0.

The only Scrum 2.0 change we did not include was the change in
priorities. We decided to avoid the issue of how to map 10 priorities
in our existing data down to a few by leaving the priorities as they
were in 1.0.

Mark Ingebretson