Project Workplan Users Guide

OUM
PROJECT WORKPLAN USER’S GUIDE
September, 2016
Project Workplan User’s Guide
Preface
The OUM Project Workplan User’s Guide provides detailed instructions for using the OUM Microsoft Project Workplan
template.
This user’s guide assumes the user has a solid understanding of key OUM terms and concepts from taking Level 1,
Level 2 and Level 3 OUM training.
Audience
This Project Workplan User’s Guide is written for:
 project managers
 project team members
 consultants
How this Guide Is Organized
This guide consists of the following sections:
Section 1 provides overview of OUM’s iterative and incremental planning process as well as an
overview of the OUM Microsoft Project Workplan template.
Section 2 provides steps for copying the Project Workplan template in order to create your
project-specific Project Workplan.
Section 3 provides steps for entering initial work effort estimates into your project-specific
Project Workplan.
Section 4 provides guidance for tailoring your project-specific Project Workplan for your project.
Section 5 provides guidance for removing out of scope activities and tasks from your project-
specific Project Workplan.
Section 6 describes steps for building an Implementation Plan (phase and activity level).
Section 7 provides guidance for extending the Project Workplan to support detailed planning
and iteration planning.
Section 8 describes the Project Workplan views used for tracking project progress.
Section 9 describes the Project Workplan reporting views used to communicate project
progress.
Section 10 describes the Project Workplan views used to maintain the Project Workplan
template.
Section 11 provides a quick index of all the OUM-specific Microsoft Project views.
Section 12 provides a quick index of OUM View Column Headings and their associated
Microsoft Project Fields along with a brief description as well as a matrix indicating on which
OUM View they are included.
How to Use this Guide
The Project Workplan User’s Guide should be used in conjunction with OUM guidance, and specifically the following:
 OUM Project Workplan template
Related Publications
This guide discusses how to use the Project Workplan template to prepare a project-specific workplan. Refer to OUM
for additional helpful guidance. In particular, consider the following:
 OUM WM.010 and WM.030 Task Overviews
 Planning a Project using OUM – An Iterative and Incremental Approach
File Ref: Document1 Preface i

 Tailoring OUM for Your Project

Your Comments are Welcome
Oracle Global Methods values and appreciates your comments as an OUM practitioner and user of this guide. As we
write, revise and evaluate our documentation, your comments are the most valuable input we receive. If you would
like to contact us regarding comments on this or other OUM guidelines, please use the following email address:
ominfo@us.oracle.com
0H
File Ref: Document1 Preface ii

Contents
1 OUM Project Planning Process/Component Overview .......................................... 1

1.1 Overview of OUM Iterative and Incremental Planning Process ................................... 1
1.2 OUM Project Workplan Template ................................................................................. 2
2 Copy the Project Workplan Template ....................................................................... 9
3 Load Estimated Effort into the Project Workplan ................................................. 10
4 Tailor the Project Workplan for Your Project ........................................................ 11
5 Remove Out Of Scope activities and tasks from the Workplan .......................... 13
6 Use the Project Workplan for High-Level Implementation Planning .................. 15
7 Use the Project Workplan for Detail and Iteration Planning ................................ 16
8 Use the Project Workplan for Tracking Project Progress .................................... 18
9 Use the Project Workplan for Progress Reporting ............................................... 19
10 Maintain the Project Workplan Template ............................................................... 20
11 OUM-Specific Microsoft Project View Descriptions ............................................. 21
12 COLUMN-Field-View Reference .............................................................................. 23
File Ref: Document1 Contents iii

1 OUM Project Planning Process/Component Overview

This section provides a high-level overview of the OUM project planning process and the various key components:
 OUM Iterative and Incremental Planning Process Overview
 Microsoft OUM Project Workplan (MPP) Template
1.1 Overview of OUM Iterative and Incremental Planning

Process
OUM 6.0 provides full implementation lifecycle planning support with a highly integrated and configurable Microsoft®
Office Project Project Workplan template. The OUM Project Workplan (OUM_WBS_Project_Workplan.mpp) is a
template. Do not update the template. Always create a project-specific Project Workplan before applying any
updates to the Project Workplan template.
The OUM Iterative and Incremental Planning Process embraces one of the key principles of iterative and incremental
planning as defined in the Unified Process (UP) and OUM…
“Plan only for that which you know.”
The reasoning behind this principle is that detailed planning for more than 6 months into a project, or more than one
iteration of an OUM phase produces results that are more hypothetical than practical, and therefore, are of little value
to the project’s successful, on time completion.
OUM breaks project planning into two distinct planning cycles – Implementation Planning, and Iteration Planning.
Implementation Planning is all about supporting the bid and initial project planning needs of a project, which
includes staff planning. This is high-level project and staff planning that is sufficient for estimating and enabling the
detailed planning which will occur next.
Iteration Planning provides the detailed ongoing project planning support for implementing the project from one
iteration to the next iteration within each phase of the project.
File Ref: Document1 OUM Project Planning Process/Component Overview

1
Support of Bid and Initial Planning Process

Bid and initial planning of a project begins with estimating the effort of a project, and then developing a preliminary
staff plan. Experience has shown that the best-practice approach for staff planning is to leverage a tool that assists
with the resource leveling based on resource scheduling functionality found in project planning tools such as Microsoft
Project.
A fully staffed Implementation Plan provides important high-level artifacts, such as:
1. Estimated effort at a summary level (activity level in OUM)
2. Dependencies between summary/high-level work groupings (OUM activities)
3. Number of Resources and level/cost of resources required for project
The three above artifacts enable a bid/project team to estimate a date range for completing the project, as well as
provide a cost estimate range.
Suggestion: It is best to use ranges whenever possible for project duration and
project cost during bid and initial planning of a project. These date ranges can then be
narrowed to a refined cost/delivery-date prior to executing each iteration.
The OUM Project Workplan template provides a work breakdown structure (WBS) that enables a bid/planning team to
focus on high-level/summary work groupings (OUM Activities), while also providing ability to perform detailed, task-
level planning later.
The Project Workplan supports the Bid and Initial Planning Process by enabling easy maintenance of estimated effort
through the use of an Estimating Results Transfer view. Refer to section 3, Load Estimated Effort into the Project
Workplan.
1.2 OUM Project Workplan Template

