OpenUP and Size Estimates
![]()
Anyone else using openup? We have been using OpenUP for a while and I am going to use Jazz/Team Concert to manage an upcoming.
One thing I noticed is missing from the OpenUP template is Size Estimates. Any thoughts on this and how I might customize the process to include this. |
7 answers
![]()
Could you please clarify your request. If you are not going to use RTC,
are you then talking about Open-up in general? Thanks. Kai Jazz Process component team jatsrt wrote: Anyone else using openup? We have been using it for a while and I am |
![]()
Sorry, bad typo, I am using RTC and the OpenUP process.
What I am talking about is the use of Size Estimate in points to help track and plan iterations. |
![]()
Hi,
with the next milestone there will be an additional field in work items to track the time spent to fix a work item. Based on the estimate and time spent field we are planning to provide a velocity report. Dirk Agile Planning Team jatsrt wrote: Sorry, bad typo, I am using RTC and the OpenUP process. |
![]()
I am talking more of a weighted and relative Size estimation, this is something the is used in OpenUP and allows you to seperate raw time from "effort/complexity" of a piece of functionality relative to other pieces.
Example: Pull all strings into a resource file Size 5 (Easy to do) Time Required 2 weeks (a long process) Implement complex algorithm Size 20 (Very complex) Time Required 1 week (we have a really smart algorithm programmer) |
![]()
This is available for the story work item type which is used to capture
requirements (e.g. implement new Web/UI design). The type offers a story point field. A story itself doesn't have an estimate though. The story is decomposed in task, defects, ... which have estimates. The amount of work needed to implement the story is the sum of the estimates of the implementing tasks. In Beta2 the progress of a story is measured in open/close counts. For 1.0 we intend to change this to use the estimate and time spent field. Dirk (Agile Planning Component) jatsrt wrote: I am talking more of a weighted and relative Size estimation, this is |
![]()
Ok, sound the documentation and this looks perfect, I think I need to send the OpenUP guys a suggest they merge their idea of use cases into stories.
|
![]()
Steps are descibed in
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/39355 Dirk Agile Planning Component jatsrt wrote: jatsrt wrote: Is there documentation anywhere for how to add the story type to a |