Discussion: Measuring Success of an Agile Project from the Customer’s Perspective

by Vikas Hazrati on  Feb 05, 2008 4

A recent discussion on the Scrum Development list looked at: “How does a customer measure the success of an Agile project?” Emphasis on: “measure”. The discussion seemed to agree that clients do need a way to track success in their terms, and various metrics were suggested, though it was agreed: it depends on the situation and the customer.

VersionOne Announces New UI and Embedded Forecasting in Release 8

by Mike Bria on  Feb 04, 2008 1

VersionOne recently announced Release 8 of their agile project management and team organization tool suite. This new release features an all-new user interface, introduction of a release forecasting toolset, and additional plug-n-play integrations for some popular open source tools.

Measure Teams, Not Individuals

by Mike Bria on  Jan 31, 2008 3

Michael Dubakov recently expressed warning against the measurement of individual velocity and individual estimate accuracy. His view: measurement of these metrics not only provides no more useful information than is already available with their team-level equivalents, but may also have a tendency to encourage teams into behaviors that reduce effectiveness.

Are Iterations/Sprints Waste or Value to Agile Teams?

by Geoffrey Wiseman on  Jan 30, 2008 13

Although many people consider iteration to be a key characteristic of agile software development, some question whether or not they're important, and add value to an agile method, or if they're superfluous, or even wasteful. InfoQ has assembled a roundup of arguments on the subject, to help agile teams decide if iterations are important for them.

Is Velocity Really the Golden Measurement?

by Mike Bria on  Jan 21, 2008 3

What value do teams get from measuring velocity, beyond the ability to reasonably estimate commitments for the short-term future? J.B. Rainsberger proposes that teams spend less energy scrutinizing velocity and more energy thoughtfully identifying and eliminating areas of waste in their projects.

Target Process 2.7: Agile Project Management tool for Distributed Teams

by Mark Levison on  Jan 21, 2008 6

Target Process 2.7 has been released. Target Process is an Agile Process Management tool that automates many of the tasks associated with an agile project. Notable features in recent iterations include visual iteration planning, program level release planning, individual velocity reports, and more.

Multiple Projects, One Agile Team

by Geoffrey Wiseman on  Dec 05, 2007 5

It's not uncommon for an organization to have one group of developers who need to complete multiple projects. In those situations, how should the group be structured, and how should their work be planned and allocated?

What Makes a Tool Agile?

by Amr Elssamadisy on  Oct 10, 2007 13

Individuals and interactions over processes and tools is the very first of the values of the Agile Manifesto. Tools, however, seem to be a big part of development on most Agile teams. When does a tool help and when does it hinder (Agile) software development?

InfoQ Article: Lean Kanban Boards for Agile Tracking

by Deborah Hartmann Preuss on  Aug 25, 2007 14

"Big Visible Charts" aren't unique to Agile - Lean manufacturing also has its Kanban Boards. "Kanban" roughly means "card or sign," and each Kanban card is "pulled" onto the board only when the work represented by an "in progress" card is retired. In this InfoQ article, Kenji Hiranabe proposes using Kanban Boards to track Agile project status (Time, Task, and Team) to enhance collaboration.

VersionOne release Agile Enterprise 7.2

by Ben Hughes on  Aug 21, 2007

Version One recently announced their new release of V1: Agile Enterprise, InfoQ provide an overview of the new functionality in the latest release of one of the more prominent pieces of Agile project management software.

InfoQ Interview: Experiences with Planning Poker

by Deborah Hartmann Preuss on  Jul 29, 2007 9

In this fourteen-minute interview, Nils Haugen described "Planning Poker," a simple mechanism for arriving at estimates collaboratively, which has additional team building benefits and improves team estimates over time. Haugen shared his views on why this technique is an important tool for Agile teams in this InfoQ interview.

Working with Mingle

by Ben Hughes on  Jul 05, 2007 12

InfoQ had some time with Mingle project engineer Jay Wallace, to use ThoughtWorks' much anticipated Mingle software and demonstrate to us how it differentiates itself from other products by being a truly agile project management tool.

Incremental Software Development without Iterations

by Amr Elssamadisy on  Jun 05, 2007 3

David Anderson described how his team is using a kanban system for their sustaining engineering (maintenance and bug fixing) activities. Iterations have been dropped although software is still released every two weeks. Work is scheduled, monitored, and run via a "kanban board" and daily stand-up meetings.

Aligning Agile with Enterprise Goals

by Geoffrey Wiseman on  May 30, 2007 1

Agile methods have achieved a level of success and respect within development teams, but it is not always easy to extend these methods beyond the development team. In Investing in Agile: Aligning Agile with Enterprise Goals, Dan Murphy and Dave Rooney stated that IT project management has evolved with agile methods, but that the enterprise hasn't followed suit.

The Dire Consequences of Fixed Price Projects

by Ben Hughes on  May 03, 2007 6

In a recent newsletter, Scott Ambler looked at why fixed price projects tend to overrun and often fail to solve the business problems they set out to conquer. Scott named the key problems in fixed price projects, identified the bad habits they encourage for customers and developers, and ended with a call to revisit how we fund our IT projects, offering an alternative.

General Feedback
Editorial and all content copyright © 2006-2014 C4Media Inc. hosted at Contegix, the best ISP we've ever worked with.
Privacy policy