You are on page 1of 2

Interpretation:

Software Customization:
1. Positive Scheduled Variance (SV) represents that software customization is
positive which means project is way ahead of the planned schedule
2. Schedule Performance Index (SPI) is more than 1 with an average of 1.13.
Hence 13% more work is being done than the planned schedule
3. Cost Variance (CV) across all the months is positive indicating that
expenditure is less than planned budget i.e. under budget.
4. Cost Performance Index (CPI) is more than 1 across all the months with 1.18
on average indicating that for every dollar investment, $1.18 worth work is
done
5. Control Ratio (CR) is greater than one indicating that cost and time of the
project are better than planned

Technical Infrastructure:
1. Positive Scheduled Variance (SV) for first month is as per schedule but turns
negative indicating that project is below the planned schedule
2. Schedule Performance Index (SPI) is one for the first month while it is less
than 1 with an average of 0.95 indicating that only 95% of the planned work
is executed
3. Cost Variance (CV) is turning negative from first month to 4 th but has become
positive in fifth month indicating that usage of available resources has
improved for 5th month
4. Cost Performance Index (CPI) is less than 1 across all months with an average
of 0.93 indicating that only 93 cents worth of work is being done for every
dollar spent
5. CR is initially going down and improved eventually indicating that the project
is getting back on track

Combined Projects
1. SV is positive except for the month of June. Overall, project seems to be going
ahead of the planned schedule
2. SPI on average is positive with avg value 1.039 indicating that the project
14% ahead of schedule
3. CV is negative June and August but positive overall indicating that the project
is under budget
4. Average CPI of 1.05indicate that for every dollar investment, 1.05 worth of
work is being done
5. Control ratios are more than 1 indicating the project is doing well in terms od
both cost and time

Recommendations:
1. Overall project status seems positive.
2. But, Technical Infrastructure lags behind in both Cost and Time while Software
Customizations seems to be doing well
3. With overall project faring well, project can be completed on time provided,
Technical Infrastructure projects are managed well while maintaining the pace
of software customization project

Questions:

1. Which of the two components are underperforming according to the plan? How do you know
this?
Technical Component
2. Are the components of the project within budget? How do you know?
Only software component is within the budget while Technical component is not
3. What can you conclude by looking at the combined earned value data for the entire project?
While combined EV gives overall status of the project, it is difficult to interpret which
component has to be addressed and which component is doing well

4. Why did Terry Baker think that the project was going according to plan the entire time?
Combined project statistics showed a positive picture of the project.
5. How much longer will the project take?
6. What should Martin have done earlier in the project timeline to prevent delays?
Analysis at each component level rather than combined project
Identification of gaps and reasons for delays
More detailed management of tasks
7. What should Martin do when managing future projects to prevent similar problems from
developing?
Information sharing on time
More detailed analysis of the project
Planning dependencies and hence the project accordingly

You might also like