Early project decisions, when not much is known, are easily the hardest. They're also often the most critical. Maybe you've found yourself in a position where you need to communicate to stakeholders what your work is going to cost and how long it will take to deliver. Feeling the pressure to deliver, you might have to make decisions based on gut feel instead of past performance. This can lead to setting unrealistic targets and often results in projects going late or over budget. 

At QSM, this is when we recommend turning to historical data. Whether it's your own data or trendlines from the 13,000 validated projects in the QSM industry database, leveraging actual completed projects can make your estimates more reliable. 

Believe it or not, collecting your own project history isn't as difficult as it sounds. We recommend capturing just a few basic metrics: Functionality Delivered, Total Effort, and Total Duration. Once you have this information, you can calculate a Productivity Index, which is the measure of productivity for the overall project or release. Then all of these metrics can be leveraged by any of the other project lifecycle tools in the SLIM-Suite for estimating, tracking, and benchmarking.

In the video above, you can see how easy it is to gather your own completed projects to use early in the planning process and determine if your estimates are reasonable or not. This helps you understand the big picture before you make any important project or portfolio decisions. 

How large is your project?
It’s projected to cost $2,000,000.
That’s cost. not size!

How large is your project?
We believe it will take 14 months to complete.
That’s schedule, not size!

How large is your project?
It’s going to be a 25-person project.
That’s staff, not size!

Software estimators often think of project size as what a project produces (features, stories, requirements, function points, or code). These are what a project has to create or account for in order to fulfill its mission. Business leaders, understandably, are more likely to visualize project size in terms of resources expended (cost, time to market, or FTE staff).  These competing definitions of “size” can produce confusion and ambiguity. Which leads us to Tip #1.

Tip 1

Be prepared to explain to business leaders how quantifying project size (as seen by an estimator) helps business leaders get more accurate estimates of the things that matter to them: cost, schedule, quality, and staffing. I find a graphic like the one below from SLIM-Estimate can be useful to illustrate the relationship between a project’s size (primarily of interest to development staff and project managers) and the major project management metrics of interest to the C-suite.

Background

No two software projects are exactly alike. So, one way to find out what a “typical” software project looks like is to take a large sample of completed projects from the QSM historical database of over 13,000 completed software projects and look at measurements of central tendency for staff, effort, size, schedule duration, and productivity.

For this study, QSM looked at validated projects that completed beginning in 2010. We eliminated 1 person projects and those that expended less than 1 person month of effort. The eliminated projects accounted for 13% of the sample. About 80% of the projects fell into the Business IT application domain, many of which were from the financial services sector. This domain includes projects that typically automate common business functions such as payroll, financial transactions, personnel, order entry, inventory management, materials handling, warranty and maintenance products. We determined both a median and an average for each metric. With the exception of schedule (project duration), these differed significantly which indicates that that the sample metric values were not normally distributed. To minimize the effect of unrepresentative projects (those that comprise a small part of the sample, but whose metric values are very large or very small), we decided to use the medians – values with 50% of the projects above and 50% below the “average” as a better measure of central tendency.

The "Typical" Project

If you were unable to attend our recent webinar, "How to Estimate Reliability for On-Time Software Development," a replay is now available.

Software development is a major investment area for thousands of organizations worldwide. The negotiation and early planning meetings often revolve around major cost and schedule decisions. But one of the most important factors, reliability, often gets left behind in these early discussions. This is unfortunate since early reliability estimates can help ensure that a quality product is delivered and predict if it will finish on-time and within budget. In this webinar, Keith Ciocco shows how to leverage the QSM model-based tools to estimate and track the important reliability numbers along with cost, scope, and schedule.

This presentation includes a lively Q&A session with the audience and covers such topics as:

On Wednesday, Dec. 8 at 1:00 PM EST, Keith Ciocco will present "How to Estimate Reliability for On-Time Software Development."

Software development is a major investment area for thousands of organizations worldwide. The negotiation and early planning meetings often revolve around major cost and schedule decisions. But one of the most important factors, reliability, often gets left behind in these early discussions. This is unfortunate since early reliability estimates can help ensure that a quality product is delivered and predict if it will finish on-time and within budget. In this webinar, Keith Ciocco will be showing how to leverage the QSM model-based tools to estimate and track the important reliability numbers along with cost, scope, and schedule.