This section provides a high-level description of the Project Workplan template terms and components that are
leveraged in later sections of this document.
Remember, the OUM Project Workplan (OUM_WBS_Project_Workplan.mpp) is a template. Do not update the
template. Always create a project-specific Project Workplan before applying any updates to the Project Workplan
template.
The Project Workplan template can be best described in the following manner:

2
 Common Terms and Definitions

 Structure Levels
 Use of Microsoft Project Text and Flag Fields
 OUM-Specific Microsoft Project Views
Common Terms and Definitions when Using OUM Project Workplan Template
The following are some common terms and definitions you need to know in order to effectively utilize the OUM Project
Workplan template.
Attention: The detailed descriptions and associated use of them are defined in the
OUM Method Guidance, as well as in the OUM Level 1 through Level 3 training.
Term Definition Usage Assumption

Partition Partitions split the functionality into  Typically, they are predefined for a product or consulting
smaller pieces (or subsystems) service offering.
that may be implemented in  Partitions can cross phase boundaries.
parallel or serially depending on  Partitions are commonly created to group one or more
project-specific factors. business process flows that allow for iteration objectives
to be achieved within each phase. They break functional
Look for the following when requirements into manageable “chunks” of work.
determining partitions:  Partitions can be defined prior to a project beginning, or
 High cohesion within a during the project when/if necessary.
partition  Four evaluation perspectives are applied when
 Low coupling between determining partitions (Risk, Complexity, Priority, and
partitions Dependencies).
Iteration An iteration is a distinct set of  The number of iterations per phase is initially calculated
activities conducted according to a during Bid and Estimating and refined prior to executing
devoted (iteration) plan and each phase. See section 5 for guidance on calculating #
evaluation criteria that results in a of iterations initially.
release, either internal or external.  Iterations are unique to each phase.
 Each iteration has a unique milestone with a distinct set
of iteration objectives.
 Each partition defined in a Project Workplan may have
its own set of defined iterations.
Activity Activities group related tasks by  OUM has a defined set of activities that are used for
topic, dependencies, data, estimating, as well as standard, method based task roll-
common skills/roles or work ups.
products.  Project-specific activities may be created to provide
project-specific task roll-ups. In many cases, these
product-specific roll-ups are predefined.
Iteration Groups Iteration groups are groupings of  They can cross phase boundaries.
functional requirements (perhaps  They are prioritized and grouped by four evaluation
in the form of use cases, but not perspectives (Risk, Complexity, Priority, and
necessarily use cases) and the Dependencies).
associated OUM tasks required to  Typically, they are defined at the end of the Inception
process them. phase and refined at the end of use case modeling for
each iteration in the Elaboration phase.

3
Structure Levels
The OUM Project Workplan adds an activity “summary” task under each activity. In Microsoft Project, effort can only
be assigned at the lowest “child” level of the hierarchy, or at the task level. The activity summary task allows you to
manage effort at the activity level, but still see the tasks included for an activity.
Activity summary tasks have the same name as the activity and use the same OUM ID with .TSK added to the end.
Refer to section 3, Load Estimated Effort into the Project Workplan for more details on the activity summary tasks.

4
Use of Microsoft Project Text and Flag Fields

The OUM Project Workplan template leverages many of Microsoft Project’s text and flag fields. How these text and
flag fields have been used can easily be seen by using the “Notes:” icon from the first row of most views in the
Project Workplan.
Double-click on the icon (Indicators) column. The Summary Task Information window pops up. Select the
Notes tab and you can see the Project Flag and Text Field Assignments used in the OUM Project Workplan.

5
The following is a complete listing of the Project Flag and Text Field Assignments:
Project Flag Field Assignments within OUM MPP Template

Flag 1 = Identifies resulting work product as a deliverable (Yes=key deliverable / No- if not)
Flag 2 = Identifies rows in plan to display on 13_OUM_Project_Summary view
Flag 3 = Unassigned
Flag 4 = Identifies OUM Method activity rows (different from project defined activity rows)
Flag 5 = Unassigned
Flag 6 = Identifies rows (work product) that are designated for consolidating results. Used for
14_OUM_Project_Consolidated_Work_Products view
Flag 7 = Identifies rows for transferring or loading estimated effort. Used for 01_OUM_Est_Results_XFER view
Flag 8 = Used for filtering rows to be displayed in plan: Value of "No" equals row should not be filtered, and thus displayed in
plan (leveraged by many OUM views in plan)
Flag 9 = Unassigned
Flag 10 = Unassigned
Flag 11 = Predefined row filtering values for Requirements-Driven App Implementation view
Flag 12 = Predefined row filtering values for Solution-Driven App Implementation view
Flag 13 = Predefined row filtering values for Software Upgrade view
Flag 14 = Predefined row filtering values for Technology Full Lifecycle view
Flag 15 = Predefined row filtering values for Business Intelligence view
Flag 16 = Predefined row filtering values for WebCenter view
Flag 17 = Predefined row filtering values for Core Workflow view
Flag 18 = Task-Level Activity Placeholder Filtering
Flag 19 = Predefined row filtering values for displaying all rows in plan
Flag 20 = Unassigned
Project Text Field Assignments within OUM MPP Template

Text 1 = Name of resulting work product
Text 2 = Estimating Channel Assignment %'s
Text 3 = Unassigned
Text 4 = Unassigned
Text 5 = Unassigned
Text 6 = Process ID
Text 7 = Process Name
Text 8 = Activity ID
Text 9 = Partition ID
Text 10 = Unassigned
Text 11 = Workshop ID
Text 12 = Iteration ID
Text 13 = Iteration Group ID
Text 14 = Activity Name
Text 15 = Task Notes
Text 22 = Phase ID
Text 23 = Phase Name
Text 24 = Estimating Role Assignments
Text 25 = Method Role Assignments
Text 26 = Approved By
Project Number Field Assignments within OUM MPP Template

Number 1 = Reserved
Number 2 = Reserved
Number 3 = Estimated # of phase iterations for plan (field for storing initial estimates)

6
OUM-Specific Microsoft Project Views

