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.
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.
Jeff Sutherland discusses how a venture capitalist firm has figured out that in order to deliver more value the team members must work less. In this article he introduces the Maxwell Curve that shows this in a visual representation.
Over at MySpace they are doing Scrum on many teams. Scott Downey, their internal Agile Coach, describes how he helps a team get kicked off with Scrum through shock therapy methods in this article on Jeff Sutherland’s blog.
Jeff Sutherland describes to the agile community how Scrum came into being and how it’s roots stem from complex adaptive systems. This article has comprehensive information on Scrum early days including discussion group archives.
Mary and Tom Poppendieck describe a different way to think about mature organizations and processes in this article.
