A funny thing happened on the way to Whole Team -- cubicle silos and floor fiefdoms. What key issues prevent us from achieving requisite wholeness for our teams? How do we learn to really share and play nice on the software playground? Read about it here.

We can see now that agility is bigger than we thought: a journey, a path that we are all on together. So we've decided to stop being so darned fundamentalist about it all the time. Sheesh! Check it out here.

What is empathetic listening, and how can we use it to build healthier software development communities? Read our notions here.

What is an "agile path" approach to agile transition? How agile is agile enough? What specific transition patterns are helpful? Read our definitions here.

What are the key differences between excellent and mediocre software? What does it mean to be a Software Craftsman (or Craftswoman)? Read our definitions here.

Craig Larman has written an excellent book comparing waterfall project management to Agile/iterative approaches. Read our review here.

How do Agile methods avoid the problems that chaotic and Waterfall approaches succumb to? Check out our perspective on the key Agile characteristics here.

We have long believed that there is no substitute for pure programming ability, or craftsmanship, on the part of individual programmers. Read our thinking on this here.