InfoQ

News

Improving Productivity without Formal Metrics

Posted by Mark Levison on Mar 17, 2008 01:00 AM

Community
Agile
Topics
Collaboration,
Teamwork,
Leadership
Tags
Coaching and Mentoring,
Continuous Improvement,
Value & Metrics,
Productivity

Ron Jeffries has started writing a series of fictional stories based on his observation of real teams. The first story (Kate Oneal: Productivity) focuses on the character Kate O'Neal (CTO) and one of her teams "Rimshot". In this episode Ron explores achieving and measuring Productivity improvements without formal metrics.

Ron is best known for being the on-site XP coach on the first XP project in 1996, in addition he has two books: Extreme Programming Adventures in C# and Extreme Programming Installed.

Kate asks all of her teams: "I'd like the teams to work on continuously improving productivity. Each team, please put together a team plan for how you'll do that, and how to communicate it briefly, in writing, so that we can roll up and learn from your reports and package them for the executive team. Get together with me if you need to, and I'd like your plans by the first of the month, please." On Rimshot reactions range from constructive engagement to hostility and assuming that management is trying to foist metrics on the team.

Rather than tell the team exactly what to do Kate asks the team questions about what they do and what benefits improving productivity might have. Through the discussion the team realize that they're spending a lot of time dealing with integration problems and that if this is fixed they could spend the time improving the quality of the code. In the end the team agrees to focus on solving the integration issues. To measure their success they will track time spent solving integration problems.

Finally with a reference to Punished by Rewards (by Alfie Kohn) Ron shows that metrics are all too easily gamed.

In the Test Driven Development Newsgroup George Dinwiddie raises the concern that this might lead to local optimizations, perhaps at the expense of global optimization. To avoid this he recommends that goals be set on a divisional (instead of team) level.

Read more about metrics at InfoQ.

Related Sponsor

VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.

No comments

Reply

Exclusive Content

Tapestry for Nonbelievers

A new article by I. Drobiazko and R. Zubairov introduces v. 5 of the Apache Tapestry component-oriented web framework. The tutorial shows how to create a component and covers IoC in Tapestry and Ajax.

Pete Lacey on REST and Web Services

In this interview, Burton Group consultant Pete Lacey talks to Stefan Tilkov about his disillusionment with SOAP, his opinion on REST, and addresses some of the perceived shortcomings REST vs. WS-*.

Business Natural Languages Development in Ruby

Jay Fields presents his concept of Business Natural Languages - a type of Domain Specific Languages geared towards being readable by domain experts.

Distributed Version Control Systems: A Not-So-Quick Guide Through

Adoption and interest for Distributed Version Control Systems is constantly rising. We will introduce the concept of DVCS and have a look at 3 actors in the area: git, Mercurial and Bazaar.

Segundo Velasquez and Agile as Seen Through the Customer's Eyes

Deborah Hartmann interviewed Segundo Velasquez about his experience as customer with an Agile team during the initial phase of software design of a product.

Fine Grained Versioning with ClickOnce

David Cooksey shows how to fine grained versioning to a ClickOnce deployment using an HttpHandler written with ASP.NET, making partial rollouts to a test audience much easier.

Implementing Manual Activities in Windows Workflow

Windows workflow (WF) is an excellent framework for implementing business processes, but lacks support for human activities. This article describes a completely generic approach for changing this.

Markus Voelter about Software Architecture Documentation

In this interview taken during OOPSLA 2007, Markus Voelter talks about the importance of documenting the software architecture, and gives some good and also bad examples on how it could be done.