BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Value & Metrics Content on InfoQ

  • InfoQ Article: Lean Kanban Boards for Agile Tracking

    "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.

  • Accurate Estimates - the ultimate oxymoron?

    Amit Rathore questions the value of real time task based estimates in the planning and execution of software projects, taking a lean stance on what they bring to the software delivery party.

  • Measuring the Immeasurable: Code Metrics for Visual Studio

    Code metrics are a way to mathematically calculate the complexity of code. There are several ways to do this, 5 of which are included in Visual Studio Orcas.

  • The Trouble With Systems

    Matt Heusser has written a new piece about the problems inherent with excessively detailed systems and processes, and - perhaps unwittingly - how this relates to agile software development.

  • InfoQ Interview: Ron Jeffries on Running, Tested Features

    At Agile2006, Ron Jeffries told InfoQ that tracking "Running Tested Features" is the essential element of Agility, from which all other practices and activities necessarily follow. Ron who took to the whiteboard to explain how RTF benefits customers, by helping helps teams deliver consistently and reliably.

  • How Closely Should We Measure Productivity?

    A goal of agile methodologies is to improve the productivity of software developers. Unfortunately, productivity can be difficult to measure. In a recent blog posting, Lidor Wyssocky argues against focusing too closely on quantifiable metrics, encouraging us instead to look at "soft evidence" for productivity gains.

  • Danube Releases ScrumWorks v1.8

    ScrumWorks, the free Agile project tracking software from Danube Technologies, this week announced the release of version 1.8, which adds a Product Import feature to bring existing projects into the tool, a number of customer-requested changes and significant performance enhancements.

  • Presentation: Agile Project Management Planning and Budgetting

    What happens to planning when teams "self organize"? Agile methods are empirical: plan it, do it, evaluate, plan again. David Hussman reviews practices for planning a project, release, iteration.

  • Is Project Status Relative?

    Scott Ambler introduces a term for a familiar project phenomenon: the "green shift" that occurs when people rework status reports to make them more politically palatable to management. But can management actually handle the truth?

  • Industry Survey Reveals The Bitter Truth About IT ROI

    A Ziff-Davis CIO Insight survey on Business Value reveals little improvement in how, or how well, IT is measuring value, even though most firms now try to use metrics such as IRR, NPV, return on assets, or activity-based costing. There's no consensus or consistency on which measures to use, or when to use them. And half of respondents doubt that the measures are even accurate.

  • The Creeping Featuritis Chart

    Creeping Featuritis is an insidious sort of product rot, reducing useful software into heaps of expensive widgets and aggravating help features. Peter Abilla brings us a chart by Kathy Sierra, capturing what it looks like from the customer's point of view, and reminds us to "focus on the customer and abandon the competitor-focused strategy all-together."

  • Measuring Performance in the Adaptive Enterprise

    Traditional thinking has turned budgets into fixed performance contracts that force managers at all levels to commit to specified financial outcomes, despite the fact that many of the underlying variables are beyond their control. As Agility increases the futility of this exercise becomes apparent. Thought-leader Jim Highsmith proposes a helpful alternative more harmonious with Agile values.

  • Jim Highsmith Proposes An Adaptive Performance Management System

    Jim Highsmith, Director of Cutter Consortium's Agile Project Management Practice told the APLN Leadership Summit audience yesterday: "...to achieve truly agile, innovative organizations, a change in our approach to performance management systems is necessary... 'Conforming to plan' while delivering scant business value will seriously impede agility, whether in projects or the entire enterprise.

  • Online Discussion on Scrum Requirements Basics

    The ScrumDevelopment list has seen lively discussion lately on Requirements issues frequently faced by new teams: "Can the ScrumMaster be the Product Owner too?", "How do we prioritize our Product Backlog?" and "QA's role in a SCRUM process". New teams quickly discover that a poor-quality Product Backlog can frustrate and undermine a team that is otherwise raring to start delivering value.

  • Statistics on Agile Practices Problematic

    Keith Ray questions the value of statistics for software processes, including Agile processes.

BT