SOLVED: Engineering Project Management

September 20, 2020
SOLVED: Engineering Project Management

 

 

Faculty of Engineering and Information Technology

 

Engineering Project Management

Course Project

Title…………

 

                         Prepared By:

St name……

St ID…..

 

                        Instructor

                                      Name……….

 

 

 

 

 

 

 

Abstract

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Table of Contents

 

 

                                                                                                                                                     

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

List of Tables

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

List of Figures

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Chapter One

Project Pre-Initiation and Initiation

It is good practice to lay the groundwork for a project before it officially starts. Senior managers

often perform several tasks, sometimes called pre-initiation tasks, including the following:

1.1 Introduction

 ………………………………………………………

1.2 the scope, time, and cost constraints for the project

……………………………

 

1.3 the project sponsor and the project manager

………………………………………………………………….

1.4 The business case for the project

………………………………………………………………………………………

 

1.0  Introduction/ Background

 

 

 

2.0 Business Objective

 

 

 

3.0 Current Situation and Problem/Opportunity Statement

 

 

 

4.0 Critical Assumption and Constraints

 

 

.

5.0 Analysis of Option and Recommendation

 

 

 

6.0 Preliminary Project Requirements

 

 

 

7.0 Budget Estimate and Financial Analysis

 

 

 

8.0 Schedule Estimate

 

 

 

9.0 Potential Risks

 

 

 

10.0 Exhibits

Exhibit A: Financial Analysis

 

 

1.5 The Project Stakeholders

……………………………………………………………

Stakeholder Register for Project Name

 

Prepared by:                                      Date:

 

Name

Position

Internal/External

Project Role

Contact Information

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

1.6 management strategy

 

This strategy includes basic information such as stakeholder names, level of interest in the project, level of influence on the project, and potential management strategies for gaining support or reducing obstacles from each stakeholder.

1.7 the Project Charter

Project Charter

 

Project Title:

Project Start Date:                                        Projected Finish Date:

Budget Information:

 

Project Manager: Name, phone, e-mail

Project Objectives:

 

 

Main Project Success Criteria:

 

 

Approach:

 

 

 

 

Roles and Responsibilities

Role

Name

Organization/

Position

Contact Information

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Sign-off: (Signatures of all above stakeholders. Can sign by their names in table above.)

 

Comments: (Handwritten or typed comments from above stakeholders, if applicable)

 

 

 

1.8 The Project Kick-off Meeting

A kick-off meeting is a meeting held at the beginning of a project so that stakeholders

can meet each other, review the goals of the project, and discuss future plans.

 

Kick-off Meeting

Date

 

Meeting Objective: Get the project off to a great start by introducing key stakeholders, reviewing project goals, and discussing future plans

 

Agenda:

  • Introductions of attendees
  • Background of project
  • Review of project-related documents (i.e. business case, project charter)
  • Discussion of project organizational structure
  • Discussion of project scope, time, and cost goals
  • Discussion of other important topics
  • List of action items from meeting

 

Action Item

Assigned To

Due Date

 

 

 

 

 

 

 

 

 

 

Date and time of next meeting:

 

 

 

 

 

 

Chapter Two

 

 

Project Planning

2.1 Overview

……………………………………

 

2.2 Requirements Matrix for Project Name

 

Prepared by:                                      Date:

 

Requirement No.

Name

Category

Source

Status

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

2.3 project scope statement

…………………………………………………………..

Scope Statement (Version xx)

 

Project Title:

Date:               Prepared by:

Project Justification:

 

 

 

.

Product Characteristics and Requirements:

1.       

2.       

3.       

4.       

 

Summary of Project Deliverables

Project management-related deliverables: business case, charter, team contract, scope statement, WBS, schedule, cost baseline, status reports, final project presentation, final project report, lessons-learned report, and any other documents required to manage the project.

Product-related deliverables: research reports, design documents, software code, hardware, etc.

  1.  
  2.  
  3.  
  4.  

 

Project Success Criteria:

 

 

 

 

 

 

2.4 work breakdown structure (WBS) and WBS dictionary

………………………………………………………………………………………………….

Work Breakdown Structure Template for Project Name

 

Prepared by:                                      Date:  

 

1.0  Main category 1

1.1 Subcategory

1.2 Subcategory

1.2.1 Sub-subcategory

1.2.2 Sub-subcategory          

1.3 Subcategory

1.4 Subcategory

 

2.0  Main category 2

2.1 Subcategory

2.2 Subcategory

2.2.1 Sub-subcategory

2.2.2 Sub-subcategory          

2.3 Subcategory

2.4 Subcategory

 

3.0  Main category 3

3.1  Subcategory

3.2  Subcategory

3.2.1 Sub-subcategory

3.2.2 Sub-subcategory          

3.3  Subcategory

3.4  Subcategory

 

4.0  Main category 4

4.1  Subcategory

4.2  Subcategory

4.2.1     Sub-subcategory

4.2.2     Sub-subcategory          

4.3  Subcategory

4.4  Subcategory

 

WBS dictionary

 

2.5 project schedule, in the form of a Gantt chart with all dependencies and resources entered and Network Diagram

………………………………………………………………………..

 

2.6 Project Organizational Chart

           

2.7 Project Budget

An example:

 

XXX Project Cost Estimate

          

Prepared by:

