For all our investment projects we use WOs underneath WBS. Initially we considered to use WBSs only but that does not work for our daily reality because of :
- project Aps projects are very limited (lack necessary grain) and have several bugs. Maintenance (EAM) apps e.g. Maintenance act/plan, manage planning buckets more mature/grain.
- as per design apparently can only be routed to project mgr at project def. we have large multi million/discipline projects with delegated budgetholderships which are defined in WBS hierarchy.
3 questions
- how do others with large multi disciplinairy projects cope with this? Also WOs or still all in on WBSs only? Custom fields with Extensibility?
- we have 3 WBS levels below project def. Is that the max as per design or can this be expanded?
- SE approval routing. Anyone found a way to stick to best practise/clean core but route to delegated budgetholders at WBS level? Splitting project defs we have considered but does not make sense in our view.
Keen to hear other's views from the daily reality and of course @Chris73 's expert views
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.