Vote #63118
未完了Work Breakdown Structure / EVM
0%
説明
I favor the addition of "Work breakdown structure management" to redmine.
WBS is a breakdown of the project's work into smaller pieces.
The project is decomposed in more manageable pieces, an pieces decomposed until they are work packages.
A work package can therefore be:
- assigned to a owner
- estimated
The WBS is therefore a tree where the leaves are Work packages.
For each work package it would be possible to:
- estimate the work required to complete
- assign resources
- assign a red/amber/green status
- assign actual work
- assign actual progress
- assign planned start/end date
- assign actual start/end date
In a way a WBS could be seen as a "feature" of an issue. But we here we lack the hierarchical view of the WBS.
Project network:
The wbs elements could be link to each other whilst defining the sequence for the project (predecessors successors).
To facilitate the creation of the WBS and network I would be great to be able to import information from MS Project (which makes it simple to create such structure).
Using those input, Earned Value report could be generated for the project - at different levels of the WBS.
Using all the data captured in the WBS (planned/start date - planned/spent effort) it is possible to calculate all Earned Value indicators and make a consolidated report at project level.
It would be great to also be able to link issues to WBS items (bug, support, feature).
I can offer some of my time for:
- requirements gathering
- input to UI design and data modelling
- testing
- I think my coding input would be too limited to be of help.
Merci!
journals
Good idea but as a plugin: redmine can't and shouldn't bear all method created on Earth: it'd become an inconsistent thing, rather less intuitive that it's now.
--------------------------------------------------------------------------------
Hy I was wondering if anyone has filled this gap. For us isn't that necessary integration with msproject. It's possible to have a field with the availables "work packages" of the project. Something like the Members settings of the project. I know that we could make a custom field. But the thing is: we want a list field that the list is filled for each project (not a global list). So we can just label it "Work Package".
Vincent, almost everything you asked about work packages could be done with "custom fields". And you could make custom fields availables for every project. I know it doesn't give you the same output (like hierarchical tree view), but it helps.
> For each work package it would be possible to:
> - estimate the work required to complete
> - assign resources
> - assign a red/amber/green status
> - assign actual work
> - assign actual progress
> - assign planned start/end date
> - assign actual start/end date
--------------------------------------------------------------------------------
I think, implementing WBS through issues (like Gantt chart is implemented) is not a very good idea.
Instead I think of creating WBS by writing a simple list in wiki and generating WBS image.
WBS is a high level list of work and it is not exhaustive. So bug fixes doesn't need to be present in WBS.
Another problem that comes with WBS is work identification and a WBS dictionary.
I think, WBS should be created using plain text. Computers now are smart enough to process such structured documents.
--------------------------------------------------------------------------------