Resource: Project Management: The Managerial Process, Ch. 13 and Electroscan, Inc.
Grading Rubric Attached!!!!
Evaluate the Earned Value Management (EVM) Case Study Scanner Project below:
Case Study: Scanner Project:
You have been serving as Electroscan’s project manager and are now well along in the project.
Develop a narrative status report for the board of directors of the chain store that discusses the status of the project to date and at completion. Be as specific as you can using numbers given and those you might develop.
Remember, your audience is not familiar with the jargon used by project managers and computer software personnel; therefore, some explanation may be necessary. Your report will be evaluated on your detailed use of the data, your total perspective of the current status
Calculate:
EVM information from the data provided using the Electroscan Student (Table Attachment) spreadsheet and then draw conclusions regarding the status of the project in the case study.
Draw:
conclusions regarding project health from the Earned Value analysis.
Analyze :
the effects of given schedule variances as well as SPI, CPI, EAC, TCIP, and any other EVM analytical products they deem valuable.
Write your findings in a 350- to 700-word memorandum.
Sheet1
| Electroscan, Inc. | 20 In-Store Scanner Project | |||||||
| 555 Alcorn Street, Suite 5 | (thousands of dollars) | |||||||
| Boston, Massachusetts | Actual Progress a/o January 1 | |||||||
| NAME | PV | EV | AC | SV | CV | BAC | EAC | |
| Scanner Project | 420 | 395 | 476 | -25 | -81 | 915 | 1128 | |
| H 1.0 Hardware | 92 | 88 | 72 | -4 | 16 | 260 | 243 | |
| H 1.1 Hardware Specifications (DS) | 20 | 20 | 15 | 0 | 5 | 20 | 15 | |
| H 1.2 Hardware Design (DS) | 30 | 30 | 25 | 0 | 5 | 30 | 25 | |
| H 1.3 Hardware Documentation (DOC) | 10 | 6 | 5 | -4 | 1 | 10 | 8 | |
| H 1.4 Prototype (PD) | 2 | 2 | 2 | 0 | 0 | 40 | 40 | |
| H 1.5 Test Prototypes (T) | 0 | 0 | 0 | 0 | 0 | 30 | 30 | |
| H 1.6 Order Circuit Boards (PD) | 30 | 30 | 25 | 0 | 5 | 30 | 25 | |
| H 1.7 Preproduction Models (PD) | 0 | 0 | 0 | 0 | 0 | 100 | 100 | |
| OP 1.0 Operating System | 195 | 150 | 196 | -45 | -46 | 330 | 480 | |
| OP 1.1 Kernel Specifications (DS) | 20 | 20 | 15 | 0 | 5 | 20 | 15 | |
| OP 1.2 Drivers | 45 | 55 | 76 | 10 | -21 | 70 | 97 | |
| OP 1.2.1 Disk Drivers (DEV) | 25 | 30 | 45 | 5 | -15 | 40 | 60 | |
| OP 1.2.2 I/O Drivers (DEV) | 20 | 25 | 31 | 5 | -6 | 30 | 37 | |
| OP 1.3 Code Software | 130 | 75 | 105 | -55 | -30 | 240 | 368 | |
| OP 1.3.1 Code Software ( C ) | 30 | 20 | 40 | -10 | -20 | 100 | 200 | |
| OP 1.3.2 Document Software (DOC) | 45 | 30 | 25 | -15 | 5 | 50 | 42 | |
| OP 1.3.3 Code Interfaces ( C ) | 55 | 25 | 40 | -30 | -15 | 60 | 96 | |
| OP 1.3.4 Beta-Test Software (T) | 0 | 0 | 0 | 0 | 0 | 30 | 30 | |
| U 1.0 Utilities | 87 | 108 | 148 | 21 | -40 | 200 | 260 | |
| U 1.1 Utilities Specifications (DS) | 20 | 20 | 15 | 0 | 5 | 20 | 15 | |
| U 1.2 Routine Utilities (DEV) | 20 | 20 | 35 | 0 | -15 | 20 | 35 | |
| U 1.3 Complex Utilities (DEV) | 30 | 60 | 90 | 30 | -30 | 100 | 150 | |
| U 1.4 Utilities Documentation (DOC) | 17 | 8 | 8 | -9 | 0 | 20 | 20 | |
| U 1.5 Beta-Test Utilities (T) | 0 | 0 | 0 | 0 | 0 | 40 | 40 | |
| S 1.0 System Integration | 46 | 49 | 60 | 3 | -11 | 125 | 145 | |
| S 1.1 Architecture Decisions (DS) | 9 | 9 | 7 | 0 | 2 | 10 | 8 | |
| S 1.2 Integration Hard/Soft (DEV) | 25 | 30 | 45 | 5 | -15 | 50 | 75 | |
| S 1.3 System Hardware/Software Test (T) | 0 | 0 | 0 | 0 | 0 | 20 | 20 | |
| S 1.4 Project Documentation (D)C | 12 | 10 | 8 | -2 | 2 | 15 | 12 | |
| S 1.5 Integration Acceptance Testing (T) | 0 | 0 | 0 | 0 | 0 | 30 | 30 | |
| Note: There are minor errors in the Larson & Gray (2013) table. These appear to be found only in the EAC column. They are corrected here. | ||||||||
| You have been serving as Electroscan’s project manager and are now well along in the project. Develop a narrative status report for the board of directors of the chain store that discusses the status of the project to date and at completion. Be as specific as you can using numbers given and those you might develop. Remember, your audience is not familiar with the jargon used by project managers and computer software personnel; therefore, some explanation may be necessary. Your report will be evaluated on your detailed use of the data, your total perspective of the current status and future status of the project, and your recommended changes (if any). |
"Looking for a Similar Assignment? Get Expert Help at an Amazing Discount!"
