Separate tasks per Sprint Backlog

Anyone? I really need to understand this in order to continue working on my project.

Thank you very much.

I'm not quite sure I follow you're scenario, but here are some thoughts
that might be relevant:

If your plan is targeting the second iteration (in the configuration of
the plan), then you will see all work items in the second iteration,
which includes work items from sprint b and sprint c. As I recall, you
can configure the plan to group by iteration, which would then separate
the sprint b work items from the sprint c work items.

If you want a plan that only shows work items from sprint b, then
configure the plan to target sprint b, not iteration two.

Cheers,
Geoff

On 10/6/2011 3:53 PM, mochomocho wrote:

Hello everybody,

I have a concept question about iterations, plans and sprints.

I'm using a scrum template and I have defined 2 iterations in the
project area.

In the first iteration I created 1 sprint backlog (sprint a) and in
the second iteration I have 2 sprint backlogs (sprint b and sprint
c)
When I add tasks to the sprint b and c and then I look to the second
iteration, all the tasks are mixed up on both sprints.

My question is, how can I leave the tasks independent from each sprint
(b and c) on the same iteration?

Thanks!

Geoff, thanks for replying.

So, your suggestion is that I have to make 1 plan for each iteration?

Then why one can make more than one plan per iteration? That's when I get lost.

I'm not quite sure I follow you're scenario, but here are some thoughts
that might be relevant:

If your plan is targeting the second iteration (in the configuration of
the plan), then you will see all work items in the second iteration,
which includes work items from sprint b and sprint c. As I recall, you
can configure the plan to group by iteration, which would then separate
the sprint b work items from the sprint c work items.

If you want a plan that only shows work items from sprint b, then
configure the plan to target sprint b, not iteration two.

Cheers,
Geoff

Plans can be configured very differently (task board, work breakdown,
etc., as well as all the custom choices). So teams will sometimes have
more than one plan for a given iteration, differing in how they are
configured.

Cheers,
Geoff

On 10/7/2011 1:38 PM, mochomocho wrote:

Geoff, thanks for replying.

So, your suggestion is that I have to make 1 plan for each iteration?

Then why one can make more than one plan per iteration? That's when I
get lost.

gmclemmwrote:
I'm not quite sure I follow you're scenario, but here are some
thoughts
that might be relevant:

If your plan is targeting the second iteration (in the configuration
of
the plan), then you will see all work items in the second iteration,

which includes work items from sprint b and sprint c. As I recall,
you
can configure the plan to group by iteration, which would then
separate
the sprint b work items from the sprint c work items.

If you want a plan that only shows work items from sprint b, then
configure the plan to target sprint b, not iteration two.

Cheers,
Geoff

Plans can be configured very differently (task board, work breakdown,
etc., as well as all the custom choices). So teams will sometimes have
more than one plan for a given iteration, differing in how they are
configured.

Cheers,
Geoff

But the way they see the plan is only changed in each user session :/

My examples were incorrect ... I meant to say that there are different
plan types (which have different names, depending on what process
template you are using, but are based on the same set of underlying plan
types).

But I did notice that there appears to be no documentation defining the
different plan types that are available (at least, I couldn't find it).
I've submitted work item 180526 asking for this documentation (if anyone
knows of some, please let me know ... there are a few hints scattered
around, but I couldn't find any comprehensive documentation).

Cheers,
Geoff

On 10/12/2011 3:23 PM, mochomocho wrote:

gmclemmwrote:
Plans can be configured very differently (task board, work breakdown,

etc., as well as all the custom choices). So teams will sometimes
have
more than one plan for a given iteration, differing in how they are

configured.

Cheers,
Geoff

But the way they see the plan is only changed in each user session :/

Hi,

A plan is owned by a process area which could be a project or a team and an iteration. The typical usage is to have one plan per process area and iteration since a plan is nothing but a query which fetches the work items that are associated with these parameters. However it is possible to create multiple plans for the same process area and iteration this means both the plans would fetch the same set of work items. However a user can edit the attached pages for each of those plans to have different content for e.g - you can edit the overview page to have different content. Also the Advanced Options for each the plan are per plan specific.

You can refer to the article: https://jazz.net/library/article/594
It outlines best practices and reveals tips and tricks that come handy while Planning.

Hope this helps.

Geoff, thanks for replying.

So, your suggestion is that I have to make 1 plan for each iteration?

Then why one can make more than one plan per iteration? That's when I get lost.

I'm not quite sure I follow you're scenario, but here are some thoughts
that might be relevant:

If your plan is targeting the second iteration (in the configuration of
the plan), then you will see all work items in the second iteration,
which includes work items from sprint b and sprint c. As I recall, you
can configure the plan to group by iteration, which would then separate
the sprint b work items from the sprint c work items.

If you want a plan that only shows work items from sprint b, then
configure the plan to target sprint b, not iteration two.

Cheers,
Geoff