Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

RTC Planning: Difference between the accumulated time calculation between the Scrum and Formal projects.

Questions
Tags
Users
Badges
Aradhya K
JAZZ DEVELOPER (1.4k●5●43●45) Jun 02 '12, 12:17 a.m.
I have 3 Questions:
1. what attributes accumulate time in scrum depends on. 
2. Can you please provide business rules for scrum for accumulate time
3. Compare the answer to the 2nd question with bussiness rules for FPM, what is the difference

1

0 votes

1 answer
12,466 views
0 votes

One answer

Permanent link
Aradhya K
JAZZ DEVELOPER (1.4k●5●43●45) Jun 02 '12, 12:59 a.m.
1. what attributes accumulate time in scrum depends on.
The attributes accumulated time in scrum depends on are:
WorkItem.OWNER: The scheduling happens only for the work items that have owners
WorkItem.SEQUENCE_VALUE: The user can arrange the work items in the my work view based on his priorities
WorkItem.RANKING, The Scrum master assigns the ranking while doing the backlog planning this is considered
WorkItem.ESTIMATE, This is calculate the amount of time required.
WorkItem.EFFECTIVE_DURATION: Sometimes the user updates the corrected estimates hence this is required.
WorkItem.RESOLVED and WorkItem.RESOLUTION_DATE: the resolved work items are excluded.
WorkItem.ITEM_TYPE: For the Plan items 
WorkItem.TARGET/planned for : the Iteration to which the work items is targetted for
WorkItem.BLOCKS_WORKITEM: If the work item has the dependence then the successor needs to wait till predessor is commplete.
2. Can you please provide business rules for scrum for accumulate time
3. Compare the answer to the 2nd question with bussiness rules for FPM, what is the difference.
The Major difference lies in the 2 custom attributes that are added for FPM project areas:
1. The Constraint type and 
2. The Constraint Date.
RTC Supports 2 constraint types:
The SNET (Start No Earlier Than) if set and specified then it is used to calculate the start date for the Work.
The FNLT (Finish No Later Than) if set and specified then it is used for plan check and to inform the user that the work item cannot be scheduled before the scheduled dates.

0 votes

Comments
Geoffrey Clemm
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Jun 02 '12, 9:23 a.m.
For sequence value, ranking, item-type, target, and blocks_workitem affect accumulated time, I can see how they would affect scheduling, but how do they affect accumulated time?

1 vote

Aradhya K
JAZZ DEVELOPER Jun 03 '12, 5:48 a.m.
The Accumulated Time is the output of the dates calculated from the Scheduler. Hence the Attributes mentioned will affect the values of Accumulated time as well.

Andrew Codrington
Sep 06 '12, 12:31 p.m.
This is an important question, but I don't think it's fully answered here or in the docs/articles I've found so far. For example, I didn't see Work Allocation mentioned here, but I'm pretty sure it's an input to the math for accumulated time. Is there a good reference article for the agile scheduler's approach to accumulated time? We're using OpenUp in 3.0.1.2 so something relevant to that would be perfect but anything that would help explain how the accumulated time works for non-FPM scenarios would be greatly appreciated.

1 vote

Your answer

Register or log in 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.

Ask a question
Guidelines
FAQ
Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 12,147
× 239

Question asked: Jun 02 '12, 12:17 a.m.

Question was seen: 12,466 times

Last updated: Sep 06 '12, 12:31 p.m.

Confirmation Cancel Confirm