It's all about the answers!

Ask a question

Scrum -> Sprint Backlog and tasks


Sterling Ferguson-II (1.6k8281269) | asked Jul 16 '09, 9:48 a.m.
Hello all,

I am still new on learning RTC. I have created a project, and I am using:

http://www.ibm.com/developerworks/rational/library/08/0701_ellingsworth/

to try and setup a Scrum pilot group. I have "hopefully" been able to work around the differences with 1.x and 2.x, but I am at a part where I created the Sprint Backlog (with stories) and I need to add the task. On the above link, it discusses adding the tasks, and hitting tab to make them a part of the story. I can't do that in 2.x, I add a task, and hitting the tab does nothing.

How do I associate the tasks with the stories on the Sprint Backlog?

thanks...

3 answers



permanent link
Michael Scharf (781) | answered Jul 16 '09, 10:32 a.m.
In RTC 2.0, the backlog is a flat list of work items. That is why the parent-child relationship is not outlined.
Use the Work Breakdown view mode to breakdown your stories into tasks.

In RTC2, we greatly enhanced Scrum support, therefore parts of the document you mentioned can not be applied anymore.
You might want to read http://jazz.net/library/article/197, which discusses RTC2 planning features based on a Scrum project

--
MikeS
Jazz Agile Planning team


itengtools wrote:
Hello all,

I am still new on learning RTC. I have created a project, and I am
using:

http://www.ibm.com/developerworks/rational/library/08/0701_ellingsworth/

to try and setup a Scrum pilot group. I have "hopefully"
been able to work around the differences with 1.x and 2.x, but I am
at a part where I created the Sprint Backlog (with stories) and I
need to add the task. On the above link, it discusses adding the
tasks, and hitting tab to make them a part of the story. I can't do
that in 2.x, I add a task, and hitting the tab does nothing.

How do I associate the tasks with the stories on the Sprint Backlog?

thanks...

permanent link
Sterling Ferguson-II (1.6k8281269) | answered Jul 17 '09, 6:43 p.m.
Thanks!!

This was very helpful!!!!

I am now trying to massage the data that was already entered from a previous tutorial. I was following a tutorial and trying to create a project "side-by-side". The tutorial that I followed recommended that I create groups/categories. So basically, you create a task, assign a category, and then your choice list is limited to the matching group that was created and their members.

Ex.
Category/group = WebUI
Category/group = Client

While this seemed great, I see that there is a Backlog category. Do I keep this? Also, when I went to fill in the user's Resource time, it seems to have taken the project and category field into the area. So the Project is named Helpdesk Application and I have to divide the resource availability as follows:

instead of just one project
Helpdesk Application 80%

It lists the categories and projects
Helpdesk Application 50%
WebUI 50%

What did I do wrong?

In RTC 2.0, the backlog is a flat list of work items. That is why the parent-child relationship is not outlined.
Use the Work Breakdown view mode to breakdown your stories into tasks.

In RTC2, we greatly enhanced Scrum support, therefore parts of the document you mentioned can not be applied anymore.
You might want to read http://jazz.net/library/article/197, which discusses RTC2 planning features based on a Scrum project

--
MikeS
Jazz Agile Planning team


permanent link
Geoffrey Clemm (30.1k33035) | answered Jul 18 '09, 11:58 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
You could keep the generic "backlog" category if you wanted some default
category to use for things that don't fit in any more specific category.
But in your case, I'd probably suggest archiving it, until you find
you have a need for it.

When you say "user's Resource time", do you mean the "Work Assignments"
panel in the Work Environment page of the User editor? If so, the
number of sections is based on the team areas that a given user is a
member of (and the time lines in the project areas that a given user is
a member of), not the number of categories (you may have named a team
area or project area the same as one of your categories, which might be
confusing things).

Cheers,
Geoff

itengtools wrote:
Thanks!!

This was very helpful!!!!

I am now trying to massage the data that was already entered from a
previous tutorial. I was following a tutorial and trying to create a
project "side-by-side". The tutorial that I followed
recommended that I create groups/categories. So basically, you create
a task, assign a category, and then your choice list is limited to the
matching group that was created and their members.

Ex.
Category/group = WebUI
Category/group = Client

While this seemed great, I see that there is a Backlog category. Do I
keep this? Also, when I went to fill in the user's Resource time, it
seems to have taken the project and category field into the area. So
the Project is named Helpdesk Application and I have to divide the
resource availability as follows:

instead of just one project
Helpdesk Application 80%

It lists the categories and projects
Helpdesk Application 50%
WebUI 50%

What did I do wrong?

Michael Schneiderwrote:
In RTC 2.0, the backlog is a flat list of work items. That is why the
parent-child relationship is not outlined.
Use the Work Breakdown view mode to breakdown your stories into
tasks.
In RTC2, we greatly enhanced Scrum support, therefore parts of the
document you mentioned can not be applied anymore.
You might want to read http://jazz.net/library/article/197, which
discusses RTC2 planning features based on a Scrum project
--
MikeS
Jazz Agile Planning team


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.