이래서 다들 저처럼 번역 시도하려다 포기하는건가^^

대학전공서적 초등생에게 줘봐야 읽기만하지 그뜻을 모르듯이요~~

또하나 초등생이 의미도 모르고 따라부르는 사랑쪼의 노래처럼요^^

그래도 일단 경험많은 이들의 참여를 이끌어 보려는 의도로 꾸준히 시도는 해 볼랍니다~~

http://jazz.net/forums/viewtopic.php?t=8600

Creating a Product Backlog Plan for new timeline
새 타임라인을 위한 제품 백로그 계획 생성하기?

arnovick :
Hello
I am trying to create a Product Backlog for a new timeline that was created. Once I saved the Product Backlog it did not show me any work items associated with it. I then opened the configure plan for the new Product Backlog to see if I had configured it correctly. The new timeline I had configured it for was not listed, but the main development timeline (marked as the Project Timeline) was. Along with this was an error indicating that the Iteration I had chosen was not part of the Project Timeline. If I change the new timeline the project timeline the plan saves correctly and I can now see all work items.

1)Why can I not create a new plan and associate it with a timeline that is not the project timeline?
2) How does changing the Project Timeline to a new timeline effect the current plans I have already created under the old project timeline?

thank you for your time!

나는 새 타임라인을 위한 제품백로그 생성을 시도 했고요 생성은 되었습니다
여기서 내가 말하는 제품백로그는 작업항목과의 연관을 나타내는건 아닙니다
제가 올바르게 구성했다면 새 제품백로그 구성계획이 열렸을겁니다
내가 구성했던 새 타임라인은 리스트되지 않았고, 메인 개발 타임라인(프로젝트 타임라인처럼 마크된)도 그랬습니다
프로젝트 타임라인의 일부분으로 선택하지 않았던 반복이 에러를 유발한거 같습니다
프로젝트 타임라인 계획을 새 타임라인으로 바꾸고 바르게 저장하면 모든 작업항목을 볼수가 있습니다

1)왜 나는 프로젝트 타임라인이라는것과 연관된 새 계획을 생성할수없는가
2)내가 벌써 생성했던 과거 프로젝트 타임라인이  프로젝트 타임라인에 새 타임라인을 어떻케 바꿔야 효과적인 현재 계획이 되는가?
~아 어렵따~~무모한 도전이구나 ㅜ.ㅜ

-----------------
arnovick :
Hello
If I create a new timeline, do I always have to create new team areas to associate existing work item categories with? It does not look like you can associate a team area with more then one timeline. Why is this?

Thanks for your time once again!
Sue

만일 새 타임라인을 생성하면 새 팀영역에 연관된 작업항목 카테고리가 항상 생기는지?
관련된 팀영역에 하나이상의 타임라인이 있을땐 그렇치 않아보이는데 왜그런가요?
생유 ~~ 이거하나는 퍼펙트하네^^

------------
gmclemm :
Question 1: At any given time, a team area is associated with exactly
one timeline (open the team area editor, and the timeline appears in the
upper right hand corner). The plan for a given team area is limited to
iterations in the timeline of that team area. You can associate a plan
with the project area itself, in which case you can associate that plan
with any iteration in any timeline in that project area.

Question 2: Changing the project timeline has no effect on the current
plans that you have already created under the old project timeline.

Cheers,
Geoff

질문1: 어떤 주어진 시간에, 한 팀영역은 실제적으로 한 타임라인에 연관됩니다
(팀영역 에디터를 열면, 타임라인은 우측상단모서리에 나타납니다)
주어진 팀영역 계획은 팀영역의 타임라인내에 있는 반복에 제한됩니다
한계획은 한 프로젝트영역 그 자체로 연상하셔도 됩니다
,당신이 연관시키려는 프로젝트 영역내의 어떤 타임라인 어떤 반복 계획도

질문2:

~~~ 나도 누구처럼 이미 포기 하고 싶군요^^
 
----------------
gmclemm :
There is a work item requesting that you be able to associate a team
area with more than one timeline: work item 99436.
It is not currently in plan.
Please feel free to indicate your interest by adding a comment to that
work item.

The main objection is that the timeline of a process helps select what
process is to be applied to a work item, so the process would be
ambiguous if a team area could be associated with multiple timelines.
The counter to that objection is that one could select a "process
timeline" which determines the timeline process, and then an arbitrary
number of additional "plan timelines", which allows work items for
multiple timelines to be included in that plan.

Cheers,
Geoff

----------------
gmclemm :
You should be able to set the timeline of a team area in a given project
area with any timeline in that project area.
You should then be able to associate a plan for that team area with any
iteration in the timeline of that team area.

If that is not the case, it would probably be best to submit a work item
so support can work with you to figure out what is going on.

Cheers,
Geoff

------------
PerFlodin :
Hi Geoff!

As you write, it is possible to associate a plan to an iteration. I think it would be useful to associate a plan to a timeline.

Consider this: To create a top level Product Backlog, I would like to include all work items in any way related to a timeline. To accomplish this, I have to create a top level iteration (similar to the default "All Work"), and associate the plan to that iteration. This iteration will extend forever in time, and gives no extra value to me; it is a dummy just to get the plan.

Any reasons it is not possible to associate a plan to a timeline directly?
Or is there another way to do what I want without introducing a dummy "forever"-iteration?

BR,
Per Flodin   

-----------------
rschoon :
Per,

this is "somewhat" possible in RTC 2.0.0.2. Create an iteration with a release planned for in the timeline e.g. call it backlog. This can be used as hook for a plan e.g. the product backlog in SCRUM. There is no need to set dates for that iteration.

See RTC 2.0.0.2 New and Noteworthy.

Ralph

--------------
gmclemm :
I actually did submit a work item a while back requesting that one be
able to associate a team with a timeline. The team responded with the
concern that performance of the planning queries will suffer as ever
more work items are associated with that timeline over time.

So instead, they would like you to create a "backlog" iteration, and
assign all the not yet scheduled work items to that. Then you would
"move" a work item from that backlog iteration to some scheduled
iteration, which avoids the performance problem.

Cheers,
Geoff

-----------------
PerFlodin :
Hi again!
gmclemm wrote:
I actually did submit a work item a while back requesting that one be able to associate a team with a timeline. The team responded with the concern that performance of the planning queries will suffer as ever more work items are associated with that timeline over time.

With my workaround (a top level iteration that lives forever) I think I would get about the same performance problem, right? I mean, this iteration would also get more and more items associated to it.

gmclemm wrote:
So instead, they would like you to create a "backlog" iteration, and assign all the not yet scheduled work items to that. Then you would "move" a work item from that backlog iteration to some scheduled iteration, which avoids the performance problem.

Do you mean I should have this "backlog" iteration not as a parent, but as a sibling to my scheduled iteration(s)?

That is possible, but then I guess I can't see the content of the "backlog" iteration and the "scheduled" iterations in the same plan, can I? I thus lose some of the nice planning overview in RTC. Or?

BR,
Per