paper

profilenkg-iv
SIMprojectreport.docx

CMGT 570 Project Management

Alliance Prototype Project

Executive Management Report

------

----

----

Executive Summary

Description

The Alliance project represents a strategic effort to enhance the sales and marketing capabilities of Uniworld with an E-commerce equipped web site. This web site is needed to help Uniworld to regain its global market dominance.

Deliverables

The Alliance Prototype product is to be composed of hardware and software required in establishing an E-commerce web site capable of demonstrating the feasibility of developing a fully functional site capable of taking product orders and generating product fulfillment. The deliverables for this project are the demonstration web site, site documentation, and recommended product architecture.

Performance

The prototype web site will be accepted upon successful completion of the customer acceptance test with no more than 12 known defects which will represent an estimated Mean Time To Failure (MTTF) of 5 days. Furthermore, no known defects can be present which could potentially cause system failure or major loss of functionality. The web site must be capable of demonstrating the feasibility of handling a peak load of 2000 hits per hour without appreciable degradation in system response

Tasks

The project contains seven major tasks. The tasks required at least five people to be working on them. management ended up having more than two people working on the same task to avoid delays. The project overview provided a clear discerption of each task along with the personal required to finish the task. Management insisted that the project does not exceed $ 50,000 within a time period of 52 days. In order for the project to be excepted, the defect level must not exceed 12 defects.

Project Planning

1. The tasks were studied in order to understand them.

2. We reviewed the available employees’ profiles.

3. Each person was assigned the task that fit his or her qualifications.

4. We planned for some risks including but not limited to overtime, buying materials, new tasks.

5. Recognitions were also part of the planning to motivate outstanding personal.

6. Stakeholders were planned to be given a status report every 2 weeks.

7. Training also was part of the planning to increase efficiency.

Project Monitoring

After running each week, we carefully reviewed the weekly report to make sure everything was going as planned. We had to make some adjustments to the original plan due to some unforeseen events. David Lewis had some family issues which made him work from home after management permission. Task 1 was delayed couple days due to the absence of some major stakeholders to one of the meetings. As a result, we had to put more people on some tasks to avoid delays.

Management Strategy

Our goal was to finish the project on time and within budget. We made sure that productivity of the employees is at its best. Therefore, we gave them free food, and we made sure that they stay entertained. We sent out status reports to all stakeholders to keep them informed every 2 weeks.

Goals vs Actual Performance

Goals

Actual performance

Budget

(Plan $50,000)

$50,388

Schedule

52 days

50 days

Defects

< 12

12

Lessons Learned (Retrospectives)

Management: we learned that informing management with big decisions will help the process of making the project easier. Management suggested that we should motivate the team in order to increase productivity. Moreover, it is important that management recognize the good work that was accomplished.

Communication: team members must communicate with each other as well as team members and management. We learned that David was going through a hard time because we communicated with him. Moreover, we discovered also that David and Tea do not get along with each other.

Leadership: it is very important that the leader of the project keeps his or her employees in mind and not to drawn them with work. They must come to work wanting to work, and it is the leader’s responsibility to make them want to come to work.

Resource Plan

Figure 1

Actual Weekly Performance

Figure 2

Week

Earned Value

Planned Value

Actual Cost

Cost Variance

Schedule Variance

PCPI

CPI

SPI

1

$ 2,415

$ 2,609

$ 1,720

$ 695

$ 194

4.83%

1.40

0.93

2

$ 3,940

$ 5,652

$ 3,440

$ 500

$ 1,712

7.88%

1.15

0.70

3

$ 9,030

$ 12,174

$ 8,200

$ 830

$ 3,144

18.06%

1.10

0.74

4

$ 15,775

$ 18,696

$ 13,295

$ 2,480

$ 2,921

31.55%

1.19

0.84

5

$ 22,655

$ 25,217

$ 18,640

$ 4,015

$ 2,562

45.31%

1.22

0.90

6

$ 30,625

$ 31,304

$ 26,670

$ 3,955

$ 679

61.25%

1.15

0.98

7

$ 38,255

$ 35,652

$ 33,255

$ 5,000

$ (2,603)

76.51%

1.15

1.07

8

$ 45,225

$ 40,000

$ 38,683

$ 6,542

$ (5,225)

90.45%

1.17

1.13

9

$ 49,840

$ 44,348

$ 44,628

$ 5,212

$ (5,492)

99.68%

1.12

1.12

10

$ 50,000

$ 50,000

$ 50,388

$ (388)

$ -

100.00%

0.99

1.00

Earned Value Graph

Graph 1

Estimated Work Finish (Weeks)

Graph 2

Quality (Defect Levels)

Figure 3

Estimated Cost at Completion

Figure 4

Project Performance Index (PPI)

Figure 5

Gantt Chart

Figure 6

Network Diagram

Figure 7

Labor Cost Summary

References

1. Kushner, P., Michael, 2017. Project Management. McGraw-Hill Education

2. SIM Project: www.simulationpoweredlearning.com

1