Mike Cohn has provided another great article on how a team can write non-functional requirements in a basic user story format.

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

Jim Shore has written a controversial and directed piece on the state of Agile and it’s future in this article.

Brian again provides an essential work to the Agile community. Find out how to “work with ease” reading the text of his keynote from the Agile Development Practices conference here.

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.

Lyssa Adkins defines 7 failure modes for Agile Coaches and provides some advice on how to manage against them in this blog entry.