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.
Two years ago, Borland knew it needed to strengthen operational oversight, reduce costs and improve efficiency and quality. Today, the number of software releases has doubled annually, costs are down, and development teams are happier and more productive. What made the difference? Borland got agile.
The Mac versus PC debate has been going on for some time with strongly held opinions on both sides of the monitor. More recently, the project management community has been debating agile versus so-called traditional techniques. And there are certainly similarities in how both discussions can be framed and, perhaps, resolved.
Agile project management and software development techniques like Scrum and Extreme Programming continue to gain popularity, but not all projects are suited to a purely agile approach. By helping to define value, eliminate waste and prevent defects, the principles of Lean Manufacturing and Six Sigma can also be used to improve the effectiveness of traditional project management processes.
In this roundtable series on emerging trends in Agile adoption, application and acceptance, three technology executives discuss how Agile methods have made a difference in their organizations, from influencing their decision making and hiring practices, to improving team and customer interaction.
In this roundtable discussion, three proponents of Agile methods discuss their strengths, respond to common criticisms and concerns, and set some misconceptions straight.
Switching to new agile development software and processes in the midst of a major release was a gamble for a developer of corporate performance management solutions. But the risk paid off with reductions in testing and packaging time as well as a nearly 30 percent increase in developer capacity.
What agile methods are, what they're not, and how you fit.