Articles published in October 2007

Case Study: October 2007

Case Study: October 2007

Theories are illuminating and helpful, but nothing can replace real-world experience. Each month, we'll post a real-life, ongoing case study for your consideration. The author will monitor comments and may even try the remedies that you, the Scrum community, suggest. The results of these trials will be posted as a comment to the case study. This case study is open for discussion. Join in. 

Why switch a failing waterfall project over to agile?

Why switch a failing waterfall project over to agile?

The first in a five-part series, this article details the advantages of converting an exisiting project to agile, as opposed to only applying agile to new projects. The next article in the series will look at how you make that switch.

Success Factors for Scrum Implementation

Success Factors for Scrum Implementation

One company's experience with implementing Scrum and the factors that helped them to succeed.

Agile Smells: Lack of Progress

Agile Smells: Lack of Progress

Progress smells often point to failings in one of three areas: backlog management, feature definition, and feature completion. This article analyzes what lack of progress means and describes remedies for weaknesses in backlog management. Parts two and three of this smell analysis will address feature definition and completion, respectively.

Scrum is Not the Point. Agile is!

Scrum is Not the Point. Agile is!

The simplicity of Scrum is both its strength and its weakness. A true understanding of agile principles is necessary for Scrum (or any other agile method) to succeed.

Predictability in Action

Predictability in Action

Agile estimation gives you the right answer, even if it’s not the one you want to hear.