Measuring project effectiveness of cost and schedule
Blue Zuma
Part 4
1. Take Blue Zuma results rom Part 2B. This is leveling outside of slack.
Start date is 3/2/2015; end date is 4/18/2016
duration is 290 days
total cost is $1,249,200
Baseline your project
(Project – Baseline)
2. Answer the questions in Part 4.
Go To: View - Tables - Costs
q1: $1,249,200
q2: Detailed Product Design; $317,000
q3: you can do the same as for task usage but it is cumbersome
go to Report - costs - cash flow
q4: July 2015; cost is $157,260; followed by Aug at $153,620
Jan 2016; cost is $2800
(go to Task Usage - click on work - select costs - unselect work in another right click
select timescale - set middle tier to half year - set bottom tier to months
Monthly costs are at the top
Part 5
enter data from part 5
change the actual durations not the dates
(go to View - Tables - Tracking)
enter Actual Duration numbers from text into the ACT. Duration column on the Gantt
Chart, type in 0 for any remaining
also, enter 100% if no remaining time exists
go back to View - Tables - entry ( some may want to go to Schedule)
Duration has gone from 290 days to 264
Finish date is now 3/11/2016
cost is $1,165,000
go to Tracking Gantt
you can see where the project has changed.
the red lines are the critical path.
( not all of the path is highlighted because the previous tasks are complete.
Qb: you can see using the tracking gantt which have gone well.
you can also use the EV charts to tell which has gone well
(View-Tables-More Tables - EV)
you will see mostly zeros, because the program thinks you want to know how the
project is doing as of 3/30.
need to change the date to 9/28 (completion of Test Prototype.
(Project - Status Date - type in 9/28/15
you can now see which of the tasks have done well
- all but Detailed Product Design and Test Prototype and Product Design Selection
Manufacturing processes has a TCPI of 0.92
Go to EV Schedule Indicators
compare PV vs EV
should vs has completed