The OUM Project Workplan template has a number of OUM-specific Microsoft Project views that support the full
implementation lifecycle of a project in an agile, iterative and incremental manner. In addition, other OUM-specific
Microsoft Project views enable filtering of the Project Workplan for OUM views (for example, Requirements-Driven
Application Implementation, WebCenter, etc.) and provide flexibility to the project manager for adjusting columns
within a Microsoft Project view without impacting other Microsoft Project views. Ultimately, the OUM-Specific
Microsoft Project views enable flexibility and scalability of the Project Workplan.
Warning: The OUM MPP views require ALL subtasks for a view be expanded
(displayed); otherwise MPP rows may not be displayed when filter is applied. Do not
use the MPP subtask filtering option, as it will create the possibility of unknown results.
The OUM-specific Microsoft Project views are built using the Microsoft Project text and flag driven
filtering approach in order to make a large, complex Project Workplan easier to navigate and practical
for day-to-day use on a project.

7
The following picture shows the current OUM-specific Microsoft Project views that have been defined
in the OUM Project Workplan template:
Refer to section 10 for a description of each view.

8
2 Copy the Project Workplan Template

The OUM Project Workplan (OUM_WBS_Project_Workplan.mpp) is a template. Do not update the template. Always
create a project-specific Project Workplan before applying any updates to the Project Workplan template.
Step 1: Open the Project Workplan template (OUM_WBS_Project_Workplan.mpp) and use the “Save As” option to
save the file with your project name.
Step 2: Close the workplan.
Step 3: Open your project-specific Project Workplan and begin to customize it to fit your project.
Warning: The OUM MPP views require ALL subtasks for a view be expanded
(displayed); otherwise MPP rows may not be displayed when filter is applied. Do not
use the MPP subtask filtering option, as it will create the possibility of unknown results.
Make sure you have not collapsed items before applying any filtering or tailoring.
When in doubt, use the Show All Subtasks.
File Ref: Document1 Copy the Project Workplan Template 9

3 Load Estimated Effort into the Project Workplan

OUM follows the success-proven industry practice of not initially estimating a project at a too granular or detailed
project level. It has been consistently demonstrated that estimating a project at a too granular/detailed level does not
produce more accurate estimating results, and in fact, leaves the estimator with a false sense of accuracy. OUM
follows this approach by rolling-up tasks into predefined activity groupings.
Support of Bid and Initial Planning Process
Bid and initial planning of a project begins with estimating the effort of a project, and then developing a preliminary
staff plan. Experience has shown that the best-practice approach for staff planning is to leverage a tool, such as
Microsoft Project, that assists with the resource leveling based on a resource scheduling functionality.
Manual Update of Estimated Work Effort
You can manually enter the estimated work effort into the Project Workplan.
If you plan on managing effort at the activity level, but want to show the underlying tasks for each activity, enter the
estimated work effort for each activity in the Est. Work column of the 01_OUM_Est_Results_XER view.
Effort entered in the Est. Work column shows up in the activity summary task under the activity. The activity summary
task allows you to manage the effort at the activity level, but still see the in-scope tasks included in the activity.
Remember, activity summary tasks have the same name as the activity and use the same OUM ID with .TSK added
to the end.
If you know you will not be managing effort at the activity level, you can choose not to use this view to enter your
effort. You can remove all the activity summary task rows, by going to the 02_OUM_Set_Project_Filter view and
copying and pasting the Task-Level Activity Placeholder Filtering column into the Out of Scope for Project column.
However, you can’t then use one of the other filtering columns. If you want to use one of the other filtering columns,
copy and paste the desired filtering column and then use the Task-Level Activity Placeholder Filtering column as a
guide to manually change the correct rows to Yes (Out of Scope).
File Ref: Document1 Load Estimated Effort into the Project Workplan 10
4 Tailor the Project Workplan for Your Project

This section provide guidance on how to initially tailor the project plan to display OUM method components that are
relevant to the standard OUM view you are using.
The OUM Method template currently supports the following filters:
 Requirements-Driven Application Implementation
 Solution-Driven Application Implementation
 Software Upgrade
 Technology Full Lifecycle
 Business Intelligence (BI)
 WebCenter
 Core Workflow
 Task-Level Activity Placeholder (Used to remove activity summary tasks as explained in Section
3)
 All Rows
Perform the following steps to tailor your Project Workplan
Step 1: Navigate to the 02_OUM_Set_Project_Filter view. This view allows you to narrow the scope of OUM tasks
based on the above listed OUM views.
Step 2: Determine which of the 9 row filters (shown above) is the best match for your project.
Step 3: Select the heading cell for the chosen column. Note that the entire column becomes highlighted. Press
Ctrl+C to copy the column to the clipboard.
Step 4: Select the heading cell for the “Out of Scope for Project?” column. Press Ctrl+V to paste the previously
copied column. Now the contents of the “Out of Scope for Project?” column should be the same as the copied
column.
Attention: Remember, rows with No are INCLUDED in your project. Rows with Yes
(that is, Yes, this component is OUT OF SCOPE) are EXCLUDED from your project.
Step 5: You can now further tailor the contents in any row in the “Project Filtered Row (Out of Scope)” column as
required for your project. You can exclude an activity or task from your workplan by changing a No to Yes or include
any task by changing o Yes to No in this column.
Review the list of OUM activities and tasks that have a No and change any that are not needed to Yes. If you notice
any activities or tasks that are excluded and you need them, change the Yes to No. Remember, you can’t have an
activity excluded (Yes) and have any tasks belonging to that activity included (No).
For additional guidance on tailoring your project, you may want to look at the following OUM resources:
 Planning a Project using OUM white paper and Tailoring OUM for Your Project white paper –
These paper can be accessed by using the Resources link in the header of most OUM pages.
Once on the Resources page, go to the Supplemental Guidance link. Once on the Supplemental
Guidance page, look for the link to White Papers in the right column of the Index table towards
the button. Click on the White Papers link to navigate to the list of available white papers.
 WM.010 Develop Baseline Project Workplan Task Overview
