So you’ve read all the tips and blogs about how to tailor OUM for your project and you’ve figured out what tasks you need. Now you have to put them into a workplan. What do you do? Do you use the traditional activity wbs structure highlighted in the method or do you need something else? The possibilities are endless. Think about how you implement your projects now. Think about what works now and what doesn’t. Consider this blog my Questions to Ask When Organizing Your OUM Workplan.
- Does the traditional OUM activity-work-breakdown structure fit my project?
- Does your project involve more than one custom-off-the-shelf (COTS) product? If so, maybe you want to do this work in partitions. Determine which activities/tasks should be duplicated into each partition.
- Do you need to consider copying sections of your workplan and putting them into iterations for accommodating use case packages?
- Can certain processes be run as “mini projects?” Some processes can almost be run as a side project on their own, for example, Technical Architecture (TA), Performance Management (PT), Documentation (DO), Training (TR), and Organizational Change Management (OCM). If so, it may make more sense to group and track these tasks under a process/activity heading and not space them out into the various phases.
- Do you use one workplan or a master workplan with individual plans that report or roll up into the master? This might work if you have Team Leaders that manage specific pieces of work. Use a placeholder activity/task in the master workplan and the detail can be managed in a sub workplan.
The bottom line is, be creative. Build your workplan(s) to suit your project. As you start another project, don’t be afraid to change something that isn’t working. Finally, share your workplans and experiences.