Galorath / DCG IT Estimation For Business Value and Project Success Clinic
Here are the slides from the Galorath / David Consulting Group estimating clinic  held in New York City. There were interesting discussions encompassing dealing with impossible demands, understanding risk and risk management, sizing, and a number of other topics. Note: The Galorath slides and the DCG slides are combined in the one PDF file.
Concepts of IT providing business value to the organization were also discussed in detail.
Thanks to all who attended and especially to Mike Harris and David Herren for their insights.
Thank you for reading “Dan on Estimating”, if you would like more information about Galorath’s estimation models, please visit our contact page or call us at +1 310 414-3222.
Computing the Value of Incomplete Software
IBM’s Murray Canter published an interesting article in the communications of the ACM covering calculating and improving the ROI in software systems.  Murray shows how to compute the “investment value” of incomplete software and illustrates why it does have value showing how to compute the net present value and the return on investment of this in process work, using Monte Carlo simulation. Murray states two axioms:
- Costs and benefits occur over time, so their present values are found through NPV equations
- The future values of costs and benefits are random variables, described as a statistical distribution
I should note this requires a subscription to ACM digital content.
Its abstract states:
“Constrained by limited budgets, most enterprises find it essential to apply unprecedented business discipline to the business function of software and system delivery (SSD) across entire software and system life cycles. For this reason, the CIO, CTO, or VP of software or systems development may be under increased scrutiny from the corporate chief finance office (CFO). When conversing with the CFO, money talks, so only one of two sorts of conversations can take place: software and systems as cost center or software and systems as value-creation center.”
Thank you for reading “Dan on Estimating”, if you would like more information about Galorath’s estimation models, please visit our contact page or call us at +1 310 414-3222.
Measurement and Providing Value to the Business ISMA Keynote 2011
Here is a copy of my keynote talk at the 2011 ISMA measurement conference, Measurement and Management and Business Value. The real point is the IT and measurement personnel have the information, knowledge and skill set to provide value to the business, far beyond the costs generate. But the information needs to be communicated in terms leaders can understand rather than the techie language we all think and speak in… AND if IT starts showing how it contributes to the business and becomes a profit center instead of a cost center IT will get more money to apply to more valuable things.
UPDATE: Someone also asked for a reference communicating the language of management. I believe this publication on business case analysis to be helpful in that regard.
PS In my talk I referred to software and measurement people as geeks. To many the term geek is a source of pride. One person in the talk was offended by being called a geek. My sincere apologies. However modern vernacular often defines a geek as a lover of technology, a software developer or someone with an intense love of mathematics. I consider myself a geek. And my friend Paul Glen makes his living by “leading geeks.”
Thank you for reading “Dan on Estimating”, if you would like more information about Galorath’s estimation models, please visit our contact page or call us at +1 310 414-3222.
Galorath Keynote ISPA March 2011
Today my conference presentation involved understanding and estimating value in software and IT systems as well as total ownership costs. It still amazes me how so many software and IT leaders do not want to think in terms of Return on Investment but just want to build things that seem to be good ideas. If we would build what has the most value IT could become a profit center. Key points were:
- Estimation is a key portion of business decision making
- Value must be considered in addition to cost
- Data doesn’t have to be perfect to be useful
- Estimators taking some responsibility for business value analysis can make a major improvement in business
Â
I have included entire PowerPoint presentation here.
Thank you for reading “Dan on Estimating”, if you would like more information about Galorath’s estimation models, please visit our contact page or call us at +1 310 414-3222.
Estimating Best Practices
The following are the bullet points from Dan’s paper on estimating best practices. Â Using these best practices can increase project success dramatically.
- Decide Why You Want An Estimate
- Map Estimation Goals To Estimate Process Maturity & Develop Plan To Achieve The Maturity
- Have A Documented, Repeatable Estimation Process
- Evaluate Total Ownership Cost; Not Just Development
- Estimate A Range And Pick A Point For The Plan
- Re-estimate The Program When It Changes
- Avoid Death Marches: Programs With Unachievable Schedules Are Likely To Fail And Drain Morale
Thank you for reading “Dan on Estimating”, if you would like more information about Galorath’s estimation models, please visit our contact page or call us at +1 310 414-3222.
Possibilistic Versus Probabilistic Estimates
I was in a cost task force meeting this morning, looking for ways to improve cost analysis in outsource environments, both from the customer and the offerer sides. These have been interesting meetings in many regards. Today the discussion focused on outsourcers who provide a low estimate, looking for the best case to win the business rather than the most probable cost.
One of the panel members pointed out that some outsources bid “possiblistic” prices rather than probabilistic prices. Possibilistic estimates are possible, if everything goes right, but everything going right is not probable.
That is one of the reasons SEER provides a range in addition to likely costs & schedule.
We recommend planning for the probable, not just the possible.
Thank you for reading “Dan on Estimating”, if you would like more information about Galorath’s estimation models, please visit our contact page or call us at +1 310 414-3222.
Viable Software Estimation Modeling: A Key Component Of Software Risk Management
I spoke with someone recently who explained the reason they use SEER is for risk management. They pointed out that not only can they determine the risks of schedule, effort and reliability, but the whole of SEER allows them to do risk reduction. A process improvement: no problem, a quick trade off is performed by setting the appropriate SEER parameters for process improvement, process experience, development tools and practices and they can see exactly what to expect, both good and bad. Then when asked to justify the result he can state explicitly: this includes reduction of team experience with processes, the process improvement going on during this project, any tools being deployed in the process improvement effort and the anticipated cost / benefit.
And for projects that are not challenged with new and different challenges, knowledge bases do the job without needing to concentrate on parameters.
Thank you for reading “Dan on Estimating”, if you would like more information about Galorath’s estimation models, please visit our contact page or call us at +1 310 414-3222.
Don’t Hide Uncertainty: Measure It
We all need to deal with estimates / projections for the future. When doing so, it is essential to include analysis of uncertainty and sensitivity of the variables including:
- Most important assumptions in the result
- Sensitivity of those assumptions (what happens if the assumptions change; which assumptions are most important in controlling overall results?)
- Probability of the estimate
- Risk Analysis showing the impacts of potential risks
Without risk, I don’t believe one has a viable estimate.
Thank you for reading “Dan on Estimating”, if you would like more information about Galorath’s estimation models, please visit our contact page or call us at +1 310 414-3222.
Controlling Software Projects: Development Is Only Job One: Chicago SPIN Nov 12 2009
Dan will be speaking at the Chicago SPIN on November 12, 2009 on the topic of controlling software projects. Estimation, planning, control, metrics, and maintenance for a total ownership cost view will be discussed.
The presentation is here: Chicago SPIN November 2009 Galorath Presentation Controlling Software Projects Development Is Only Job 1
PS Dan looks forward to his short visit to Chicago, his home town. And is going to carefully avoid pizza, hot dogs, and Italian beef while he is there.
The flyer follows:
Thank you for reading “Dan on Estimating”, if you would like more information about Galorath’s estimation models, please visit our contact page or call us at +1 310 414-3222.
Joint Confidence Level Solution By Galorath
Congratulations to Galorath’s Chris Hutchings and Denton Tarbet and MCR’s Steve Book for their approach to NASA’s joint probability challenge. Chris worked all weekend and had it nailed by Monday. Then he saw the papers from the prior week’s NASA 2009 cost symposium on Monday. Steve Book had independently come up with the same approach.
So while perhaps Denton and Chris can’t claim to be first to publish it, they can claim to be creators of what appears to be one of the winning approaches to joint confidence level.
Hats off to all three, and to the others who presented approaches to joint probability at the NASA Cost Symposium.  There were a number of other excellent solutions presented at the NASA symposium.Â
And other risk gurus at Galorath and elsewhere are studying even more effective solutions.
Thank you for reading “Dan on Estimating”, if you would like more information about Galorath’s estimation models, please visit our contact page or call us at +1 310 414-3222.
Project Prediction Infographic