If you start with the Core Workflow:
If none of the above filters fit your project, consider starting with the Core Workflow and make adjustments to the Out
of Scope for Project? column it based on the following questions.
File Ref: Document1 Tailor the Project Workplan for Your Project 11
1. Do you need additional Business Requirements (RD) and Requirements Analysis (RA) tasks? If
so, add them.
2. Are you implementing a custom-off-the-shelf (COTS) product? If yes, review the Mapping and
Configuration (MC) process and add any tasks not already included in the Core Workflow. If no,
remove the Configuration Sub-Flow tasks.
3. Is there custom work? If yes, add additional Analysis (AN), Design (DS), Implementation (IM)
and Testing (TE) tasks, as appropriate. If no, you may be able to remove the tasks in the Custom
Development Sub-Flow.
4. What are the Technical Architecture (TA) requirements? Add TA tasks as appropriate.
5. Will there be any data conversion? Add any Data Acquisition and Conversion (CV) tasks as
appropriate.
6. Are there any Performance Management (PT) requirements? Add PT tasks as appropriate.
7. What are the Documentation (DO) requirements? Add DO tasks as appropriate.
8. What are the Organizational Change Management (OCM) requirements? Add OCM tasks as
appropriate.
9. What are the Training (TR) requirements? Add TR tasks as appropriate.
10. What are the Transition (TS) requirements? Add TS tasks as appropriate.
11. What are the Operations and Support (PS) requirements? Add PS tasks as appropriate.
Step 6: Once you have finished tailoring your workplan, you can leave the 02_OUM_Set_Project_Filter view and use
the 03_OUM_Plan_Filtered view to get a filtered look at your Project Workplan. Only those rows that are included
(No) show up in this view. At this point, you do not need to go back to the 02_OUM_Set_Project_Filter view unless
you wish to include an activity or task that you have excluded. If you want to exclude an activity or task, you can do
that from the 03_OUM_Plan_Filtered view by changing the No to Yes. However, you will not see the task excluded
until you exit this view and come back to it.
Warning: The estimated “start” and “finish” dates are only valid after project resources
have been assigned to activities and resource leveling has been completed.
File Ref: Document1 Tailor the Project Workplan for Your Project 12
5 Remove Out Of Scope activities and tasks from the

Workplan
Once you have completed tailoring your project-specific Project Workplan, you need to remove all out of scope
activities and tasks so that they don’t cause problems as you use the workplan.
Even though the workplan has “filtered” the in scope and out of scope tasks, certain manipulations of the workplan
can result in out of scope activities and tasks inadvertently showing up (for example, expanding and collapsing
specific sections).
To prevent this happening, once you have determined all tasks that are out of scope and marked them as such by
placing “Yes” in the Out of Scope for Project? Column, use the following OUM view to review all out of scope tasks
and activities:
 17_OUM_Show_Out_Of_Scope_Rows
This OUM view shows all tasks and activities that you have marked as out of scope and gives you an opportunity to
review and then delete them permanently from your workplan. Make sure that none of these activities (or tasks) has
any effort associated with them. If effort is associated with any of the out of scope activities or tasks and you delete
the activity or task, the effort will be lost. If you find effort, determine if it should be transferred elsewhere, is showing
up in error, or if the activity or task should be changed to in scope by placing a “No” in the Out of Scope for Project?
Column.
The following example shows the 17_OUM_Show_Out_Of_Scope_Rows. Note the out of scope rows that show
Effort. These rows need to be either changed to No (In Scope) or the effort needs to be moved to another activity.
You can delete activities and tasks individually or all at once. If you delete a summary level row, all associated
“children: rows will also be deleted. If you choose to delete all out of scope activities and tasks listed on this view,
place the cursor in the first square of the view and press delete.
File Ref: Document1 Remove Out Of Scope activities and tasks from the
Workplan 13
Warning: Once you have deleted any activities or tasks, you cannot use
02_OUM_Set_Project_Filter view to retrieve the deleted activities or tasks.
Refer back to section 3, Load Estimated Effort into the Workplan, to recall information on managing effort at the
activity or task level and removing activity summary tasks.
Now you can continue tailor the workplan by adding partitions, iterations, workshops, etc.
File Ref: Document1 Remove Out Of Scope activities and tasks from the
Workplan 14
6 Use the Project Workplan for High-Level Implementation

Planning
The following OUM views are used for implementation planning:
 04_OUM_Phase_Level_Filtered
 05_OUM_Activity_Level_Filtered
Remember, OUM recommends a layered approach to planning. The first layer is the Implementation Plan. The
Implementation Plan is a brief, coarse-grained outline for the project. The objectives for the project are reflected in the
Implementation Plan. The main purpose of the Implementation Plan is to provide a roadmap for achieving the
project’s goals, along with an estimate of the number iterations needed for each phase as well as the purpose of each
iteration.
Attention: It is important to stay at a broad or high-level of planning during the bid and
estimating cycle. Only display or plan detail where knowledge exists.
Once again, for additional guidance on implementation planning and Implementation Plans, you may want to look at
the following OUM resources:
 OUM Manage view, specifically
o Planning a Project using OUM (located in the Key Components, Supplemental
Guidance section)
 WM.010 Develop Baseline Project Workplan Task Overview
o Determining the Number of Iterations technique
The Determining the Number of Iterations technique can be found in the Techniques section of the WM.010 Task
Overview. This technique is helpful when estimating the number of iterations for each phase.
04_OUM_Phase_Level_Filtered
This view gives the bid estimating team and the customer an activity-summarized view of the estimated work effort at
an activity level for each phase
05_OUM_Activity_Level_Filtered
This view gives the bid estimating team and the customer an activity-summarized view of the estimated work effort at
an activity level for each phase.
It is important to note that estimated work (effort) loaded in 01_OUM_Est_Results_XFER was done at the activity
level (same level displayed in this view).
This view also provides the ability for the bid and estimating team to leverage Microsoft Project’s scheduling
functionality to perform high-level staff planning.
Warning: The estimated start and finish dates are only valid after project resources
Warning: Predecessor Dependencies for all activities must be defined in order for the
MS Project scheduling functionality to correctly estimate the correct “Est. Start Date”,
and “Est. Finish Date.”
File Ref: Document1 Use the Project Workplan for High-Level

Implementation Planning 15
7 Use the Project Workplan for Detail and Iteration Planning

