Speaking on Techncial Performance Measures and conducting workshop on same topic with Mr. Kranz and Tom Coonce of IDA.
Speaking on Techncial Performance Measures and conducting workshop on same topic with Mr. Kranz and Tom Coonce of IDA.
There was a question posed on LinkedIn
How do you get Project Manager understand the importance of Earned Value Management?
It's been shown over and again when we make EV a compliance process and hold managers accountable for compliance it is a necessary condition for success, but far from sufficient.
Until EVM starts providing actionable information to the program management staff in the form of "leading indicators" it will always be one of those compliance processes. This information must reveal where in the program, technical and programmatic changes can be made, the testable outcomes of those changes on program performance, and the impacts on cost and schedule forecasts and the EAC against the BAC. Starting at the program level, but going down to the Control Account and Work Package.
In other words...
Nice data there in your Formats 1-5 and really nice IMS, what should I do next?
EV numbers themselves are lagging indicators, non-statistically adjusted, non risk adjusted, not connected to the effectiveness and performance measures of the project - unless enlightened users do so - and not connected to the needed capabilities of the customer as delivered by the program. There is no DID for the IMP, so Systems Engineering rarely flows down MOEs and MOPs - except where they do, because of the knowledge of the power of this approach.
Next is a real problem. 748-C has a loop hole big enough to fly a 787 through. In section 3.8 "Earned value is a direct measurement of the quantity of work accomplished. The quality and technical content of work performed is controlled by other processes." Measuring quantity is a construction centric view of producing value. Not a value centric view. Our defense, space, biopharma, software intensive programs that apply EVM are not pouring concrete or welding pipe. (I used to work in that domain as a SW developers on piping design systems). If we see EV as measuring quantity we ignore all the concerns Paul Solomon has brought forward, starting with the missing Technical Performance Measures for the product.
Sure we have exit criteria for the Work Packages. But these need to trace vertically through the IMP to the Capability to accomplish the mission or provide a solution to the business need. In other do something with the resulting product or service. It has to be the right thing of course. But EV - as stated in 748 - only measures to quantity of parts needed to delivery a capability, not the ability of the system to fulfill the needed capabilities. This by the way is essentially a Systems Engineering issue. With the missing IMP, most of the motivation for connecting the dots between EV and mission success is simply not there. It's back to the immutable principle
We don't know what done looks like in units of measure meaningful to the decision makers
"Earning value" means assessing the efficacy of the BCWS. This means assessing the Technical Performance Measures of the work be delivered. Many implementations assign TPMs and QBD's this work. But this is not called out in 748-C nor any formal EV guidance. It is called out in the DAG and the old SEMP DID. No SEMP DID is in place.
So as EV practitioners we need to make the business case of EVM, not just the compliance case. When we add "leading indicators" that are statistically sound (Eric Druker has written about this as have others, including me), forecasting of EAC based on ARIMA processes rather than our linear, non-statistical, non risk adjusted CPI/SPI measures. As well those measure "roll up" the variances of all the past time series data, just like Darrell Huff tells us to do in "How To Lie With Statistics".
All the data is available in the EV engine and in the CR at PARCA for DOD jobs. What's next is to start using EVM in the same way supply chain managers, quality control managers, systems engineers, and every design and manufacturing engineer does - compare statistically adjusted performance against the probabilistic plan to see leading indicators emerge of where we are going to go into the ditch in the future, show the PM, that corrective action "before the fact" rather than after.
This will be a topic discussed at EVM World and ISCEA conferences coming soon.
Earned Value measures the production of tangible outcomes from work efforts on a project using Physical Percent Complete. This P%C is calculated used Quantifiable Backup Data shows what technical or operation goals must be met on a planned date in order to claim some Percent Complete. Measures of this physical percent are NOT how much money you spent or how much time you took to do the work.
They are only measured in unit of tangible technical progress to plan. This tangible technical progress is defined BEFORE the work starts. This progress goal is derived from the time phased Measures of Effectiveness and Measures of Performance goals of the project.
These MOE, MOP, KPP, and TPMs are defined below and their measures - in units meaningful to the decision makers - established before work starts, put on baseline and used to compare progress to plan (time phased) to produce that Physical Percent Complete in the Earned Value (BCWP) formula in the first chart.
Unless we know what capabilities we need at the end of the project, and know those somewhere near the beginning of the project, have a Plan to produce those capabilities at the needed time for an anticipated budget, we're going to be disappointed in the result.
Identifying the needed capabilities is the first and most important practice for the success of any project. To achieve the project's objectives or a particular end state, we need to define these capabilities through Measures of Effectiveness. We can do this through scenarios from the customer's point of view. The effectiveness measures describe how well the results from the project enable a business process or fulfill a strategic mission of the business - in this case enforcing the will of the emperor. These measures must be in units meaningful to the decision makers. In the case Darth Vadar.
When we let those needed capabilities emerge we have likely disconnected the products of the project from the mission or vision of the business. Requirements can emerge to fulfill the capabilities. But the capabilities need to be steady and focused on mission outcome, otherwise we are just on a spend plan. We'll have no way to know what done looks like until the money runs out.
Here's an example of an increasing maturity of the capabilities for a health insurance provider network ERP system.
This approach is not usually found in traditional or agile projects. These approaches start with requirements, stories, features - all related to the technical aspects of the project. A Master Plan is developed that shows the needed capabilities (above), the order of delivery of these capabilities, and the dependencies between these capabilities.
The increasing maturity of the project's outcomes is then stated in this map. Technical requirements implement the capabilities, so they need a plan - schedule actually - as well. Small incremental capability delivery is the best approach. This is obvious and the basis of agile, but not always planned that way.
This plan contains all the steps (delivered capabilities) needed to increase the maturity of the of the project from the start. This does not mean we know how these capabilities are going to be delivered, but it does show what DONE looks like at the end of the project. In this example Phase 1 - Go Live.
This approach does not define any specific development process - agile or traditional. It is the basis of success for any development process.
Capabilities Are the Vehicle For Delivering Value
The Capabilities and their Measures of Effective need to remain stable over the life of the project. Without this reached DONE with any sense of budget and schedule will not only be difficult, you will be rubber banding the baseline used to measure your performance. You'll have turn a project into an operational activity. Projects have defined outcomes, defined periods of performance and associated budget. Operations can be fixed budget, open ended periods of performance, and emerging outcomes. But reaching a defined description of DONE becomes much more difficult.
The notion of successfully managing a project starts - as always - with the 5 Immutable Principles of project success.
So What's the Point?
If these principles are not in place on your project, it'll be a disappointment. So in the end any successful project management process must answer the following:
By the way, the common objections by some in the agile community to the notion of on-budget, on-schedule as a measure of project performance is seriously misinformed. Those paying for the project not only want to know these, they must know this. It's not the developers money. It's the customers money. They must know the final cost and the date when the project is done. They must also - of course - know that what is being produced delivers the needed capabilities. But having those capabilities late is not good. Spending much more than budgeted is not good. All three attributes are needed.
These numbers by the way are probabilistic. Every number on a project is drawn from a statistical process to produce a probabilistic outcome. The notion that NOT forecasting the future performance of cost, schedule, and technical outcomes can't be done is simply nonsense. Of course it can be done. You just have to remember the things you learned in your high school statistics class. Plus a few other things about probability distributions and confidence levels.
There have been several posts and discussions on LinkedIn about applying Earned Value Management to projects. This coming Thursday, I'll be talking about applying Agile software development processes to Earned Value Management project, but in order to do that we need Earned Value to be applied first. So let's look at how to install EVM on your project.
Let's start with some basics and get rid of the myths of EVM
So now let's look at setting up an Earned Value Management System at the highest level - the principles level.1. What are we building?
3. Master Plan and Schedule
4. Resouce Plan
5. Cost collection
6. Baseline Management
So Now We've Got an EVMS, What Do We Do?
When we have our Performance Measurement Baseline (PMB), the Integrated Master Schedule (IMS) with its seqeunce of Work Packages and work activities, with resources assigned to do the work and the budget to fund that work, we can start to measure progress to plan.
At periodic times - usually weekly, possibly bi-monthly, but for sure every month, we can assess the physical percent complete on the work. This means measuring tangible progress to a pre-planned set of attributes. With this measurement comes the physical percent complete. With the physical percent complete we can calculate the Earned Value.
With this measure we can determine where we are along the way to complete, how much we need to improve out performance, and what corrective actions we need to take to get back on schedule, or stay on schedule.
There's a post on a Deltek implementation partner site about applying Earned Value. It has some good advice, but the premise of the starting point needs to be addressed.
Before going on to suggest things to do on a project using EVM, it's best to have one of those don't do stupid things on purpose discussions. If the customer or potential customer is doing stupid things on purpose, it's important to stop those first, before attempting to make any other improvements. Once that is done, the core paradigm of Earned Value Management is very simple and obvious ...
Turning the Subjective into the Objective
This phrase is not mine, it is a colleague's who said it while we were walking down the hallway of a client site, who is introducing EVM to a $1.9B weapons program that has never had EVM before, but is now being mandated to do so by Congress!!!
So Here's the Introduction to What Not To Do and the Simple Fix
Let's start with a picture of where to start. The are 32 Guidelines in ANSI-748-C. 11 are needed for he success of any project, in any domain. If you aren't doing these 11 in some way, the probability of success for your project is low. This is the case of all project management and product development processes, These are like the 5 Immutable Principles - they have to be there in some way. Here's the 32 from ANSI-748-C and the 11 are colored and listed below.
So Let's See How the 11 Can Address Each Of These Issues?
Here's their list of reasons why Earned Value Management is not readily adopted by contractors.
So What Does All This Mean?
It means applying the 11 Guidelines shown above to your program is the same as being a credible program manager. If you're not doing these 11, you're probably not doing your job as a Program Manager on an EVM program. Think about that. You've been assigned to look after $20,000,000.00 of the governments money. Would you actually use some the phrases above when asked why you're doing a poor job of managing the program? Not for long I suspect.
One Final Comment
Earned Value Management is one of several enabling technologies to turn the subjective into the objective. But it is only a necessary condition for success. It is far from a sufficient condition for success. You need an Integrated Performance Measurement Baseline with these elements
Ray Stratton's news letter just arrived. There he speaks to the "44 Day Rule," for the duration of work activities. Some places use that for the duration of a Work Package. Other places use that as the duration of a work activity contained in the Work Package.
Here's another idea.
You need to answer the question - How long are you willing to wait before you find out you are late?
The answer to this question, then drives two things:
With the answers to these two questions, the duration of a work activity should now be self evident. As well as the point in time needed to take corrective action. This corretive must have enough time to have the lateness be fixed. So some arbitrary durations cannot be used. You need to know how the work is being performed.
But a simple (and simple minded) rule assumes the work is being performed linearly. So yuo can answer the question by saying, what is the capacity for work that must be applied to fix the activity when it gets behond schedule?
By the way, when this corrective action is applied, it will cost more money, unless you change the scope or improve the effectiveness of the work to cover the extra work needed to correct the problem.
This is why short duration activties are best. The Agile folks know this, maybe not for the same reason. But short duration tasks - the 44 day rule - force the assessment of work so corrective actions can take place.
How many legs does a dog have if you call the tail a leg? Four. Calling a tail a leg doesn't make it a leg
- Abraham Lincoln
The notion that we can rename things and then assume they are the same doesn't work, just like Lincoln said. The notion of measuring progress with the passage of time and calling it Earned Value, doesn't mean we're doing Earned Value.
Doing Agile without doing Scrum, XP, Crystal, or DSDM is not doing agile.
The LinkedIn forum The Project Manager Network - #1 Group for Project Managers which I sometimes wonder if that is actually the case, has a conversation going on around project failure. A Master's student asked about project failure modes. That led to the use of Earned Value. One participants made some pretty boneheaded statement around EV:
5% (2 hrs)for applying the border and title
20% (8 hrs) for defining the area - boundaries and overall dimensions
30% (12 hrs) for showing all the equipment
5% (2 hrs) for the drawing being checked
10% (4 hrs) for it being Issued for Approval
15% (6 hrs) for it being Issued for Bid
15% (6 hrs) for it being Issued for Construction.
100% = 40 hrs.
So, silly me, I responded that determining physical percent complete was a straight forward process once you have Quantifiable Backup Data or measures of Physical Percent Complete, or even better, Technical Performance Measures. Let's look at each concept
Then the final come back from the OP.
If you're doing a drawing and it takes 40 hours to do the drawing and no two drawings are alike, how do you determine what percentage complete you are? When estimates of the work to be completed are put together, they will estimate X drawings at 40 hrs/drawing. They will have different standards by discipline. Will a person ever report 41% complete on a drawing? Most likely not. It will be shown as 40%. Collectively all the drawings may be 41%, but not individual. No matter how you look at it, it is still an estimate.
First measuring progress to plan by the number of hours consumed is called Level of Effort. Second LOE is a very poor measure of anything other than the passage of time and consumption of resources.
In the end the poster was insistent that ANSI-748-B is just a guide, and doing EV was a local issue. No doubt that is true in his domain. But as a practitioner of EVM using ANSI-748-B for programs subject to DCMA Validation, as well as engagements with the DOD office that own the Earned Value Management processes for the DOD, I'd be laughed out of the room with an approach like that.
For a summary Earned Value in a Nutshell using a similar drawing example.
So Here's The Way TO Do Earned Value
That's all there is - essentially - for doing Earned Value Management. Of course if you read ANSI-748-B, the NDIA Earned Value Management Intent Guide, and the DCMA Intent Guide, there is a lot more.
You Can't Make Stuff Up
OK, you can. But if you do, it makes having a conversation about EV much harder.
When I encounter a "subject matter expert," I've now learned to assess if this person is a "knowledge holder," or a "learning individual." This is what informed that "learning." This came to my from a friend and neighbor who is a graduate of the University of Chicago in economics and spoke at this conference.
In our business - project and program management - there are lots of "knowledge" providers, assessors of knowledge, frameworks for measuring our knowledge. What is needed now is how to learn to make better decisions about our projects. This is not going to happen without a decision making framework for the core principles, practices, and processes for project management. The current Bodies of Knowledge, self-proclaimed providers of better BOKs and assessment tools, authors (I'm one of them), and experts in the field, all need to reassess what we are doing to increase the Learning abilities, beyond the just the possesion of knowledge and the dispensing of this knowledge to others.
How can we actually learn to improve our probability of succes. The Decision Scientist for project success - as suggested here - needs to have art, science, and the scale to provide actionable information for the decision makers for the project.
We have most of the data we need, what we don't do is make decisions on this data, or even know how to make decisions with this data. We report it, but don't use it to make decisions. Numbers matter, but leadership needs to use the numbers.
Forecasting involves making projections about future performance on the basis of historical and current data.
The chart below is a synthetic (same as fake) Cost Performance Index at the program level 2½ years. The area on the right is the forecast of possible values of the CPI given the historical behaviour, with tuning parameters and smoothing functions.
The next step is to use real program performance data over some realistic period of time - say 4 year - and use H-W (or a similar forecasting tool), to confirm that a less that complete assessment, say take 2 years of data, forecast a 6 month value, and see of the actual 2 year, 6 month value come out close the to the forecast.
This is all done in R, with very simple commands, once the time series for the CPI is formatted and partitioned properly.
Shim Marom has a nice series of posts about Earned Value. It this post he provides the calculation of Earned Value, or Budgeted Cost for Work Performed.
BCWP = BCWS x Percent Complete
Shim, then mentions that many times it is difficult to determine Percent Complete.
Here's where to start
This approach is independent of applying Earned Value. It should be used for all project work.
Below are the other measures of performance.
So when asked what is the percetn complete, take out the KPP's and TPM's and look at your delivered product to see if it is compliant with the planned values? Do ot weigh the proper amount for this point in the project, Does it go fast enough? Does it have the planned reliability? Can it process the transactions properly at the right rate. Does it provide the planned storage capacity.
Does it do what you planned it to do on the planned day you said it would, for the planned budget?
That's how you determine your physical percent complete. Here's a way to lay out those high level measures that will show where you need to assign these measures
Came across (through Google agent) a nice short description of what is Earned Value. It's from a British construction firm. The phrasing is a bit off for our domain, so I'd like to clean it up. Let's start with a simple and s imple minded project.
Earned Value has three components for our project:
Notice the at the time of assessment statement. This is critical. If we plan to spend $1,000 as the total budget for the work over a 4 week period, this is the Planned Value, the Budgeted Cost for Work Scheduled or BCWS. This is the budget to produce our outcome. When we assess the performance of our efforts, we do that at a point in time. This point has a cummualtive budget and we need to assess our cummulative performance, and our cummulative actual costs all at the same time.
At the half way point (week 2), our plan says we should have spent 50% of our budgeted cost (BCWS = $500 at this point in time). This is naive of course, but makes our calculations simple. This means that after 2 weeks of work, we planned to have spent $500.
We assume - again naively - that over the course of the 4 week, the ACTUAL value of the product - the drawings - we are producing is growing linearly. So at the 2 week point, our product should be worth 50% of the Planned Cost or $500. This is the Earned Value. We essentially earn our budget in this simple minded example.
So now the 2 weeks has come, it's Friday of the second week of our 4 week deliverable. We planned to spend $500 and to earn $500 of value. At our status meeting, here's where we are:
During those two weeks, we spent $50 per drawing on the first 7 drawings, just like we planned. But on the 8th drawing we spent $70 because it was harder. Which is also the reason we didn't get to finish the 9th and 10th drawings. So for the first 7 drawings that were produced we spent (7 x $50) and for the 8th drawing we spent $70 for a total of $420 for 8 drawings.
Now we can compute some indicies
So let's do some claculations using Earned Value formula.
That's all interesting, but the real value in Earned Value is the ability to forecast the future. The first forecast calcualtion is our Estimate At Completion. This our estaimate of how much this project is going to cost when we are do, if we don't change anything
But that's not the real problem, let's see how late we are going to be.
Here's the quick summary:
So what can we do?
This is what Earned Value can tell us. No other method can do this.
This is the Value of Earned Value
It is common in the Agile world and other domains at times to state that Earned Value. One example of this misunderstanding comes for a site I had not heard of before.
Here is the descriptions used for an "Agile" project management method.
The description of Earned Value goes like this
Nope, This is Not Earned Value
The three variables of Earned Value are
So where did the author of the post go wrong?
In fact if you're doing agile and doing it right, Earned Value provides little value (so to speak). However, if you doing Earned Value projects, and want to add Agile, that is straightforward. Here's how.
In the end "earned value" can make use of Agile. But "earning" the value is NOT the measure of the passage of time and consumption of money or resources, as suggested by the poster. It is the measures of the "value" produced by the consumption of resources and passage of time.
That is if we invested $100 and did that over a week, did we get a $100 in value from that investment? A simple way to calculate that measure is to ask what percent complete were we at the end of the week?
If we were only 90% complete, when we had planned to be 100% complete, but had spent out $100, then we are only 90% of our planned schedule progress, but are 100% of our planned budget. So we are 10% late and 10% over budget.
Trending is a critical tool in forecasting the future performance of a project. "We've be doing this well for awhile now, what's going to happen in the future?" is a very common question for project management to ask of the "project controls" staff.
Two indices in Earned Value are the Cost Performance Index (CPI) and Schedule Performance Index (SPI). They are calculated from the Earned Value Management numbers of BCWP (Budgeted Cost of Work Performed), BCWS (Budgeted Cost of Work Scheduled) and ACWP (Actual Cost of Work Performed). This post is not about Earned Value, but about statistical analysis of Earned Value numbers. You can find good tutorials on EVM in several places, including A Gentle Introduction to Earned Value.
What is critical is the forecast for where the project is going with the information from the past. In the standard approach static information is used to compute a forecast of the future. This information is a cumulative measure of CPI/SPI for all past periods and the current period of performance. Together these are used in a linear formula to forecast future performance - again in a linear, non-probabilistic manner.
All of this has lead me to think about the probabilistic processes needed to improve the credibility of project performance measures. I discovered through our BioChem son, the programming system R. R is a functional programming language and system for statistics and probability.
Along with R the US DOD has rolled out an XML format for capturing the monthly Integrated Performance Management Report. The time series of CPI and SPI are available monthly in electronic readable form. With this data forecasting using R and the myriad of tools can be done.
Using a simple functional command line,
will produce a nice picture of the time series data with forecast value at defined confidence levels.
The problem to be solved is simple:
Mathematically this means that what drove the variances in the past is assumed to no longer be driving the future. Those sources of variance are washed out. This may be the case from corrective actions for the Epistemic uncertainties (uncertainty due to lack of knowledge). But the Aleatory uncertainties (uncertainty due to randomness or luck) that drive the variances are not subject to corrective actions. They are baked into the system and no amount of new knowledge or corrective effort is going to make them go away.
This is simply bad data analysis in any discipline I've ever worked, except program controls.
This idea started with Eric Ducker's paper and presentation at ICEA titled, "Performing Statistcal Analysis on Earned Value Data."There are some other sources as well:
There is a class of responders on the forums that continue to seek simple and simple minded solutions to complex problems. Claiming the problems can be solved with simple solutions. Of course those solutions cannot be demonstrated with any credibility outside of a limited domain. Let's start with Mencken
For every complex problem there is an answer that is clear, simple, and wrong. - H. L. Mencken
In the project domain most of the problems start with poor estimates of cost and schedule. Hollmann starts it off http://lnkd.in/vjf4X4. Bent Flyvbjerg takes a more radical view, calling estimators liars , but I chalk that up to a language barrier.
The core problem starts with the politics of estimating. Rarely do the buyers of the project know what it should cost. So when they hear a number that is larger than their expectations, they reject the number. They signal to the sellers what they expect to pay for something. This expectation can come from poor knowledge or simply a naive understanding of the problem, or worse a public promise that simply can't be kept.
But a second problem exists. That across domains, there is the wrong headed belief that one domain has the solution to another domains problems. We need to break the loop we're stuck thinking that problems are only found in other domains and making the ill-informed suggestions that "if you just did it my way," there would be no problem. There is a fundamental issues with managing complexity and managing in the presence of uncertainty. We want it to be simple, it is not, but since it is hard, people don't want to actually work hard on the solution. Instead seeking simple and may times "simple minded" solutions - buy this tool, use my excel spread sheet, dumb down the processes.
So What Is The Solution
First is to recognize that ALL domains have similar problems. Cost and Schedule estimates have been discussed for many decades. Lots of literature leads us back to the singular source - the political will to search for the credible estimate, even if that means not starting the project. Or better yet, to start the project knowing the estimates are flawed.
One provocateur voice in our community suggests that PMs that take on project with poor estimates should be held criminally liable for the results. This of course is laughable, but it demonstrates the complete understanding of the problem and the solution.
This approach reminds me of Pauli's quote when presented with a nonsensical submission from a student.
They were worse than wrong because they could not be proven wrong. Famously, he once said o: Das ist nicht nur nicht richtig, es ist nicht einmal falsch! "Not only is it not right, it's not even wrong!"
Thus is where we are now. Not much in the form of research and questioning, lots of pontificating about how the other guy is all messed up, and if you'd only do it my way, you'd have your solution. Reminds me of the current US political problems. Do it my way. Of course that doesn't work, because we have complex - wicked - problems, and there is no single way. Mencken was right, and he was right long before any of the current problems.
We may be doomed to repeat history with first recognizing the problem is us.
Shim Marom has a great blog post about a conversation around using Earned Value Management. The exchange is typical of those not starting with the Project Controls paradigm for managing projects. I attribute this typical exchange to missing information about how projects get to be successful. PMI has not done a good job around project controls, AACEI lives and breaths the notion, Agile has something to say, but leaves many gaps, and most of the ad hoc approaches to managing the expenditure of other peoples money in pursuit of a product have little to say.
It's been said before, but Shim's post needs as many voices as possible. If we want to show up on or near the planned time, at or near the planned budget, with something that has a hope of working, we need a method of planning work and controlling cost.
Here's are 11 activities that contribute to that goal on the non-technical side of the project. The odd numbering system will be revealed at the end
1. Define the deliverables – what does the customer want? Do we know this at a level of detail so we and the customer will recognize it when it arrives?
2. Define who is going to produce these items – do we have the people needed to produce them? Do we know the skills needed to do this work? Do we know something about how this work effort is going to be organized?
5. Put these two thing together - so the people on the project know who is doing what. Who is accountable for producing the outcomes of the project? How will they communicate this to the customer?
6. Plan the sequence of work – so everyone is not doing anything and everything out of order. Einstein's quote that the purpose of time is to keep everything from happening at once is applicable here.
7. Define when you need things to be produced – what day do I need something? The order of the deliverables is usually important to the assembly of the parts of the product. Spoilage is actually an issue when developing software, since emergent requirements many times result in rework.
8. Figure out how much money you’ll need for producing things – do we have enough time and money to produce what was asked for at the time it is needed? If you're spending other peoples money, you'll likely have to explain how much money you need and when you need it. Open checkbooks are rare these days.
16. Capture how much you spent – who spent what on what outcome at what time? The people giving you the money, will probably like to know what you spent it on.
23. Determine if there is a difference between what you planned and what you spent – why did we not follow our plan? When spending other peoples money, they like to know you've got their interest at heart. This can be done with a budget versus actuals discussion. Just like any business process (or even in life), having and budget and trying to stay on budget is a demonstration that you're trusted to spend the money.
25. Add up all these variances – do we have enough time and money remaining to do what the customer wants? This is a quetsion you probably ask yourself every month as you're paying bills. Same goes for managing other people's money on your project. The surprise of we have no more money (or time) is unpleasant in all circumstances.
26. Take action to stay on budget and schedule – either way, yes or no, what should we do about it. If we're on budget and on schedule, what do you need to do to keep it that way? If you're off budget or schedule, what are you going to do to get back?
28. Implement you actions – with the knowledge from #26 do it, Project Management is a verb, do something about the variances.
These 11 activities are simply good project management. These are what project managers should be doing on the Programmatic side of the project. The Technical management of the project can be done in a variety of ways, and of course they will influence the programmatic side. Add to that the people management and you've got the picture of what a project manager should be doing.
By The Way these 11 activities are numbered from the 32 Guidelines of ANSI-748-B - Earned Value Management. So when you hear someone say - we can't do EVM on our project or EVM is a waste of time in our domain usually spoken by the IT folks and even by the senior thought leaders of IT, ask yourself - are these 11 activities missing? If so, what's the chance your project is in the ditch and you don't even know it?
The domain we work in is unique in some ways compared to the general roles of a Project Manager. First is the "management" of the project or program is done by a specific set of people. The Program Manager and the Control Account Managers. The "program controls" function provides oversight and insight to those people.
There are specific roles on the PP&C (Program Planning and Controls) side of the program. Here are the questions we ask when interviewing someone for that role:
Planning1. Integrated Master Plan
2. Integrated Master Schedule
Earned Value Management
3. Control Account Plan
4. Work Package
5. Earned Value Execution, in you experience ...
Monitoring and Control
6. Performance Measures
7. Performance Reporting
8. Duration Estimating
9. Technical and Programmatic Risk Management
10. Critical Path Analysis
11. Building the IMS
12. Microsoft Project Demonstration
These and similar question will bring out the level of experience on the PP&C side of the project. These of course are not related to the other aspects of "managing" the project. But when someone says, "I've got experience managing projects," this is one place to start to see if "providing performance visibility" to the project has been one of those experiences.