How to create a lifecycle project
How can i create a lifecycle project containing two or more Change and Configuration Management projects?
As i mentioned somewhere else in this forum,
our company wanted to use RTC for better project planing and bugtracking for further projects.
But what we need is the option to "link" these projects in rtc.
so i came across the ALM Projects, is this the right way of doing what we need?
Or how does the process consumption (in the overview Tab of the project settings) works?
Are there any guides/Tutorials how to use this?
At least, we have one base project, handling the base features of our product line. From this project, we derived some other projects for additional or spezialized features.
So, what we want is the following:
If for example, a customer reports a bug in his derived project, he should be able to set the "found in" property to all of the projects, he is able to see.
The developer (tester, whatever) then look, if it not could be a bug in the base project and, if so, changing the "found in" property to this.
Also, the "planed for" property of the workitem should show the iterations of ALL projects.
How could this be realized?
We use Version 3.0.1
As i mentioned somewhere else in this forum,
our company wanted to use RTC for better project planing and bugtracking for further projects.
But what we need is the option to "link" these projects in rtc.
so i came across the ALM Projects, is this the right way of doing what we need?
Or how does the process consumption (in the overview Tab of the project settings) works?
Are there any guides/Tutorials how to use this?
At least, we have one base project, handling the base features of our product line. From this project, we derived some other projects for additional or spezialized features.
So, what we want is the following:
If for example, a customer reports a bug in his derived project, he should be able to set the "found in" property to all of the projects, he is able to see.
The developer (tester, whatever) then look, if it not could be a bug in the base project and, if so, changing the "found in" property to this.
Also, the "planed for" property of the workitem should show the iterations of ALL projects.
How could this be realized?
We use Version 3.0.1
3 answers
One important thing to keep in mind is that a "project area" is a place
where projects with a common process are located. So as long as your
projects have a shared notion of things like work item types and state
models, then you'd usually allocate a separate team area for each of
your projects within that project area (i.e. you commonly wouldn't
create a separate project area for each project).
Cheers,
Geoff
On 10/19/2011 4:23 AM, incredibleleitman wrote:
where projects with a common process are located. So as long as your
projects have a shared notion of things like work item types and state
models, then you'd usually allocate a separate team area for each of
your projects within that project area (i.e. you commonly wouldn't
create a separate project area for each project).
Cheers,
Geoff
On 10/19/2011 4:23 AM, incredibleleitman wrote:
How can i create a lifecycle project containing two or more Change and
Configuration Management projects?
As i mentioned somewhere else in this forum,
our company wanted to use RTC for better project planing and
bugtracking for further projects.
But what we need is the option to "link" these projects in
rtc.
so i came across the ALM Projects, is this the right way of doing what
we need?
Or how does the process consumption (in the overview Tab of the
project settings) works?
Are there any guides/Tutorials how to use this?
At least, we have one base project, handling the base features of our
product line. From this project, we derived some other projects for
additional or spezialized features.
So, what we want is the following:
If for example, a customer reports a bug in his derived project, he
should be able to set the "found in" property to all of the
projects, he is able to see.
The developer (tester, whatever) then look, if it not could be a bug
in the base project and, if so, changing the "found in"
property to this.
Also, the "planed for" property of the workitem should show
the iterations of ALL projects.
How could this be realized?
We use Version 3.0.1
One important thing to keep in mind is that a "project area" is a place
where projects with a common process are located. So as long as your
projects have a shared notion of things like work item types and state
models, then you'd usually allocate a separate team area for each of
your projects within that project area (i.e. you commonly wouldn't
create a separate project area for each project).
Cheers,
Geoff
Thanks for your reply :)
To make sure, i understand what you are meaning,
"a common process" is the Process Description (which i can't modify after project creation) within the Project Area in the overview tab? (such as scrum, simple teamprocess and so on...)
So if i try to combine scrum project with a simple team project, that woudn't work?
For further explaination of our case,
we create more projects because each of them has different timelines and we (only one developer team) are working at all of them at the same time,
and i found no way to set more than one current iteration representing the actual release for each project.
Yes, by "common process", I meant something like Scrum vs. Formal
Project Management. More formally, it is what appears under the
Project Configuration node in the Process Configuration. The "Team
Configuration" part of the process can be overridden/modified in the
team areas (as long as that part of the process hasn't been marked as
"frozen" by the project lead for that project area).
WRT current iterations, each timeline within a project area has its own
separate "current" iteration (but within a given timeline, at most one
iteration can be current).
Cheers,
Geoff
On 10/20/2011 6:38 AM, incredibleleitman wrote:
Project Management. More formally, it is what appears under the
Project Configuration node in the Process Configuration. The "Team
Configuration" part of the process can be overridden/modified in the
team areas (as long as that part of the process hasn't been marked as
"frozen" by the project lead for that project area).
WRT current iterations, each timeline within a project area has its own
separate "current" iteration (but within a given timeline, at most one
iteration can be current).
Cheers,
Geoff
On 10/20/2011 6:38 AM, incredibleleitman wrote:
gmclemmwrote:
One important thing to keep in mind is that a "project
area" is a place
where projects with a common process are located. So as long as
your
projects have a shared notion of things like work item types and
state
models, then you'd usually allocate a separate team area for each of
your projects within that project area (i.e. you commonly wouldn't
create a separate project area for each project).
Cheers,
Geoff
Thanks for your reply :)
To make sure, i understand what you are meaning,
"a common process" is the Process Description (which i can't
modify after project creation) within the Project Area in the overview
tab? (such as scrum, simple teamprocess and so on...)
So if i try to combine scrum project with a simple team project, that
woudn't work?
For further explaination of our case,
we create more projects because each of them has different timelines
and we (only one developer team) are working at all of them at the
same time,
and i found no way to set more than one current iteration representing
the actual release for each project.