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.

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.

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.

This presentation by David Anderson discusses what is Agile, how does the community embrace changes to its foundations, and his thoughts on what will allow us to express more maturity as a community. It is full of thought provoking ideas and potentially controversial methods that are rooted in existing theory and industry practices.

This article on CIO.com is sub-titled:

Agile methodologies seemed like a good idea to this software development team. But when the company doesn’t sincerely accept the change in work style, the result is just a buzzword for “project hell.”

Jeff Sutherland, co-inventor of Scrum, points out the relationship of Scrum to organizational patterns put out by James Coplien in this article.

This article at InfoQ is an interesting take on using Scrum in an environment that it is not well nourished. Should a ScrumMaster be a blocker to help the team get things done or is this a smell to avoid?

Is your organization or team working on a Service-Oriented Architecture (SOA) implementation? Are you wondering if this can be implemented using an Agile approach? Check out how an extremely large organization, Bosch, has used an Agile approach along with Test-Driven Design (TDD) to implement SOA using a middle-out architecture strategy.