Uncle Bob has provided another interesting piece that focuses on the responsibility of people to do good work on their software projects.

A video with multiple people in the agile community has been created to discuss what causes Scrum and agile to fail at this location.

Mark Levison has compiled a listing of great Scrum case studies for those interested in how others do it in this blog entry.

This article describes a presentation from Mitch Lacey on “When Working Software is Not Enough: A Story of Project Failure” with significant details about what lead to the failure.

The author of this blog entry describes how user stories are insufficient for quality requirements (aka non-functional requirements) and Chris Sterling has this blog entry on how to use an “Abuse User Story” to describe the cost of not addressing quality attributes in a user story format.

Mario
Moreira describes how infrastructure can be refactored in a similar nature as code in this article.

Johanna Rothman provides and explains 3 simple steps teams can follow to transition a Waterfall project to Agile in the middle of the project in this blog entry.

Mark Levison rolls up a listing of post Agile 2008 resources on his blog “Notes from a Tool User” here.

This blog entry discusses the problem with having too many projects started. The problems are related to project portfolio management and how do we decide what should be started.

Camron Shimy describes the value of making information radiators big and visible for your teams and others in this blog post.