Quick Insights

  • How honest are your software measures?

    Process measures are easy to spin and game. Product measures are more honest.

    View Paper
  • Health (forest) ≠ ∑ health (individual trees)

    Practitioners and leadership must objectively understand both code quality and design quality

    View Paper
  • Quantify design quality. It is the crux of instrumenting a lean transformation.

    Business agility is as much a function of architecture as it is of process.

    View Paper
  • Steering software projects more predictably

    Measuring design quality provides breakthrough insight for steering.

    View Paper
  • Play offense: How to pull the trigger on a software refactor or rewrite

    Measuring design quality can help you act decisively and manage change.

    View Paper
  • Is your code structured as you intended? Probably not.

    Hidden and unintentional complexity causes waste and overhead. Identify architectural impurities early and consistently.

    View Paper
  • Primer on design quality, the (more important) half of steering software projects

    Durable business agility = product agility * process agility. You need both.

    View Paper
  • Is your software healthy? Process measures tell only part of the story.

    Quantifying design quality helps to steer projects and improve software economics.

    View Paper
  • More honest earned value management of software projects

    Earned value should focus more on the progress and quality of the product, not the process.

    View Paper

Tired of software headaches?