The Latest

What makes a team agile? Is it in the way it plans projects or how it engineers its products? In this article, Steve Berczuk explains how agile code and technical practices can help a team stay agile across the product lifecycle.

I've worked with Scrum for a while, having gotten my CSM certification in 2005, and I've spent time both before and after that trying to learn what I could about Scrum, agile, and Lean, both in the context of software and out side of it. After absorbing bits of information on Kanban informally, I decided that to was time to read a book on it. I read David Anderson's book Kanban: Successful Evolutionary Change for Your Technology Business.

Do you know colleagues who box themselves into the corner regularly? Getting lost is not the problem; coping with having gotten lost is the problem. Markus Gärtner explains how to notice that you are stuck, how to ask for help, and who you should be asking.

There is definite asymmetry between building trust and destroying trust. While building trust can be complex and time-consuming, destroying trust can be done in one simple instant.

Yves Hanoulle has edited a book, called Who Is Agile? I love this book because of all the back-stories, the pictures, and the links. And, oh my goodness, the links.

Training people and introducing new ideas requires more than just clear, factual explanations or theorems. Brian Bozzuto explores how games, simulations, and other exercises play an instrumental role in helping people be comfortable enough with new ideas that they choose to put them into practice.

Many new products being developed require the contribution of artists and other such "creatives," but artists often view the creative process as an organic thing that cannot be analyzed, dissected, or reduced to a set of defined practices without killing it. This article explores barriers such as these to the introduction of agile methods and how these barriers can be overcome.