InfoQ Homepage Value & Metrics Content on InfoQ
-
Should We Manage Both Features and Tasks?
Although it keeps people busy, managing tasks is neither interesting nor useful. Managing value created provides greater leverage and greater risk management. Jon Kern blogged last week on creating good features (rather than tasks) by focusing on value and testability. But do we sometimes need to manage tasks, too? David Anderson used the Theory of Constraints to back an unexpected answer.
-
SirsiDynix Case Study: Jeff Sutherland on Highly Productive Distributed Scrum
Scrum co-creator Jeff Sutherland has just finished a paper on the SirsiDynix project, which he calls the most productive large Java project ever documented. The project used Distributed Scrum and some XP practices. Although distributed teams are often expected to experience reduced productivity, this team's productivity level matched that measured by Cohn on a co-located team!
-
Anderson's "Agile Management" Reviewed
Stick Minds has posted two reviews of David Anderson's "Agile Management for Software Engineering: Applying the Theory of Constraints for Business Results", in which Anderson combines TOC and Agile approaches. The book targets senior IT executives, project managers, development managers, and team leads. Do manufacturing metrics really enhance Agile software development? Apparently the jury is out.
-
Worth Repeating: The BigBook Technique
Mark Hedlund has a favourite story: he tells of the BigBook Technique, a simple ploy engineers once used to communicate with their CEO about a death-march project. With yet another big-project implosion in the news, Hedlund felt the need to roll out this simple remedy, again. In effect: nine women simply cannot deliver a baby in one month. If that sounds familiar, this story may be of use to you.
-
Is the Feedback Loop Worth the Time?
John Brothers, on Indefinite Articles, blogged an interesting conversation last week between Mary Poppendieck and Robert Bogue. Drawn from the Agile Project Management newsgroup, it pointed out two different stances on the relative cost and value of "frequent feedback", a key component of Agile methodologies.