Date:

          

Note: Change the WBS items and other entries to meet your project needs. This data is from Figure 7-1 of Schwalbe's text

  

Information Technology Project Management, Fourth Edition. Also make sure the formulas work properly based on the data you enter.

 

# Units/Hrs.

Cost/Unit/Hr.

Subtotals

WBS Level 1 Totals

% of Total

  

WBS Items

 

 

 

 

 

  

1. Project Management

 

 

 

$306,300

20%

  

   1.1 Project manager

960

$100

$96,000

 

 

  

   1.2 Project team members

1920

$75

$144,000

 

 

  

   Contractors (10% of software development and testing)

 

 

$66,300

 

 

  

2. Hardware

 

 

 

$76,000

5%

  

    2.1  Handheld devices

100

$600

$60,000

 

 

  

    2.2  Servers

4

$4,000

$16,000

 

 

  

3. Software

 

 

 

$614,000

40%

  

    3.1 Licensed software

100

$200

$20,000

 

 

  

    3.2 Software development*

 

 

$594,000

 

 

  

4. Testing (10% of total hardware and software costs)

 

 

$69,000

$69,000

5%

  

5. Training and Support

 

 

 

$202,400

13%

  

     5.1 Trainee cost

100

$500

$50,000

 

 

  

     5.2 Travel cost

12

$700

$8,400

 

 

  

     5.3 Project team members

1920

$75

$144,000

 

 

  

6. Reserves (20% of total estimate)

 

 

$253,540

$253,540

17%

  

          Total project cost estimate

 

 

 

$1,521,240

 

  

 

2.8 Project Financial Analysis

An example:

 

Financial Analysis for Project Name

Created by:

  

Date:

        

Note: Change the inputs, shown in green below (i.e. interest rate, number of years, costs, and benefits). Be sure to double-check the formulas based on the inputs.
             

Discount rate

8.00%

          
             

Assume the project is completed in Year 0

    

Year

      
 

0

1

2

3

Total

  

Costs

140,000

40,000

40,000

40,000

    

Discount factor

1.00

0.93

0.86

0.79

    

Discounted costs

      140,000

   37,200

   34,400

   31,600

 243,200

 
             

Benefits

0

200,000

200,000

200,000

    

Discount factor

1.00

0.93

0.86

0.79

    

Discounted benefits

0

 186,000

 172,000

 158,000

 516,000

 
             

Discounted benefits - costs

     (140,000)

 148,800

 137,600

 126,400

 

 272,800

NPV

Cumulative benefits - costs

     (140,000)

 

     8,800

 146,400

 272,800

   
             

 

ROI

112%

          
 

Payback in Year 1

      

Assumptions

            

Enter assumptions here

            

 

Example Payback period:

Year

Costs

Benefits

Cum Costs

Cum Benefits

0

140,000

0

140,000

0

1

37,200

186,000

177,200

186,000

2

34,400

172,000

211,600

358,000

3

31,600

158,000

243,200

516,000

 

2.7 A list of prioritized risks (part of a risk register)

List of Prioritized Risks for Project Name

 

Prepared by:                                                  Date:

 

Ranking

Potential Risk

1

 

2

 

3

 

4

 

5

 

6

 

7

 

8

 

9

 

10

 

 

 

 

2.9 Summary

  

 

 

 

Chapter Three

 

Project Execution

3.1 Introduction

……………………………………………….

 3.2 Milestone report

……………………………………………………….

Milestone Report for Project Name

 

Prepared by:                                                  Date:

 

Milestone

Date

Status

Responsible

Issues/Comments

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

3.3 Summary

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Chapter Four

Project Monitoring and Controlling

 

Monitoring and controlling is the process of measuring progress toward project objectives, monitoring deviation from the plan, and taking corrective action to match progress with the plan. Monitoring and controlling is done throughout the life of a project.

 

4.1           Introduction

4.2           Status/Progress Report

……………………

Status/Progress Report

 

Project Name:

Team Member Name:

Date:

Reporting Period:

Work completed this reporting period:

 

 

Work to complete next reporting period:

 

 

What’s going well and why:

 

What’s not going well and why:

 

Suggestions/Issues:

 

Project changes

 

 

 

4.3           Summary

 

 

 

 

 

 

 

 

 

Chapter Five

 

Project Closing

 

 

4.1 Introduction

 

 

…………………………………………………

4.2 Lessons-learned report

 

……………………………………………………………..

Lessons Learned Report

 

Prepared by:              Date:

Project Name:          

Project Sponsor:      

Project Manager:     

Project Dates:           

Final Budget:            

  1. Did the project meet scope, time, and cost goals?

 

 

 

  1. What was the success criteria listed in the project scope statement?

 

 

 

  1. Reflect on whether or not you met the project success criteria.

 

 

 

  1. In terms of managing the project, what were the main lessons your team learned?

 

 

 

  1. Describe one example of what went right on this project.

 

 

 

  1. Describe one example of what went wrong on this project.

 

 

 

  1. What will you do differently on the next project based on your experience working on this project?

 

 

 

 

 

 

4.3 Conclusion

 

 

 

 

 

 

 

 

 

 

 

References

 

  

 

[1]     …………………………  use this type of reference

[2]     …………………………….

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Place your order

LEAVE A COMMENT

Comment Box is loading comments...