Showing posts with label dashboarding. Show all posts
Showing posts with label dashboarding. Show all posts

Monday, May 28, 2012

Proportionality in controls

Early identification of the 'pinch' points and putting more effort towards controlling those elements is, in my opinion, time well spent.


In the example below, we're 5 months in on a project, the customer isn't too sensitive to cost, but is extremely sensitive to delays.






































Doubtless there are a few ways of tracking quality. I've often thought that if you're handing over  project deliverables sequentially, CPI and SPI sort of give you a 'QPI' or quality performance index since your customer is signing off acceptance of products as you go. 


With IT projects you do involve the customer in test and review activities throughout the design and development work, but sign-off tends to be a bigger bang type activity. The PM of any IT project needs to be fully cognisant of the customer's wants, needs and any deficiencies as an ongoing process. This activity is encompassed within testing and defect management.


I'll do a post at a later date on the range of metrics relating to defect management which I like to capture but here I've singled out something I've always been very keen on. See the bottom of the three charts above. Something not entirely clear is that that the graph isn't cumulative. Each month the number of defects identified that month is plotted against the number of defects fixed that month. At a glance, this shows whether or not you have an unsustainable, worsening or improving state with regard to defect identification and resolution.

Note the control charts above, not only are these easily maintained and communicable, they illustrate trends and the tolerances to which the project is expected to adhere. Incidentally, I'm a fan of publishing this sort of material directly to the project team - it encourages shared ownership and good alignment of decisions throughout the project team.

As can be seen above we've got more tolerance on cost than time. Take the cost (CPI) plot, we went from a good start, to holding steady, followed by three consecutive periods of deteriorating performance. With the benefit of hindsight it would have been useful to have a more frequent reporting interval - if we'd had fortnightly reporting - somewhere between month 2 and month 3, it would have become apparent that corrective action was required, and consequently far more easy to justify.

While the time (SPI) plot serves to illustrate this point very well, what we could have seen in advance was the very limited tolerance on schedule would have benefit from more regular reporting for precisely the reason above. The emergence of a trend would have happened far more quickly.


These sort of indicators are one approach to helping ensure that within any given project, benefits are maximised and risk is minimised. The best indicators are those that inform timely decision making before things go off the rails, not simply reporting on the fact that they have.



Sunday, April 29, 2012

Turning data into information with earned value management

While a firm believer in earned value management I have a confession to make. I've never joined a project or programme in which earned value management is in use. Either within my specific work stream or any other that I have been able to get sight of. I estimate there are potentially three likely reasons for this.
  1. There is no requirement to track cost or schedue performance in fine detail
  2. There is no capability or inclination to use earned value management
  3. There is no market for the specific outputs of earned value management
I might be able to help with number three.

I'm a fully paid up member of the Association for Project Management (APM). The APM has several publications and its Earned Value Management Guide is (I think) one of the most thorough and clear pieces on the topic by anyone anywhere.

The document covers a great deal of material but I include here what was, for me, an entirely novel approach to illustrating earned value - namely the bullseye chart. See below.



Now, for earned value advocates I appreciate that some of the trending and intuitive extrapolation is less apparent. However, for sponsors and stakeholders not well versed in earned value management, I think its appeal is self-evident.

Equally once the initial spreadsheet is assembled, it uses precisely the same data as traditional earned value charts so really, its very little extra effort.

I owe a huge deal of credit to Jon Peltier of peltiertech.com, an MVP with superlative Excel knowledge for providing a step-by-step on his site for how to create a bullseye chart. It is remarkably finicky. You'll be pleased to know, I've saved you all the hard work by including an Excel file here which you're free to use.

I believe it's possible to add date markers to the series labels on the graph which I think would be an enhancement. And for those of you with an appetite for such things, you could publish this via Excel Services in SharePoint and, using external data sources for the bullseye chart, have a real-time dash board for all your projects.