The Future of Software Analysis and Measurement : Expert Panel Questions & Answers
Here are some of the questions that were answered after the webinar with Bill Curtis, David Herron, and Dan Galorath. They were answered on Cast software’s Facebook page.
What about aerospace component level software and how would you apply a cost factor their complexity factors?
What is IFPUG Back Fired Points, how does it help?
Daniel Galorath Backfiring means counting lines of code then using a number of lines per function point to approximate function points. I think it is much better than nothing for a finger in the wind. Many others in the industry object strongly to it.
Another question – What type of information is needed to start using a software analysis and measurement tool?
Bill Curtis First you need to know how you want to use the results. That will help you establish criteria for evaluating which of the various tools best meets your needs. The Goal-Question-Metric paradigm is a good guide for determining what your measurement needs are.
Here’s another question from the webinar – Would like to understand how we can improve our ability to capture metrics (defect density either using effective loc and or functional point) for applications that rely heavily on database’s where the logic resides – e.g to map biz rules existing in table rows/columns etc?
Daniel Galorath Generally you would count the work involved in building the database, not the entry of the data into the database itself. SEER will provide estimates of defect density, etc. From my understanding CAST can provide measurement of this.
What is the panel’s opinion on LLOC to FP translation such as QSM language by language table which they developed from their database.
Do you have to have a technology inventory?
How do you extend the IT governance to software suppliers? what requirements to pose to them?
Bill Curtis Customers are starting to write measurable quality targets such as robustness or security targets into their outsourcing contracts as the equivalent of service level agreements. They then establish a Quality Gate where all software received is measured and evaluated before being put in operation. If the supplier’s software falls below the quality target they must remediate the code or face a financial penalty.
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.
DoD Affordability: Implementing Directive For Ash Carter Initiative
A lot of people are interested in DoD’s initiative for improving affordability, often referred to as the Ash Carter memo. Here it is from NDIA and others: “Implementation Directive for Better Buying Power: Guidance for Obtaining Greater Efficiency and Productivity in Defense Spending,” issued by Dr. Ashton Carter, DoD AT&L, concerning implementation instructions for a series of measures aimed at improving efficiencies and reducing costs in support of Secretary Gates’ Efficiency Initiative. This directive and guidance are effective immediately.
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.
Capers Jones, Gary Gack, Leon Kappleman, Dan Galorath Team Up To Improve IT
From the consortium web site:
Information Systems Risk Management Consortium Charter
Written on January 28, 2010 at 4:25 pm, by adminThe consortium is the result of four of the industry’s leaders (Capers Jones, Gary Gack, Leon Kappelman, Dan Galorath) deciding to pool our expertise and form a consortium called the Information Systems Risk Management Consortium for the purpose of offering our combined talents to assist the information systems industry. The process improvement results we’ve achieved with other diversified government and industry organizations and large distributed companies has convinced us we can help you accelerate your strategic initiatives while improving tactical performance with measurable results within a 6 to 18 month calendar window.
Our experiences can help your teams identify and reduce the potential risks earlier in the project life cycle. In most cases the problems and failures are avoidable if you know what to look for, what to do about them, have repeatable processes, appropriate practices, and utilize independent expertise like ours both before and after contracts are awarded. Federal Government organizations a world-class companies often lack the necessary in-house expertise to ensure success in these high-risk, complex, multi-year initiatives. Independent specialists with world-class experience and capabilities can provide the critical differentiator needed to manage successfully large high-risk projects.
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 the Costs and Benefits of Software Process Improvement
I recall, some years ago, participating on a source selection for an improved software development environment. My part was essentially to assess the costs (personnel, time, etc.) and the benefits (increases in productivity when the new software development was deployed.
Interesting work and right up SEER’s alley. I looked at improved development tools and development practices and cost reduction versus the costs and temporary reduced productivity.
Watts Humphrey of SEI published a document on costs and benefits of software process improvement that is worth review.
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.
A Business Imperative for Change From the Taskforce on Defense Acquisition Law and Oversight
This document analyses Government Acquisition Reform and was developed by a business task force including a who’s who of American technology business and government. It is very relevant to those concerned with DoD acquisition costs. I have included a few quotes and conclusions here to give the reader a flavor of the document.
“I reject the notion that we have to waste billions of taxpayer dollars to keep this nation secure.” —Barack Obama
1. Requirements need to be iterative
“Higher costs, whether based on low estimates or poor enterprise management, is unacceptable and harmful to the defense enterprise.”
“While the shortcomings of defense acquisition are manifold, the issue that has drawn by far the greatest criticism to date is the high cost, and cost growth, of the products it produces. Simply stated, we are on an unsustainable cost trajectory.” —John Young, former USD (AT&L)
Adherence to program execution processes aimed at satisfying the needs of the war fighter is essential: with resources to address contingencies, with proven technology, and viable poor estimates of production volumes. Programs should be funded when:
1. the requirement is clear (And requirements should be iterative);
2) funding is adequate, including reserves, is available
3) the technology is proven
4) the system concept is well-defined
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.
Software Engineering Body of Knowledge from IEEE
The 2004 Software Engineering Body of Knowledge is available at no cost from: http://www.computer.org/portal/web/swebok/htmlformat While it doesn’t focus on estimation, planning and control, it is a valuable resource for software engineers. There will be an expanded 2010 version coming out as well.
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.
10 Biggest IT Development Money Wasters
From Justin James and Techrepublic: IT Development Moneywasters
#1: Communication problems
#2: Process issues
#3: Refusal to go live and iterate (aka: insistence upon perfection)
#4: Penny wise, pound foolish
#5: Outsourcing missteps
#6: “The Longest Yard” (documentation and user training)
#7: Developers used as support staff
#8: Poor foundation for development
#9: Fail to know the business
#10: Neglect to calculate project ROI
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.
Estimation Plus Process and Measurement Rigor Yields More Successful Projects: SEER and Tracer
It has been rewarding working with the Computer Aid (CAI) people, the people who sponsor the ITMPI in tying together best practice approaches (SEER for Estimating, Planning and Control and Computer Aid’s Tracer for metrics, reporting and root level management). I am always inspired when I hear the CAI people explain their process and success in fixed price software development and maintenance. They do it by a number of methods and processes. But the one that always makes me the most excited is their Tracer software. Tracer allows root level tracking of tasks and progress, providing near real time feedback regarding project health and status and individual task performance. I think it is wonderful that they have made their solution available to the industry at large. It is much like the factory floor real time feedback in manufacturing, applied to software. From CAI’s web site is the following description which describes estimating effort, cost, and process tracking.:
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.
Government IT Projects: Opportunity For More Success
I heard of a wonderful blog on Zdnet regarding additional oversight and transparency in Government IT projects costs, schedule: S.920 the Information Technology (IT) Investment Oversight Enhancement and Waste Prevention Act of 2009.
The bill is targeted to prevent issues:
1. cost overruns and schedule slippage from the estimates established at the time the program is initially approved
2. Number of requirements and business objectives at the time the program is approved that are not met by the delivered products
3. Number of critical defects and serious defects in delivered information technology.
The bill requires specific items be available on project performance including:
-
Cost, schedule, and performance using Earned value (ANSI-EIA-748-B)
-
Project Trends
-
commencement of the project;
-
Variance from cost, schedule or performance & rationale
-
Number of times projects are re-baselined
This can really help, if done correctly. ” When Performance Is Measured Performance Improves, When Performance Is Measured and Reported the Rate of Performance Increases”
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.
Final Version of the GAO Cost Guide
It appears that this is the final version of the GAO cost estimating guide which provides guidance on preparing viable cost estimates both early in the process and throughout the life cycle. Congratulations to the team. This is a great contribution to the industry and can, if used as intended create more successful projects. I especially appreciate the focus on preparing a viable estimate of cost, schedule, etc. then applying earned value management (EVM) to that. So often, in the past we have seen a chasm between those that generated estimates and the EVM people. These are two sides of the same coin. The introduction 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.
Project Prediction Infographic