Now that the high-level implementation planning has been done, you need to further customize and tailor the Project
Workplan to address project specific requirements.
The 06_OUM_Project_Planning view supports the project implementation/delivery team. It is the primary view for
applying detail tailoring to the plan for the project and supports the ongoing maintenance of the project plan.
The 06_OUM_Project_Planning view allows you to see the workplan in its entirety and apply any additional tailoring.
In addition to including or excluding OUM components, you may also want to add additional iterations of tasks or
entire activities. To add additional iterations of tasks or activities, simply copy and paste additional components or
groups of components into your workplan.
In OUM’s layered approach to planning, the second layer is the Iteration Plan. The Iteration Plan represents the
lowest and most detailed layer of planning. An individual Iteration Plan will be created for each iteration in the project.
The current Iteration Plan focuses on how an incremental set of objectives and/or functionality will be delivered within
the framework of the project. The main purpose of the Iteration Plan is to lay out how the team will achieve the stated
objectives for the given iteration.
Once you have established the Implementation Plan (usually during Project Start Up), you can start on the initial
Iteration Plan (or the detailed plan if iterations are not being used). Towards the end of the first iteration, the current
Iteration Plan is used to create the Iteration Plan for the upcoming iteration, and so on. Since the initial Iteration Plan
most likely is for the first (and possibly only) iteration of the Inception phase, which will be what you will concentrate
on for the first Iteration Plan.
Iterations
Once you determine what you will include in the first iteration, assign a common iteration ID to those activities and
tasks (e.g., INC1 for Inception, Iteration 1 or if the Inception phase will only have one iteration, you may not need to
use the ID until Elaboration).
Iteration planning for the next iteration of a project typically occurs at the end of the current iteration.
You may need to copy and paste groups of tasks that need to be repeated for subsequent iterations. Assign the
subsequent iteration a common iteration ID and assign it to all the tasks within the iteration.
Partitions
Partitions are optional and your project may not need partitions. In addition, you may not be ready to assign your
partitions in the initial iteration and you may wish to do it in a later Iteration Plan. For example, it is not uncommon for
a project team to define or refine the project partitions at the end of the Inception phase, and prior to starting the
Elaboration phase.
If your project is using partitions, identify the groups of activities and tasks that need to be repeated for each partition.
Copy and paste these groups of tasks, one for each partition and assign a common partition ID for all those tasks
within each partition.
Workshops
Workshops are optional and your project may not need workshops. In addition, you may not need workshops in every
iteration.
If your project is using workshops for the current iteration for which you are planning, identify the groups of activities
and tasks that need to be repeated for each workshop. Assign a workshop ID to each workshop and assign it to the
groups of tasks that make up that workshop. If there are multiple workshops that will use the same tasks, copy and
paste these groups of tasks, one for each workshop and assign a common workshop ID for all those tasks within each
workshop.
Iteration Groups
Iteration groups are specific to custom development and are usually assigned as part of use case modeling and are
not required in every iteration.
File Ref: Document1 Use the Project Workplan for Detail and Iteration
Planning 16
If your project is using iteration groups for the current iteration for which you are planning, identify the groups of
activities and tasks that need to be repeated for each iteration group. Copy and paste these groups of tasks, one for
each iteration group and assign a common iteration group ID for all those tasks within each iteration group.
File Ref: Document1 Use the Project Workplan for Detail and Iteration
Planning 17
8 Use the Project Workplan for Tracking Project Progress

The following views allow you to track progress from different perspectives:
 07_OUM_Project_Partitions - This view gives the project managers and project team leads the
ability to track progress and view the plan from a project partition(s) perspective.
 08_OUM_Project_Activities - This view gives the project managers and project team leads the
ability to track progress and view the plan from a project-specific custom activities viewpoint.
 09_OUM_Project_Iterations - This view gives the project managers and project team leads the
ability to track progress and view the plan from an iteration(s) perspective.
 10_OUM_Project_Iteration_Groups - This view gives the project manager and project team leads
the ability to track progress and view the plan from an iteration group (s) perspective.
 11_OUM_Project_Workshops - This view gives the project manager and project team leads the
ability to track progress and view the plan from a workshop(s) perspective.
 12_OUM_Activity_Work_Allocation - This view gives the project manager and project team leads
the ability to track progress and view the plan from the perspective of a specific activity. This is
helpful when an activity has been split across partitions, workshops, iterations, iteration groups,
etc. It brings all instances of the activity together in one view.
These views simply show you all the rows that contain a value in the respective columns for each view, for example
the 11_OUM_Project_Workshops view shows you all rows that contain a Workshop ID.
Tip: Inside any of these views, consider right clicking in the appropriate column (for example, Workshop ID column)
and using the Sort by… option to sort the included activities/tasks by differently (for example, by Workshop ID).
File Ref: Document1 Use the Project Workplan for Tracking Project Progress
18
9 Use the Project Workplan for Progress Reporting

The following views are used for reporting project progress:
13_OUM_Project_Summary View
This view gives the project manager and project team leads the ability to report on the project progress at a
customized, summarized level. The project manager can choose any set of rows in the Project Workplan on which
ongoing reporting is appropriate for the project. Having a customizable reporting view without impacting other
tracking views minimizes the ongoing reporting effort for project. Rows are displayed in this view when the value of
the “Summary Row Flag” is set to “Yes”.
Warning: The estimated “start” and “finish” dates are only valid after project resources
14_OUM_Project_Consolidated_Work_Products View
This view gives the project manager and project team leads the ability to view and report on project progress by
consolidated work products (CWPs) defined for the project. The project manager can define which consolidated work
products to include in this view by setting the “Consolidate Flag” to “Yes”. This view can be very important if a project
is being managed using the consolidated work product delivery approach, and even more so, if the statement of work
or contract references the CWPs.
15_OUM_Project_Deliverables View
This view gives the project manager and project team leads the ability to view and report project progress by the
deliverables defined for the project. The project manager can define which work products are considered
Deliverables for the project by simply setting the “Deliverable Flag” to “Yes”. This view provides easy ongoing
customer reporting.
16_OUM_Project_Tasks_By_Process View
This view gives the project managers, project team leads, and team members the ability to view the planned work by
OUM process. This view leverages the “Process ID” column that has been pre-assigned to all rows within the plan to
a specific OUM process (e.g., “TA”). This view gives a unique filtering aspect to the plan that allows a team resource
to view the plan for a specific process. This capability is even more important when resource skills center on specific
project processes.
File Ref: Document1 Use the Project Workplan for Progress Reporting 19
10 Maintain the Project Workplan Template

The following views are used for maintaining the Project Workplan template:
 00_OUM_All
 18_OUM_View_Maintenance
These views are used to maintain the Project Workplan template and should generally not be adjusted except by the
Global Methods team.
File Ref: Document1 Maintain the Project Workplan Template 20

11 OUM-Specific Microsoft Project View Descriptions

