consideration for changing team structure & category

Your team structure should just represent the current reality.
Changing the team structure shouldn't negatively affect historical data
(what data concerned you in this regard?).

WRT categories, as long as you don't "re-use" a category for a different
category (by renaming it), you shouldn't lose any historical
information. Over time, you can "archive" categories that you no longer
want to use. This hides them from the GUI, but they still are around
for historical reference.

Cheers,
Geoff

On 6/28/2010 10:22 PM, tayaka wrote:

Hi,

My customer would like to change team structure& workitem
category by sprint.

For example,

Sprint1:
feature1 - team1
feature2 - team2

Sprint2:
feature 1 - no use (if possible, archive it)
feature1-1 - team1-1 (team1 devided int team1-1 and team1-2)
feature1-2 - team1-2
feature2 - no use
feature2-1 - team2
feature2-2 - team2

- Team membership is also changed.
(someone move from team1 to team2)

I think if we change team structure& workitem category, it
affects all historical data(such as plans, reports, dashboad) ,
right?
We don't wanna change all historcal data.

How do we change team structure and workitem category, safely?
Is there any consideration or any point to change team structure and
workitem category?

Thank you for your answer.

I think report is ok (all histrical data remain safely).

My concern is about (old) plans.
I think that changing workitem category association affect old plan.


For example,

Sprint1:
Team1 works with "Core" and "App1"

Core - Team1
App1 - Team1

"Team1-Sprint1 backlog" shows workitems associated with "Core" and "App1".

Sprint2:
Team1 works with only "Core"
Team2 works with "App1" (Team1 is divided , sometimes theam devided

Core - Team1
App1 - Team2

"Team1-Sprint1 backlog"(old plans) now shows workitems only associated "Core" ("App1" is disappered)

---

I know that workitem category can be set by each timeline,
but I don't know how to set different workitem category for each iteration.

Is there any way to use different workitem category setting for each itaration
without any influence for old plan?

Your team structure should just represent the current reality.
Changing the team structure shouldn't negatively affect historical data
(what data concerned you in this regard?).

WRT categories, as long as you don't "re-use" a category for a different
category (by renaming it), you shouldn't lose any historical
information. Over time, you can "archive" categories that you no longer
want to use. This hides them from the GUI, but they still are around
for historical reference.

Cheers,
Geoff

On 6/28/2010 10:22 PM, tayaka wrote:

Hi,

My customer would like to change team structure& workitem
category by sprint.

For example,

Sprint1:
feature1 - team1
feature2 - team2

Sprint2:
feature 1 - no use (if possible, archive it)
feature1-1 - team1-1 (team1 devided int team1-1 and team1-2)
feature1-2 - team1-2
feature2 - no use
feature2-1 - team2
feature2-2 - team2

- Team membership is also changed.
(someone move from team1 to team2)

I think if we change team structure& workitem category, it
affects all historical data(such as plans, reports, dashboad) ,
right?
We don't wanna change all historcal data.

How do we change team structure and workitem category, safely?
Is there any consideration or any point to change team structure and
workitem category?

If you want to keep the content of old (non-current) plans to remain
fixed, then I believe you would need to create new categories, rather
than changing the associations of existing categories. In particular,
you would probably want to rename the old category CAT to be CAT_x and
archive it, so it no longer is used, and then create the "new" CAT category.

Anyone else have a different approach to suggest?

Cheers,
Geoff

On 6/30/2010 1:37 AM, tayaka wrote:

Thank you for your answer.

I think report is ok (all histrical data remain safely).

My concern is about (old) plans.
I think that changing workitem category association affect old plan.


For example,

Sprint1:
Team1 works with "Core" and "App1"

Core - Team1
App1 - Team1

"Team1-Sprint1 backlog" shows workitems associated with
"Core" and "App1".

Sprint2:
Team1 works with only "Core"
Team2 works with "App1" (Team1 is divided ,
sometimes theam devided

Core - Team1
App1 - Team2

"Team1-Sprint1 backlog"(old plans) now shows workitems
only associated "Core" ("App1" is disappered)

---

I know that workitem category can be set by each timeline,
but I don't know how to set different workitem category for each
iteration.

Is there any way to use different workitem category setting for each
itaration
without any influence for old plan?

gmclemmwrote:
Your team structure should just represent the current reality.
Changing the team structure shouldn't negatively affect historical
data
(what data concerned you in this regard?).

WRT categories, as long as you don't "re-use" a category
for a different
category (by renaming it), you shouldn't lose any historical
information. Over time, you can "archive" categories that
you no longer
want to use. This hides them from the GUI, but they still are
around
for historical reference.

Cheers,
Geoff

On 6/28/2010 10:22 PM, tayaka wrote:
Hi,

My customer would like to change team structure& workitem
category by sprint.

For example,

Sprint1:
feature1 - team1
feature2 - team2

Sprint2:
feature 1 - no use (if possible, archive it)
feature1-1 - team1-1 (team1 devided int team1-1 and team1-2)
feature1-2 - team1-2
feature2 - no use
feature2-1 - team2
feature2-2 - team2

- Team membership is also changed.
(someone move from team1 to team2)

I think if we change team structure& workitem category, it
affects all historical data(such as plans, reports, dashboad) ,
right?
We don't wanna change all historcal data.

How do we change team structure and workitem category, safely?
Is there any consideration or any point to change team structure
and
workitem category?

Thank you for your answer. I'll try it.

If you want to keep the content of old (non-current) plans to remain
fixed, then I believe you would need to create new categories, rather
than changing the associations of existing categories. In particular,
you would probably want to rename the old category CAT to be CAT_x and
archive it, so it no longer is used, and then create the "new" CAT category.

Anyone else have a different approach to suggest?

Cheers,
Geoff