Agile Organization: Best and Worst Practices
Any organization will find itself hosting a wide range of projects, from traditional waterfall like undertakings to others that look a lot like looping squiggly lines. The question is, will the organization be a willing and gracious host, ready to meet the diverse requirements of projects with varied personalities?
In my experience, most organizations are not willing nor gracious hosts. They tend to lock into one monolithic methodology and then attempt to force feed it throughout the department, division or even enterprise wide. This can take the form of massive training programs, the creation of a project office that holds people accountable to mandated practices and procedures along with the wholesale introduction of required-to-use software tools including specified templates and workflows. I refer to the latter practice as totoolitarianism.
The one-size-fits-all approach provides only the illusion of control. Why? Few employees actually follow the system because if they did, they would never get any real work done. They merely go through the motions doing the bare minimum to comply.
This invariably leads to a project management counterculture, one that at worst applies ad hoc approaches to get things done or at best, sneaks in a legitimate agile project management practices. And since this culture is ‘‘illegitimate,” it can’t be managed.
Please log in or sign up below to read the rest of the article.