This section provides a brief overview of all the OUM-specific Microsoft Project views.
View Supports Brief Description
00_OUM_All Bid and Estimating This view allows the entire project team to view all rows
in the plan without any filtering.
Initial Planning
This is an important view as it enables you to bring
Project Implementation previously “Out of Scope” rows back into scope as well
as to view rows that have been excluded from the
Delivery project.
01_OUM_Est_Results_XFER Bid and Estimating This view allows estimated effort to be entered in the
OUM Project Workplan at an activity level by phase.
Initial Planning
02_OUM_Set_Project_Filter Bid and Estimating Enables the user to follow the “build-up” versus
“tailoring down” philosophy of using OUM by narrowing
Scope the scope of the OUM components based on the major
OUM views. You can start with several OUM views,
Initial Planning including the Implement Core Workflow and then
further and build up (or tailor) the Project Workplan as
recommended in OUM training.
Once you have selected a starting view (for example,

Requirements-Driven Application Implementation,
WebCenter, etc.) and applied it, you can further tailor
the workplan using this view, by individually changing
the value in the Project-Filtered Row (Out of Scope)
column.
03_OUM_Plan_Filtered Scope This view shows all rows that contained ‘No” in the Out
of Scope for Project? column. You will NOT see any
Initial Planning rows that contain a ‘Yes’ in this column. If you want to
see which rows are missing, use the 00_OUM_All or
Project Implementation the 02_OUM_Set_Project_Filter views. You can
change a ‘No’ value to a ‘Yes’ on this view. Once you
Delivery leave and come back, the row will not display.
04_OUM_Phase_Level_Filtered Bid and Estimating This view gives the bid estimating team and the
customer a phase-summarized view of the estimated
Initial Planning work effort.
05_OUM_Activity_Level_Filtered Bid and Estimating This view gives the bid estimating team and the
customer an activity-summarized view of the estimated
Initial Planning work effort at an activity level for each phase.
06_OUM_Project_Planning Initial Planning This view gives the management/leads for a project the
ability to further customize and tailor the Project
Project Implementation Workplan to address project specific requirements.
Delivery It is the primary view for applying specific tailoring to

the plan for the project and supports the ongoing
maintenance of the project plan.
07_OUM_Project_Partitions Initial Planning This view gives the project managers and project team
leads the ability to track progress and view the plan
Project Implementation from a project partition(s) perspective.
Delivery
08_OUM_Project_Activities Initial Planning This view gives the project managers and project team
Project Implementation from a project-specific custom activities viewpoint.
Delivery
09_OUM_Project_Iterations Initial Planning This view gives the project managers and project team
Project Implementation from an iteration(s) perspective.
Delivery
File Ref: Document1 OUM-Specific Microsoft Project View Descriptions 21

View Supports Brief Description

10_OUM_Project_Iteration_Groups Initial Planning This view gives the project manager and project team
Project Implementation from an iteration group (s) perspective.
Delivery
11_OUM_Project_Workshops Initial Planning This view gives the project manager and project team
Project Implementation from a workshop(s) perspective.
Delivery
12_OUM_Activity_Work_Allocation Project Implementation This view gives the project manager and project team
Delivery from the perspective of a specific activity. This is
helpful when an activity has been split across partitions,
iterations, iteration groups, etc.
13_OUM_Project_Summary Project Implementation This view gives the project manager and project team
leads the ability to report on the project progress at a
Delivery customized, summarized level. The project manager
can choose any set of rows in the Project Workplan on
which ongoing reporting is appropriate for the project.
Having a customizable reporting view without impacting
other tracking views minimizes the ongoing reporting
effort for project. Rows are displayed in this view when
the value of the “Summary Row Flag” is set to “Yes.”
14_OUM_Project_Consolidated_Work_Products Project Implementation This view gives the project manager and project team
leads the ability to view and report on project progress
Delivery by consolidated work products (CWPs) defined for the
project.
15_OUM_Project_Deliverables Project Implementation This view gives the project manager and project team
leads the ability to view and report project progress by
Delivery the deliverables defined for the project.
16_OUM_Project_Tasks_By_Process Project Implementation This view gives the project manager and project team
Delivery from the perspective of a specific OUM process.
17_OUM_Show_Out-Of_Scope_Rows Initial Planning This view is used to permanently remove out of scope
activities and tasks from the project-specific Project
Workplan.
18_OUM_View_Maintenance Project Workplan Allows you to refine/customize what is displayed in the
Maintenance existing OUM views by changing the text/flag values
that are used to filter the Project Workplan.
This view also is helpful in identifying why a particular

row is or is not being displayed within a specific OUM
view.
20 _OUM_Resource_Usage Project Implementation Allows viewing of project plan resources through project
tailorable view.
Delivery
File Ref: Document1 OUM-Specific Microsoft Project View Descriptions 22

12 COLUMN-Field-View Reference
This section lists the OUM View Column Headings and their associated Microsoft Project Fields along with a brief description as well as a
matrix indicating on which OUM View they are included.
17_OUM_Show_Out_of_Scope_Rows
16_OUM_Project_Tasks_By_Process
12_OUM_Activity_Work_Allocation
10_OUM_Project_Iteration_Groups
14_OUM_Project_Consolidated_
15_OUM_Project_Deliverables
11_OUM_Project_Workshops
01_OUM_Est_Results_XFER
18_OUM_View_Maintenance
08_OUM_jProject_Activities
07_OUM_Project_Partitions
13_OUM_Project_Summary
02_OUM_Set_Project_Filter
09_OUM_Project_Iterations
06_OUM_Project_Planning
OUM View
03_OUM_Plan_Filtered
Microsoft
Column Description
Project Field
Heading
Work_Products
00_OUM_All
% Work % Work This is a calculated field in X X X
Complete Complete Microsoft Project that can be
manually overridden. It
represents a roll up summary of %
of work completed for the phase,
activity and/or task.
Activity ID Text8 OUM Activity ID. This is not the X X X X X X X X X X
same as the OUM ID (WBS).
Activity Name Text14 OUM Activity Name. This is not X
the same as the Name (Name).
Actual Finish Actual Finish This date is system-time stamped X X
Date Date or manually entered when an
activity or task has been
documented as completed in the
Project Workplan. In this view, the
date represents when the last task
has been completed for the
activity or the last activity has
been completed for the phase.
Actual Work Actual Work Actual work performed for a phase X X X
that is a roll up of actual work
recorded at the activity and/or task
level in the Project Workplan.
Approved By Text26 This is the customer resource who X X
approved the CWP is 100%
completed/finished. The CWP
should not be marked as
100%completed/finished without
this column being populated.
File Ref: Document1 COLUMN-Field-View Reference 23

