Why Giving Up Control is Good for Your Methodology...and Your Projects
Methodology. Process. Framework. These are three words that, in the world of project management, define much of the organizational expectations placed upon project managers. There are, of course, those who will argue that these describe different concepts and should be interpreted with different meanings. But the essential point is the same: They are trying to define expectations of how projects should get managed.
An important question to ask is, “Why do we have processes, anyway?” Specifically, if you have well-trained and capable project managers, shouldn’t you just get out of their way and let them got on with the job at hand? Certainly, there are many project managers that would like that state of affairs: many of us value our independence and the autonomy to do what we think is right. Some organizations essentially manage in this way, adopting a fairly hands-off attitude to what is done in the name of project management. Most organizations, however, have a bias toward establishing a consistent and defined approach to the delivery of their projects. They value standards, they define processes and they mandate templates that are to be employed at each stage of the project process.
I have certainly been guilty of advocating for improvements in process, increases in consistency and enhancements of rigor in how projects are managed. Over two
Please log in or sign up below to read the rest of the article.