Take Your Time to Go Faster
It seems odd to be thinking of organizations that are only now incorporating agile as “late adopters,” but the truth is the rapid expansion of agile in recent years has created a situation where that is the case. While agile may not be the only—or even main—project approach in most organizations, it is certainly an important element of project execution. Organizations that are yet to embrace it are losing out on the benefits it can deliver.
There is increasing recognition of this, and those organizations who are now embarking on agile adoption are feeling pressure to “catch up” with their competitors. That can be a healthy driver for agile acceptance, but it can also drive bad practices—and that’s what I want to look at in this article.
Realistic goals, realistic timelines
Part of the problem is the perception among many inexperienced organizations that agile is going to deliver significant improvements very quickly and with little effort. Certainly, agile methods have demonstrated they can improve many project elements in a fairly dramatic way, and those improvements can happen in early iterations of agile execution.
However, that doesn’t mean an agile implementation is quick and easy. Most organizations recognize they need some outside assistance when they first start, sending staff for training on their method
Please log in or sign up below to read the rest of the article.