OUM View
Microsoft
Column Description
Project Field
Heading
Work_Products
00_OUM_All
Assigned Resource Column used to assign project X X X X X X X X X X X
Resource Initials resources initials to an activity
Initials grouping or task(s), so MS Project
scheduling functionality can be
used to level resources and assist
in establishing estimated start and
finish dates for activities.
Baseline Baseline This is the estimated finish date X X
Finish Date Finish that was baselined at the
beginning of the project when the
plan was initially developed.
Cons WP Flag6 This column indicates whether or X X X
not a work product is considered a
consolidated work product (CWP)
for the project. A value of “Yes”
indicates the method component
for this project is being treated as
a CWP.
Duration Duration X
Est # of Number3 Number field where you can enter X
Phase the estimated number of iterations
Iterations that will occur for a phase. See
section 5 of this document for
guidance on how to calculate the
value for this column for each
phase.

OUM View
Microsoft
Column Description
Project Field
Heading
Work_Products
00_OUM_All
Est Effort Work Estimated effort (or work) for X X X X X X X X X X X X X X X
activities initially derived from the
values entered on the
view that are then
allocated/distributed to the
applicable tasks within the activity.
Depending on the view, estimated

effort for phase derived from the
sum of estimated effort at activity
level.
Est Finish Finish Estimated date for finishing the X X X X X X X X X X X X X X X
Date activity based on task
dependencies and staff
resourcing considerations. The
value of this column is optimally
generated by MS Project based
on both activity dependencies and
resource assignments.
Est Start Start Estimated date for starting the X X X X X X X X X X X X X X
Date activity based on predecessor
dependencies and
resource/staffing limitations or
considerations. The value of this
column is optimally generated by
MS Project based on both activity
dependencies and resource
assignments.
Estimating Text2 Column used to store the delivery X X X X X
Channel channel assumptions used when
Assignments estimating effort for an OUM
activity, and the respective %
allocations for each activity. This
information is helpful for staff
planning and budgeting work

OUM View
Microsoft
Column Description
Project Field
Heading
Work_Products
00_OUM_All
Estimating Text24 Column used to store the X X X X X X X X X X X X X
Role estimating role assignment(s)
Assignments assumptions used when
estimating the effort for an OUM
activity and the respective %
allocations for each resource
defined for the activity. This
information is helpful for staff
planning and budgeting work.
Iteration Text13 User-assigned textual-based ID X X X X X X X X X X X
Group ID for OUM tasks that are part of a
specific iteration group. Iteration
groups are created by the user
during the use case modeling
work that occurs in the
Elaboration phase of a project, if
they are required. This Iteration
Group ID enables other iteration
group-based views to correctly
display (filter) activities and tasks
associated to a specific iteration
group.
Iteration ID Text12 User-assigned textual-based ID X X X X X X X X X X X X
assigned to a specific iteration
within a specific OUM phase.
Iteration IDs are created by the
user during the detailed iteration
planning that should occur prior to
an iteration starting. This Iteration
ID enables other iteration-based
views to correctly display (filter)
activities and tasks associated to
a specific iteration.

OUM View
Microsoft
Column Description
Project Field
Heading
Work_Products
00_OUM_All
Key Del Flag1 User-defined value in this column X X X X X X X X X X X X X X
identifies whether the row or more
specifically the work product of a
task is considered a key
deliverable for the project.
Typically, deliverables are stated
or documented in the statement of
work or contract for the project.
This flag enables other OUM
deliverable-based views to work.
This column indicates if the work

product associated to the method
component is considered a project
deliverable. Typically, only those
items indicated on the project
statement of work (SOW) or
project contract as deliverables
are considered deliverables. A
value of “Yes” indicated the
method component for this project
is being treated as a deliverable.
Method Role Text25 Textual column which lists the X X X X X X X X X X X
Assignments method role(s) assigned to a task
within the OUM method guidance.
This column is intended to provide
a link between the Project
Workplan and the methodology,
which is important if a project is
audited for method compliancy.
Name Name Name assigned to the OUM X X X X X X X X X X X X X X X X X X
component. Depending on the
view that is the phase, activity or
task name.
OUM Activity Flag4 X
Row

OUM View
Microsoft
Column Description
Project Field
Heading
Work_Products
00_OUM_All
OUM ID WBS OUM Component ID, that is, X X X X X X X X X X X X X X X X X X X
phase, activity and task ID
On the
view, only the task-level activity
placeholders show, that is OUM
Activity ID followed by .TSK.
OUM Phase Flag5 X
Row
Out of Scope Flag19 This column contains the project X
for All Rows? filtering values to display all rows.
(Display All Basically, if you copy this column
Rows) into the Project Filtered Row (Out
of Scope) column and all rows are
included in the Project Workplan.
Out of Scope Flag15 This column contains the project X X
for BI View? filtering values to display only
OUM rows that make up the OUM
Business Intelligence view.
for Core filtering values to display only
Workflow OUM rows that make up the tasks
View? that are part of the OUM Core
Workflow.

OUM View
Microsoft
Column Description
Project Field
Heading
Work_Products
00_OUM_All
Out of Scope Flag8 The value of this column drives X X X X X X X X X X X X
for Project? the project level filtering for many
of the other OUM-specific
Microsoft Project views (03
through 16). This column can be
used in two ways. First, you can
change any specific row at any
time. If a task is OUT of scope for
your project, insert Yes. If a task
is not out of scope (that is, in
scope) for your project, insert No.
Second, using the
02_OUM_Set_Project_Filter view,
you can use any of the other
columns to populate this column
by doing a simple copy and paste.
See Section 4 of this document
(Tailor the Project Workplan for
Your Project) for more information
on project filtering.
for Req- filtering values to display only
Driven App OUM rows that make up the OUM
Imp View? Requirements-Driven
Application Implementation
view.
for Software filtering values to display only
Upgrade OUM rows that make up the OUM
View? Software Upgrade view.
for Sol-Driven filtering values to display only
App Imp OUM rows that make up the OUM
View? Solution-Driven Application
Implementation view.

