Leveraging QSM's industry database of over 13,000+ completed projects, Katie Costantini takes a high-level look at changes to software schedules, effort/cost, productivity, size, and reliability metrics from 1980 to 2019.
Doug Putnam examined 390 contemporary software applications of the same size, a significant portion of which used agile methods and tools, to see what matters more - staffing decisions or methodology. He discovered that while the additional staff reduced the schedule by approximately 30%, the software project cost increased by 350%. The additional staff also created 500% more defects that had to be fixed during testing. In this article, Doug Putnam identifies a staffing "sweet spot" and outlines a step-by-step planning process that uses predictive analysis and early estimation to more accurately account for staffing needs.
In a recent article for Government Computer News, QSM's Larry Putnam, Jr. leverages data from from the QSM Database to identify best practices for successful government projects.
In this article originally published on Agile Connection, QSM's Larry Putnam, Jr. turns to cold hard data from completed projects in the QSM database to determine whether big agile is "enterprise savior or oxymoron."
In a recent article for Projects at Work, QSM's Don Beckett identifies seven principles, based on comprehensive studies, that leaders must support and uphold to help create an environment in which projects can succeed. Ignoring them practically guarantees failure.
This study looks at the QSM software project database and examines a set of validated projects counted in function points that have completed since the year 2000 to see what they tell about productivity, schedule, and staffing.
How can I quantitatively evaluate potential suppliers and determine whether or not a potential supplier is likely to perform as promised?
This article discusses the new issue of the fixed deadline and how managing expectations and using metrics can make fixed deadlines far less daunting.
This article discusses the drop in productivity and decline in reliability and how to fix these issues.
Yes! Do you want to be on the trailing edge of this paradigm shift while your competitors are using objects to consistently maneuver inside your development cycle.
John A. Strand III