Seen from an airplane window, the ground looks almost two dimensional.  Only the largest features: cities, rivers, and mountain ranges, stand out against the background.  The true complexity of the terrain only becomes apparent after we land and have to navigate through congested traffic, bad weather, and one-way streets.

Software projects are similar.  Staffing and budget plans are often based on high level requirements that tell us what needs to be done, but not how to accomplish it.  As business objectives are translated into the actions that need to be taken and the work products that must be produced, the size of the project, whether expressed in lines of code, function points, or RICEF objects, increases along with the time and effort required to create them.

This level of detail cannot be seen at the Requirements stage; it is invisible.  But, it can be accounted for and managed.  Software consultant, Capers Jones, has stated that software projects grow 1.5% per month.  A QSM study based on IT projects found that 90% of those projects were larger than they were initially estimated to be.  The average size growth was 15%.  This bias towards size growth was not the result of poor estimating.  At the time the initial estimates were done, the components that accounted for the size growth were simply not apparent.

During the webinar I recently presented, "Maximizing Value Using the Relationship between Software Size, Productivity, and Reliability," I received quite a few interesting questions. Here are the highlights:

Do you see the same behaviors in Agile projects as those you presented in this webinar?

In the work for my presentation, I did not look at Agile projects separately.  I was looking at overall trends, breaking things down by application type rather than by development methodology. 

However, Don Beckett recently made a conference presentation on Agile called “Beyond the Hype”.  Don looked at duration, effort, staff, productivity for Agile projects.  There is a nice table where he compared the performance of a typical agile project to a typical IT project. 

Don’s presentation summarizes it well.  The staff is a little higher on Agile projects, the duration and effort are a little lower, but the basic relationships between the metrics and size are similar.

Does the language an application development project is written in have any impact on the data? In other words, when looked at independently, do mainframe COBOL projects look different than .Net projects? 

On October 17 at 7:30 PM, Keith Ciocco will be presenting "Best Practices for Establishing a Successful Estimation Process" at the Gartner Symposium ITXpo. This presentation covers best practices for project estimation. Keith will summarize some key things to remember when setting up a successful estimation process at the organizational and project level, including the importance of calibrating to historical data and measuring size and productivity.

QSM will also be exhibiting at this conference. Stop by booth ET3 and enter to win an iPad 2!

Find more information about the Gartner Symposium ITXpo here and Symposium Session Agenda here.

A replay is now available for the webinar, "Maximizing Value Using the Relationship between Software Size, Productivity, and Reliability," presented by Paul Below.

Now, more than ever, software projects need to efficiently deliver reliable software. However, many development plans unintentionally guarantee a less than optimal result. This presentation describes how to maximize value by establishing minimum acceptable reliability and how to take advantage of the apparent paradox between software size and productivity through appropriate selection of team size and schedule duration.

Paul Below has over 25 years' experience in measurement technology, statistical analysis, estimating, forecasting, Lean Six Sigma, and data mining. He serves as a consultant for QSM, providing clients with statistical analysis of operational performance for process improvement and predictability. Mr. Below is a Certified Software Quality Analyst, a past Certified Function Point Specialist, and a Six Sigma Black Belt. He has been a course developer and instructor for Estimating, Lean Six Sigma, Metrics Analysis, Function Point Analysis, as well as statistical analysis in the Masters of Software Engineering program at Seattle University. He has one US patent and two patents pending.

View the webinar replay.

Have you ever found yourself wondering which SLIM tool to use for a task, or what interfacing features are available for various SLIM Suite applications? We've created a handy Quick Reference Guide that offers a concise, "at a glance" summary of the great features built into SLIM Suite! This one page table is chock full of useful information about import/export capabilities, major tool features, and interfaces to other SLIM tools or applications like Microsoft Project and IBM Rational Focal Point and Rational Team Concert.

Here's what you'll find:

