When it comes to managing projects, more organizations are testing the agile waters. Some are diving right in, while others are dipping their toes, wondering what dangers lurk beneath the surface. Some begin swimming quickly, never looking back; others don’t get much past doggy-paddling.
Why do some companies sink and others swim when using agile methods to manage projects? Are some organizations better suited to it than others, or is it just a matter of having the right training and enough life jackets handy? Once you do start swimming in agile waters, how do you know you’ll be okay in the deep end?
In search of answers to these questions, ProjectsAtWork gathered insights and best practices from three experts who presented at the Agile 2008 Conference earlier this year. Their thoughts might help you better navigate the Agile waters.
Attitude and Attention
It is generally agreed that companies that are already flexible and accustomed to changing direction regularly are more likely to succeed than those that resist change. “If status quo is what they need to stay alive, agile won’t work well,” says Stacia Broderick of AgileEvolution, an agile consulting firm.
Damon Poole, chief technology officer of AccuRev, a company that makes products that automate the software development process