It's all about the answers!

Ask a question

Filters on Plans


Adam Coulthard (1322116) | asked Aug 04 '09, 4:53 p.m.
Hi,

This is on the same lines as my post about team release plans. I've been working on the plans for my teams implementation of Rational Team Concert and in the Plan item view there is a set of filters. One of this is exclude / show execution items, my question is what defines an execution item? Because for a Project Release Plan this appears to be stories in our setup (we have plan items and enhancements as the top level work items) but tasks and defects do not seem to be treated as ones.

I've also got the problem of other work item types that we have created which a execution items but I'm not sure how to define them as such. Is there a place to define what an execution item is?

Thanks

6 answers



permanent link
Michael Scharf (781) | answered Aug 04 '09, 6:06 p.m.
adamcoulthard wrote:
Hi,

This is on the same lines as my post about team release plans. I've
been working on the plans for my teams implementation of Rational
Team Concert and in the Plan item view there is a set of filters.
One of this is exclude / show execution items, my question is what
defines an execution item? Because for a Project Release Plan this
appears to be stories in our setup (we have plan items and
enhancements as the top level work items) but tasks and defects do
not seem to be treated as ones.

I've also got the problem of other work item types that we have
created which a execution items but I'm not sure how to define them
as such. Is there a place to define what an execution item is?

Thanks


yes :-)
open the "Process Configuration" tab of your Project Area editor and navigate to "Project Configuration" -> "Configuration Data" -> "Planning" -> "Top-Level Work Item Types".
More information can be found here: http://jazz.net/library/article/201

--
MikeS
Jazz Agile Planning team

permanent link
Geoffrey Clemm (30.1k33035) | answered Aug 04 '09, 11:46 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Mike,

The tab you describe allows you to define what are the top level work
item types, but Adam was asking how you define what types are execution
item types. In particular, if you define a new work item type, how do
you specify whether or not that new work item type is an execution item?
The only thing I could find in article 201 about execution items was:

"Agile methods distinguish between sizing plan items and estimating
execution items. Usually, plan items are sized using an abstract value.
Scrum, for example, uses story points but other agile methods might use
any other abstract value, such as gummy bears. In contrast, execution
item effort is estimated in working hours."

But this seems to only say how execution types are to be used, not how
you specify whether a type is an execution type ... or am I missing
something?

Cheers,
Geoff



Michael Schneider wrote:
adamcoulthard wrote:
Hi,

This is on the same lines as my post about team release plans. I've
been working on the plans for my teams implementation of Rational
Team Concert and in the Plan item view there is a set of filters. One
of this is exclude / show execution items, my question is what
defines an execution item? Because for a Project Release Plan this
appears to be stories in our setup (we have plan items and
enhancements as the top level work items) but tasks and defects do
not seem to be treated as ones.

I've also got the problem of other work item types that we have
created which a execution items but I'm not sure how to define them
as such. Is there a place to define what an execution item is?

Thanks


yes :-)
open the "Process Configuration" tab of your Project Area editor and
navigate to "Project Configuration" -> "Configuration Data" -
"Planning" -> "Top-Level Work Item Types".
More information can be found here: http://jazz.net/library/article/201

permanent link
Michael Scharf (781) | answered Aug 05 '09, 2:37 a.m.
Geoffrey Clemm wrote:
Hi Mike,

The tab you describe allows you to define what are the top level work
item types, but Adam was asking how you define what types are execution
item types. In particular, if you define a new work item type, how do
you specify whether or not that new work item type is an execution item?
The only thing I could find in article 201 about execution items was:

"Agile methods distinguish between sizing plan items and estimating
execution items. Usually, plan items are sized using an abstract value.
Scrum, for example, uses story points but other agile methods might use
any other abstract value, such as gummy bears. In contrast, execution
item effort is estimated in working hours."

But this seems to only say how execution types are to be used, not how
you specify whether a type is an execution type ... or am I missing
something?

Cheers,
Geoff



The agile planning tools distinguish between top level and execution item types only. Therefore, all work item types not marked as top level item types are considered to be execution item types.
Specifying whether an type is an execution type is achieved by specifying that it is not a top level item type.

--
MikeS
Jazz Agile Planning team

permanent link
Geoffrey Clemm (30.1k33035) | answered Aug 05 '09, 8:39 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Thanks Michael! I've submitted work item 89261 to get this information
into the RTC documentation, and work item 89262 to get a comprehensive
glossary for RTC into the dynamic help documentation.

Cheers,
Geoff

Michael Schneider wrote:
Geoffrey Clemm wrote:
Hi Mike,

The tab you describe allows you to define what are the top level work
item types, but Adam was asking how you define what types are
execution item types. In particular, if you define a new work item
type, how do you specify whether or not that new work item type is an
execution item? The only thing I could find in article 201 about
execution items was:

"Agile methods distinguish between sizing plan items and estimating
execution items. Usually, plan items are sized using an abstract
value. Scrum, for example, uses story points but other agile methods
might use any other abstract value, such as gummy bears. In contrast,
execution item effort is estimated in working hours."

But this seems to only say how execution types are to be used, not how
you specify whether a type is an execution type ... or am I missing
something?

Cheers,
Geoff



The agile planning tools distinguish between top level and execution
item types only. Therefore, all work item types not marked as top level
item types are considered to be execution item types.
Specifying whether an type is an execution type is achieved by
specifying that it is not a top level item type.

permanent link
Adam Coulthard (1322116) | answered Aug 20 '09, 6:59 a.m.
Thanks for the help Michael and Geoff. Sorry I'd not replied sooner I've had so much work on that not had a chance to get back to reply.

I had wondered whether specifying the top level work items meant that all the rest defaulted to being execution items. I assume that execution items are handled differently between plans because on some plans I only get storys added when I check include execution items when I would have expected all the tasks and defects to be shown as well.

permanent link
Michael Scharf (781) | answered Aug 21 '09, 5:44 a.m.
could you post detailed steps of what you are doing and when you are seeing a behavior that you do not expect?

Thanks!

--
MikeS
Jazz Agile Planning team

adamcoulthard wrote:
Thanks for the help Michael and Geoff. Sorry I'd not replied sooner
I've had so much work on that not had a chance to get back to reply.

I had wondered whether specifying the top level work items meant that
all the rest defaulted to being execution items. I assume that
execution items are handled differently between plans because on some
plans I only get storys added when I check include execution items
when I would have expected all the tasks and defects to be shown as
well.

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.