• Tool descriptions and features
• Workbook extensions for each application
• API (Application Programmer's Interface) and third party integration availability by application
• Which settings and data can be imported into each tool
• Export options for charts, reports, and project data

Whether you've licensed one or two applications or the entire tool suite, we hope our Quick Reference Guide will be a helpful resource. 

You can find more resources in the QSM Support section of our website.

On Thursday, Oct. 6 at 1:00 PM EDT, QSM will host a webinar focused on the relationship and apparent paradox between software size, productivity, and reliability.

Now, more than ever, software projects need to efficiently deliver reliable software. However, many development plans unintentionally guarantee a less than optimal result. This presentation describes how to maximize value by establishing minimum acceptable reliability and how to take advantage of the apparent paradox between software size and productivity through appropriate selection of team size and schedule duration.

Paul Below has over 25 years' experience in measurement technology, statistical analysis, estimating, forecasting, Lean Six Sigma, and data mining. He serves as a consultant for QSM, providing clients with statistical analysis of operational performance for process improvement and predictability. Mr. Below is a Certified Software Quality Analyst, a past Certified Function Point Specialist, and a Six Sigma Black Belt. He has been a course developer and instructor for Estimating, Lean Six Sigma, Metrics Analysis, Function Point Analysis, as well as statistical analysis in the Masters of Software Engineering program at Seattle University. He has one US patent and two patents pending.

View the replay of this webinar.

We are pleased to announce that QSM has a new SLIM product tour. This online demo shows you how to quickly and easily use SLIM-Estimate to create an estimate validated by industry benchmarks or your own project history. The demo then demonstrates how to negotiate trade-offs and highlights some of the new features of the tool. The product tour also includes SLIM-MasterPlan, which allows you to roll-up multiple estimates and is ideal for iterative and non-iterative developments.

View the new SLIM demo here and tell us what you think!

The next time you call or email QSM for support, you may notice a few unfamiliar names or voices. That's because QSM Research and Support is growing!

The first addition to our team is Katie Costantini. Katie joined QSM as a temporary summer intern in May of this year. We were so delighted by the quality of her work that we recently offered her a full time position at QSM as a Technical Support and Documentation specialist.

Katie Costantini joins QSM Research and Technical Support with three years of customer service experience under her belt. Over the summer, she has been working hard to upgrade our product documentation to a newer platform and format. You'll see some of her work in the next edition of SLIM-Suite manuals and help. She also assisted with the redesign of our new FAQs page and has been helping us revamp our ramp up documentation and processes. Katie graduated from Virginia Commonwealth University cum laude with a B.S. in Economics and a minor in Latin and Roman Studies. Raised in a Marine Corps family (ooh rah!), Katie has lived in California, North Carolina, Virginia, and Cairo, Egypt.

Over the next year, Kate will be working on support documentation and the next update of the QSM database and industry trend lines. Her strong quantitative background and stellar organizational skills are already helping us bring about some exciting changes that we'll be unveiling soon!

The second (chronologically speaking) addition to QSM Research & Support is Laura Zuber:

The QSM Database is the cornerstone of our tools and services, so our clients and prospects often ask for more information regarding the data and types of projects represented. This blog post addresses some frequently asked questions about the QSM Database.

Sources of Data

Since 1978, QSM has collected completed project data from licensed SLIM-Suite^® users and trained QSM consulting staff. Consulting data is also collected by permission during productivity assessment, benchmark, software estimation, project audit, and cost-to-complete engagements. Many projects in our database are subject to non-disclosure agreements but regardless of whether formal agreements are in place, it is our policy to guard the confidentiality and identity of clients who contribute project data. For this reason, QSM releases industry data in summary form to preclude identification of individual projects/companies or disclosure of sensitive business information.

Data Metrics

Our basic metric set focuses on size, time, effort, and defects (SEI Core Metrics) for the Feasibility, Requirements/Design, Code/Test, and Maintenance phases. These core measurements are supplemented by nearly 300 other quantitative and qualitative metrics. Approximately 98% of our projects have time and effort data for the Code and Test phase and 70% have time/effort data for both the R&D and C&T phases.

Productivity is captured via the following metrics:

QSM Productivity Index (PI)
Cost per SLOC or Function Point
SLOC or Function Points per month
SLOC or Function Points per Effort Unit (Months, Hours, Days, Weeks, Years)

Quality data is captured via the following metrics:

If you haven't already done so, now is a great time to check out our new Frequently Asked Questions page!

Over the summer, our Intrepid Support Intern Katie revised, updated, or rewrote over 80 frequently asked questions and we've redesigned the FAQs page to make it easier to use. You can browse FAQs by category or enter search your own custom search terms in the Search box.

Can't find what you're looking for? Just email QSM Support - we'll be happy to assist!