OUM View
Microsoft
Column Description
Project Field
Heading
Work_Products
00_OUM_All
for Tech Full filtering values to display only
Lifecycle OUM rows that make up the OUM
View? Technology Full Lifecycle view.
for filtering values to display only
WebCenter OUM rows that make up the OUM
View? WebCenter view.
Partition ID Text9 User-assigned textual-based ID to X X X X X X X X X X
assist with indexing OUM
components such as activities and
tasks into a specific user- created
partition. This ID enables other
partition views to correctly display
(filter) activities and tasks
associated to a partition grouping.
Partition Row Flag3 Partition Row Flag - Not used to X X
filter partitions - See Text 9 -
Partition ID
Phase Text23 Name of OUM phase
Predecessors Predecessors Column defines the activities that X X X X X X X X X X X X X
must be completed prior to the
selected activity starting (most of
the times this is a “Finish to Start”
predecessor dependency). There
are other derivatives of this
dependency such as “Finish to
Finish”, but in most cases it is
“Finish to Start.”
Process ID Text6 OUM process ID assigned to X X X X X X X X
process associated to OUM task
Process Text7 Name of OUM process associated X X X X X X X X
Name to the OUM process ID

OUM View
Microsoft
Column Description
Project Field
Heading
Work_Products
00_OUM_All
Project Flag10 The value in this column is X
Activity Row leveraged by multiple OUM
defined filters that in turn support
other OUM-specific Microsoft
Project views such as the OUM
“05_OUM_Activity_Level_Filtered”
view.
Remaining Remaining This is a calculated field in X X X
Work Work Microsoft Project that can be
manually overridden. It
represents a roll up summary of
remaining work for the phase,
activity and/or task.
Resource Resource Column used to assign project X X
Names Names resources to an activity so MS
Project scheduling functionality
can be used to level resources
and assist in establishing
estimated start and finish dates for
activities.
Successors Successor Column defines the activities that X
are depending on the selected
activity to be completed prior to
them starting.
Summary Flag2 User-defined value in this column X X X X X X X X X X X X X
Row identifies whether the row in the
plan is desired to be part of the
13_OUM_Project_Summary view.
The summary view is intended to
provide summary level reporting
to the project customers. This flag
enables the project management
team to identify specific rows to be
displayed.

OUM View
Microsoft
Column Description
Project Field
Heading
Work_Products
00_OUM_All
Task-Level Flag18 This column contains the project X X
Activity filtering values that allow for
Placeholder removing the OUM Activity
Filtering Summary Tasks.
Task Notes Text15 User Task Notes X
Work Product Text1 Name of OUM work product X X X X X X X X X X X
associated to the OUM task
Workshop ID Text11 User-assigned textual-based ID to X X X X X X X X X X X
assist with indexing OUM
components such as activities and
tasks into a specific user-created
workshop. This ID enables other
workshop views to correctly
display (filter) activities and tasks
associated to a grouping of tasks
that are performed within a
particular workshop.
XFER Flag Flag7 This column identifies whether a X
row should be included in the
OUM
“01_OUM_Est_Results_XFER”
view and should NOT be
changed.

Project Workplan Users Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Project Workplan Users Guide

Uploaded by

Copyright:

Available Formats

OUM

PROJECT WORKPLAN USER’S GUIDE

File Ref: Document1 Preface i

 Tailoring OUM for Your Project

File Ref: Document1 Preface ii

1 OUM Project Planning Process/Component Overview .......................................... 1

2 Copy the Project Workplan Template ....................................................................... 9

3 Load Estimated Effort into the Project Workplan ................................................. 10

4 Tailor the Project Workplan for Your Project ........................................................ 11

6 Use the Project Workplan for High-Level Implementation Planning .................. 15

8 Use the Project Workplan for Tracking Project Progress .................................... 18

9 Use the Project Workplan for Progress Reporting ............................................... 19

10 Maintain the Project Workplan Template ............................................................... 20

11 OUM-Specific Microsoft Project View Descriptions ............................................. 21

12 COLUMN-Field-View Reference .............................................................................. 23

File Ref: Document1 Contents iii

1 OUM Project Planning Process/Component Overview

1.1 Overview of OUM Iterative and Incremental Planning

File Ref: Document1 OUM Project Planning Process/Component Overview

Support of Bid and Initial Planning Process

1.2 OUM Project Workplan Template

File Ref: Document1 OUM Project Planning Process/Component Overview

 Common Terms and Definitions

Term Definition Usage Assumption

File Ref: Document1 OUM Project Planning Process/Component Overview

File Ref: Document1 OUM Project Planning Process/Component Overview

Use of Microsoft Project Text and Flag Fields

File Ref: Document1 OUM Project Planning Process/Component Overview

Project Flag Field Assignments within OUM MPP Template

Project Text Field Assignments within OUM MPP Template

Project Number Field Assignments within OUM MPP Template

File Ref: Document1 OUM Project Planning Process/Component Overview

OUM-Specific Microsoft Project Views

File Ref: Document1 OUM Project Planning Process/Component Overview

Refer to section 10 for a description of each view.

File Ref: Document1 OUM Project Planning Process/Component Overview

2 Copy the Project Workplan Template

File Ref: Document1 Copy the Project Workplan Template 9

3 Load Estimated Effort into the Project Workplan

4 Tailor the Project Workplan for Your Project

5 Remove Out Of Scope activities and tasks from the

6 Use the Project Workplan for High-Level Implementation

File Ref: Document1 Use the Project Workplan for High-Level

7 Use the Project Workplan for Detail and Iteration Planning

8 Use the Project Workplan for Tracking Project Progress

9 Use the Project Workplan for Progress Reporting

10 Maintain the Project Workplan Template

File Ref: Document1 Maintain the Project Workplan Template 20

11 OUM-Specific Microsoft Project View Descriptions

View Supports Brief Description

Once you have selected a starting view (for example,

Delivery It is the primary view for applying specific tailoring to

File Ref: Document1 OUM-Specific Microsoft Project View Descriptions 21

View Supports Brief Description

This view also is helpful in identifying why a particular

File Ref: Document1 OUM-Specific Microsoft Project View Descriptions 22

File Ref: Document1 COLUMN-Field-View Reference 23

File Ref: Document1 COLUMN-Field-View Reference 24

Depending on the view, estimated

File Ref: Document1 COLUMN-Field-View Reference 25

File Ref: Document1 COLUMN-Field-View Reference 26

This column indicates if the work

File Ref: Document1 COLUMN-Field-View Reference 27

File Ref: Document1 COLUMN-Field-View Reference 28