Yes, you can just start with the Simple Team Process, and move to Scrum
or whatever else you might want at a later time. In particular, your
SCM artifacts (streams, snapshot, workspaces) can be used with any
process, and are not restricted to be used just by the process you used
originally.

Cheers,
Geoff

On 7/12/2011 8:08 PM, hujirong wrote:

Hi

This is the first time we use RTC for the first project. As things are
delayed so much that the project team wants to put the source code
into RTC asap. They don't care about Work Items and processes right
now, bugs was managed in QTP and they have no plan to migrate them
over for now as well. All they want is to get the code into RTC and
start working. Now all I know is they want a mainline and a couple of
streams maybe for this project.

In this case, would it be a good idea to create a new project area
from Simple Team Process template? New timelines, streams,
components, type of team members, work items, etc. all can be added
later when I have more information, right? There is no limitation on
this, isn't it?

Thanks
Jirong

Yes, you can just start with the Simple Team Process, and move to Scrum
or whatever else you might want at a later time. In particular, your
SCM artifacts (streams, snapshot, workspaces) can be used with any
process, and are not restricted to be used just by the process you used
originally.

Cheers,
Geoff

On 7/12/2011 8:08 PM, hujirong wrote:

Hi

This is the first time we use RTC for the first project. As things are
delayed so much that the project team wants to put the source code
into RTC asap. They don't care about Work Items and processes right
now, bugs was managed in QTP and they have no plan to migrate them
over for now as well. All they want is to get the code into RTC and
start working. Now all I know is they want a mainline and a couple of
streams maybe for this project.

In this case, would it be a good idea to create a new project area
from Simple Team Process template? New timelines, streams,
components, type of team members, work items, etc. all can be added
later when I have more information, right? There is no limitation on
this, isn't it?

Thanks
Jirong

I'd just like to add that when Geoff says you can move to Scrum or another process, that he means you could later create a new project area using the Scrum process and then move your SCM artifacts over to that project area. It's not that you can change easily switch the process of an existing project area from Simple to Scrum.

- Jared

Let's be very explicit.

What is "easy" is at the end of a given iteration, create a new project
area with whatever process you want, and then move a few work items from
your old project area (with your old process) to your new project area
(with your new process). This is what I meant by "moving" to a new process.

What is "doable" is to evolve your process incrementally, by adding new
roles, new work item types, new iterations. This involves learning
about how to create those kinds of objects, but there are graphical
editors that help you do so.

What is "hard" is to try to just switch an existing project area from
one process type to a very different process type. Note that in 3.0, it
actually is easy to switch the process type of a project area ... just
create your original project area so that it uses the process from one
project area, and then when you want to switch the process type, go to
the Process Sharing tab of the project area editor, and use the process
from a different project area with the process type you want to switch
to. But what is hard is updating all of your existing work items to
conform to the available work item types in the new process.

Cheers,
Geoff

On 7/14/2011 3:08 PM, hujirong wrote:

jburnswrote:

I'd just like to add that when Geoff says you can move to Scrum or
another process, that he means you could later create a new project
area using the Scrum process and then move your SCM artifacts over to
that project area. It's not that you can change easily switch the
process of an existing project area from Simple to Scrum.

- Jared

Thanks a lot for this information. That's my original question. So is
it easy to transfer from Simple to Traditional? Assume I know how to
add additional timelines, streams, component and work items.

Jirong

Ok, we want to know where we can get this editor for RTC 3.0.1
Thanks

Let's be very explicit.

What is "easy" is at the end of a given iteration, create a new project
area with whatever process you want, and then move a few work items from
your old project area (with your old process) to your new project area
(with your new process). This is what I meant by "moving" to a new process.

What is "doable" is to evolve your process incrementally, by adding new
roles, new work item types, new iterations. This involves learning
about how to create those kinds of objects, but there are graphical
editors that help you do so.

What is "hard" is to try to just switch an existing project area from
one process type to a very different process type. Note that in 3.0, it
actually is easy to switch the process type of a project area ... just
create your original project area so that it uses the process from one
project area, and then when you want to switch the process type, go to
the Process Sharing tab of the project area editor, and use the process
from a different project area with the process type you want to switch
to. But what is hard is updating all of your existing work items to
conform to the available work item types in the new process.

Cheers,
Geoff

On 7/14/2011 3:08 PM, hujirong wrote:

jburnswrote:

I'd just like to add that when Geoff says you can move to Scrum or
another process, that he means you could later create a new project
area using the Scrum process and then move your SCM artifacts over to
that project area. It's not that you can change easily switch the
process of an existing project area from Simple to Scrum.

- Jared

Thanks a lot for this information. That's my original question. So is
it easy to transfer from Simple to Traditional? Assume I know how to
add additional timelines, streams, component and work items.

Jirong

In the Eclipse client, select the "Open" operation on your project area,
and select the Process Configuration tab.

Cheers,
Geoff


On 7/18/2011 2:08 PM, ishibmjazz wrote:

Ok, we want to know where we can get this editor for RTC 3.0.1
Thanks

gmclemmwrote:
Let's be very explicit.

What is "easy" is at the end of a given iteration, create
a new project
area with whatever process you want, and then move a few work items
from
your old project area (with your old process) to your new project
area
(with your new process). This is what I meant by "moving"
to a new process.

What is "doable" is to evolve your process incrementally,
by adding new
roles, new work item types, new iterations. This involves learning

about how to create those kinds of objects, but there are graphical

editors that help you do so.

What is "hard" is to try to just switch an existing
project area from
one process type to a very different process type. Note that in
3.0, it
actually is easy to switch the process type of a project area ...
just
create your original project area so that it uses the process from
one
project area, and then when you want to switch the process type, go
to
the Process Sharing tab of the project area editor, and use the
process
from a different project area with the process type you want to
switch
to. But what is hard is updating all of your existing work items to

conform to the available work item types in the new process.

Cheers,
Geoff

On 7/14/2011 3:08 PM, hujirong wrote:
jburnswrote:

I'd just like to add that when Geoff says you can move to Scrum or
another process, that he means you could later create a new project
area using the Scrum process and then move your SCM artifacts over
to
that project area. It's not that you can change easily switch the
process of an existing project area from Simple to Scrum.

- Jared

Thanks a lot for this information. That's my original question. So
is
it easy to transfer from Simple to Traditional? Assume I know how
to
add additional timelines, streams, component and work items.

Jirong

Yes, that is my understanding.

Cheers,
Geoff

On 7/19/2011 10:53 AM, hujirong wrote:

Hi Geoff

The Simple Process Template only generated one workflow
(bugzillaWorkflow), but there are three Work Items (Defect, Task and
Enhancement). Does that mean they all sharing the same workflow?

Thanks
Jirong