W6_Aiya_Introduction to EVM part2: steps to implement EVM for Advisory service step 1

Introduction to EVM part2: steps to implement EVM for Advisory service step 1.

1-      Problem identification:

The aim of this blog is to identify the first step to implement EVM method this blog is considered as a completion of week 2 blog. The first step is to identify the scope of work of the project this will be done by constructing Work Breakdown Structure (WBS). OPWP is the owner and needs to identify the WBS up to level three.

2-      Feasible Alternatives

There different ways to structure the WBS which are:

-          analogy approach

-          top-down approach

-           bottom-up approach 

3-      Development of the outcome of the alternatives

Top- down approach is used when the scope of work is well known and usually it is used for projects that are repeated over and over. Bottom-up approach is much more detailed and can be time consuming. Further analogy approach requires a hierarchal list of tasks should be developed and uniquely coded and needs be on actual basis.

4-      Selection criteria

In the procurement process the WBS needs to be easily implemented and completed to cover the important aspects of the process those two elements are the most critical criteria’s.

5-      Analysis and Comparison of the alternatives

The analog approach is recommended when working for a consulting firm that does similar projects for the same client, this approach may be simple and effective. top-down approach begins with the final or largest deliverables. Then, all of the components that make up these deliverables are identified. This process continues to greater and greater detail until all work packages are identified. bottom-up approach involves intense team participation. Members begin by identifying as many specific tasks as possible, and then group these tasks into larger project activities. These project activities may then be grouped into more and more comprehensive activities, until the final deliverables for the project are planned.

for this blog posting top-down approach is preferable as OPWP is the owner and no need for very detailed WBS.

To create the WBS all major deliverables must be identified. And then divided each deliverable into component tasks. Each task well be coded using a unique code to make easy for referencing.

The below figure describes the procurement process in Project Development Department using Top-Down approach:

6-      Selection of the preferred alternative

Alternately,3D WBS can be created to for tendering process as it can be applied in typical scope of work project for better visibility and flexibility of cost estimation feedback, schedule and project control monitoring/analysis. However, it is much more complicated that why the author of this blog recommends creating it in the upcoming blogs.

7-      Performance monitoring and the post evaluation results

It is recommended to keep track of the WBS created an incase the employee finds a task that is requires but not registered in the WBS to update it as it is a live document.

8-      References:

1-      Emanuele Della Valle, Work Breakdown Structure

https://www.slideshare.net/emanueledellavalle/pmsp2012-07-wbs

2-      Work Breakdown Structure

http://www.doing-projects.org/Conceptbox/Work-Breakdown-Structure-WBS

3-              MICHAEL D TAYLOR , JUNE 3, 2017, WBS Types (Work Breakdown Structure)

https://project-management.com/wbs-types-work-breakdown-structure/