Keith Ciocco has more than 30 years of experience working in sales and customer service, with 25 of those years spent with QSM. As Vice President, his primary responsibilities include supporting QSM clients with their estimation and measurement goals, managing business development and existing client relations. He has developed and directed the implementation of the sales and customer retention process within QSM and has played a leading role in communicating the value of the QSM tools and services to professionals in the software development, engineering and IT industries.      

Register now!

If you were unable to attend our recent webinar highlighting the pioneering measurement work by Larry Putnam, Sr. and how it applies to today's estimation challenges, a replay is now available.

QSM was deeply saddened by the passing of our founder, Larry Putnam, Sr. just a few months ago. Larry's left behind a 40 year legacy in the software estimation and measurement field. His models were the basis for our SLIM-Suite of tools and many of his discoveries about the behavior of software projects still hold true today. In this webinar, his son and QSM Co-CEO Larry Putnam, Jr. reviews Larry Putnam, Sr.'s original research and the data it was based on. He then explores if that original research continues to stand the test of time when compared with data derived from modern development approaches. He also shows how modern agile development practices exploit some of the laws Larry discovered over 40 years ago. Finally, he discusses the role of estimation in today’s increasingly agile world.

Watch the replay!

On Wednesday, Nov. 3 at 1:00 PM EDT, Larry Putnam, Jr. will present "Larry Putnam, Sr.'s Legacy and Understanding the Physics of Software Projects."

QSM was deeply saddened by the passing of our founder, Larry Putnam, Sr. just a few months ago. Larry's left behind a 40 year legacy in the software estimation and measurement field. His models were the basis for our SLIM-Suite of tools and many of his discoveries about the behavior of software projects still hold true today. In this webinar, his son and QSM Co-CEO Larry Putnam, Jr. reviews Larry Putnam, Sr.'s original research and the data it was based on. He then explores if that original research continues to stand the test of time when compared with data derived from modern development approaches. He also shows how modern agile development practices exploit some of the laws Larry discovered over 40 years ago. Finally, he discusses the role of estimation in today’s increasingly agile world.

Register now!

If you were unable to attend our recent webinar, "Critical Cost & Schedule Target Setting with Data-Driven Estimation," a replay is now available.

It might come as no surprise that technology organizations will spend millions of dollars this year on agile and traditional development programs. But did you know that many will lose big money and time because they don’t have an effective way to establish and negotiate reasonable cost, schedule, and quality targets? In this webinar, Keith Ciocco demonstrates how we use the QSM estimation tools to manage these major challenges and the uncertainty that can come with very early critical planning decisions.

Watch the replay!

On Wednesday, September 15th at 1:00 PM Eastern, QSM will host a free webinar, "Critical Cost & Schedule Target Setting with Data-Driven Estimation."

It might come as no surprise that technology organizations will spend millions of dollars this year on agile and traditional development programs. But did you know that many will lose big money and time because they don’t have an effective way to establish and negotiate reasonable cost, schedule, and quality targets? In this webinar, Keith Ciocco will demonstrate how we use the QSM estimation tools to manage these major challenges and the uncertainty that can come with very early critical planning decisions.

Register now!

QSM is deeply saddened to share that our founder, Larry Putnam, Sr. passed away last week at the age of 91, leaving behind a 40 year legacy in the software estimation and measurement field.

Larry began his illustrious career in the military, graduating from West Point in 1952. He was commissioned in the Armor Branch and went on to serve 26 years on active duty. While in the service, he studied Nuclear Effects Engineering at the Naval Postgraduate School, where he obtained a Masters degree in Physics. 

But it was to be the relatively new field of software development where Larry would ultimately make his mark. He was assigned to manage the Army's computer program budget at the Pentagon in the mid-1970s. After struggling to defend his yearly budget to the Department of Defense (DoD) budget review authority (OSD) because he couldn't justify the staffing levels for one of his systems, he made it his mission to understand software engineering staffing and effort. Starting with the Rayleigh equation as the ideal way to apply people to a design-intensive project, he began collecting Army data to see if it followed the Rayleigh pattern.  Just from comparing the budget data to a group of about 15 systems, he was able to confirm it was a fit.  Using the simple projections of the Rayleigh curves, he was able to get the 50 systems currently in development under financial control.  (He speaks candidly of this experience in Roots Run Deep: The Journey to Software Application Estimation and Risk Management.)