Release Plan Roll up...
Using RTC 2.0 beta and I have a question about the roll up capabilities of Iteration Plans to a Release Plan.
1) I understand that the desire to measure a release's likelyhood of being on time by measuring a complexity factor. OOTB you can choose a few things, Story Points being maybe the closest out of the box. Why can I not roll up load or work hours?
2) When I configure the Release Plan, I have to choose what Iteration it is for, why is that? Can you not associate the plan to a main development line and have all iterations underneath roll up to this Release Plan? As is, it's more like a parent iteration plan than a plan for the whole release.
1) I understand that the desire to measure a release's likelyhood of being on time by measuring a complexity factor. OOTB you can choose a few things, Story Points being maybe the closest out of the box. Why can I not roll up load or work hours?
2) When I configure the Release Plan, I have to choose what Iteration it is for, why is that? Can you not associate the plan to a main development line and have all iterations underneath roll up to this Release Plan? As is, it's more like a parent iteration plan than a plan for the whole release.
2 answers
Does RTC 2.0 M3 solve this with the implementation of the Project Release Plan?
I cannot tell because it still states "for an iteration" at... https://jazz.net/downloads/rational-team-concert/milestones/2.0M3?p=news
"There is a new plan type called a Project Release Plan. A project release plan shows all top level work items (e.g. for Scrum Stories and Epics) for an iteration and all its child iterations as well as for a team or project area and all its child team areas. Such a plan gives a high level overview of the work plan for a whole release and a group of teams."
I cannot tell because it still states "for an iteration" at... https://jazz.net/downloads/rational-team-concert/milestones/2.0M3?p=news
"There is a new plan type called a Project Release Plan. A project release plan shows all top level work items (e.g. for Scrum Stories and Epics) for an iteration and all its child iterations as well as for a team or project area and all its child team areas. Such a plan gives a high level overview of the work plan for a whole release and a group of teams."
RTC 2.0 will not rollup hours on release plans. The reason for this is
that in an agile approach future iterations aren't estimated yet. And
rolling up past information alone isn't very helpful.
However we rollup the complexity attribute for release plans for all
iterations to use the volocity of the past iterations to plan the work
for future iterations.
Dirk Bumer
Agile Planning Component
pawrampe wrote:
that in an agile approach future iterations aren't estimated yet. And
rolling up past information alone isn't very helpful.
However we rollup the complexity attribute for release plans for all
iterations to use the volocity of the past iterations to plan the work
for future iterations.
Dirk Bumer
Agile Planning Component
pawrampe wrote:
Does RTC 2.0 M3 solve this with the implementation of the Project
Release Plan?
I cannot tell because it still states "for an iteration"
at...
https://jazz.net/downloads/rational-team-concert/milestones/2.0M3?p=news
"There is a new plan type called a Project Release Plan. A
project release plan shows all top level work items (e.g. for Scrum
Stories and Epics) for an iteration and all its child iterations as
well as for a team or project area and all its child team areas. Such
a plan gives a high level overview of the work plan for a whole
release and a group of teams."