Hi to all,
I'm working in PMO team and I'm helping a colleague to re-organize & improve usability of its plan.
Now he is not able to use properly the plan....The assignements to resource are made...but
the schedule is raw (on monthly
base only to check overallocation).
The dimension of the project:
- IT software product development
- +/- 40 resources
- +/- 3000 manday (effort)
- monthly release to multiple customers
Now the plan, IMHO, as too much activities (one for each requirement, totally 750 activities).
I would suggest him a complete refactoring of the plan because those issue.
Issue:
- Often they miss requirements in release (low quality!).
- Requirements changes too much quickly and he tends to insert all customer and market request and needs.
- Often the estimate for development are very inaccurate because the missing of functional analysis.
- Links between activites are impossible to manage (too much and not monitored).
- He don't want change WBS because he's afraid of loose single requirement because they don't track properly requirements
request.
The wbs is muddled...Often the exercise is to move from one release to others the single requirements (activities) to see
effects of load over resources.
I would propose refactoring:
- focus WBS on RELEASE and not on macro-req (see attach).
- collapse micro-req into bigger ones (see attach).- put real and useful link between activities
- try to convince him that changes requests has to be approved and estimated.
In attach the as-is and my proposal of to-be (for wbs). Please do not consider detail of link...are missing many links.
Coud you suggest for pitfall, experiences, well-know issues?
Have you some similar experiences?
