The Latest

Have you ever wished for a tool to help you define and refine requirements and make your programs more testable? OClear could be the tool you've been waiting for.

Taking an lean-agile slant on metrics for configuration management, the authors focus on ways to measure the value CM and SCM adds to the project and product and how to measure flow and waste.

This unique podcast shares a conversation held between Bob Payne, Barg Upender, and David Kane as they discuss agile movie making. Take a minute to learn one of the exciting ways that agile can be utilized outside of its traditional mediums.

Agile is being evangelized in executive boardrooms and introduced top-down with increasing frequency. Considering that Agile advocates self-management by the individual and within a team, what is the role of senior leadership? My experience from this top-down perspective has given me insight into attitudes and techniques that are successful and others that fail. I assert that there is an effective and appropriate stance for senior leadership that will improve the effectiveness of an Agile transformation. Key to my list of recommendations for making Agile work is the balanced involvement of both senior-level leaders and practitioners in the planning and executing the introduction of Agile practices.

Much has been written about the balanced scorecard methodology. Its goal is to measure desired outcomes and predict drivers of those outcomes. For a properly implemented agile team, this line-of-site measurement happens naturally and is controlled daily. This article suggests a simple and natural scorecard that provides accurate daily visibility of drivers and outcomes for an agile team focused on delivering business value to its clients.

Delivering More Business Value Where Needed

Within the software development community, one of the biggest movements over the past decade has been Agile Development whereby teams adopt practices and attitudes consistent with the now famous Agile Manifesto. Additionally, there has been much discussion over the past four to five years about applying principles from the Theory of Constraints (ToC) and Lean Product Development (Lean) to software development. This has had a tendency to muddy the surrounding waters as teams question whether they  should apply Agile, ToC, or Lean concepts. Are these three approaches mutually exclusive? Is there some hidden magic that can be unlocked by careful application of all three? Isn't it hard enough just trying to be Agile, without also trying to be Lean and ToC-ish? In this article we give an overview of Lean and ToC and show how they can be used in conjunction with Agile practices to focus on an organization's business value. By using elements of Lean, ToC, and Agile together more business value can be delivered with less effort.

Users don't have to be doomed to the nightmare of software fraught with defects that should have been fixed before release. Time spent testing now can save you from the Death Spiral later. Remember: If you don't have time to do it right, how will you have time to do it over . . . and over . . . and over?