Project Management

Should You Standardize Project Methodology?

When you standardize project methodology across projects in the organization, you introduce reliability to project management. But when you do not standardize, project managers are better able to manage projects in a way that fits their natural style. Which is better? In a post for Voices on Project Management, Ramiro Rodrigues discusses the pros and cons to standardization.

Standards & Practices

One benefit of standardization is that this standard can be made to align with the identity and strengths of the business, which looks attractive to customers. Standardization also promises more predictability of services and products, both for customers and for stakeholders. There is more clarity and less guesswork involved in understanding the direction of a project. And lastly, standardization provides clear processes for continuous improvement, so that there are not questions of “Now what?” following an initial success.

However, standardization can also introduce new layers of bureaucracy and tedious paperwork that only get in the way of project completion. If the standard imposed does not agree with the actual day-to-day work of project management in the organization, then you have just erected new walls for no reason. That is why Rodrigues says that, if you are going to standardize, you should ensure it does these things:

  • Enhances project management processes
  • Brings increased clarity and transparency to project phases
  • Minimizes rework and work stress
  • Benefits stakeholders
  • Speeds up project delivery while maintaining quality

He continues to say this:

This latter issue, together with the need for resource optimization and a drop in the learning curve, has led corporations to search for alternatives — such as agile methods…

However, this objectivity “line” should not be stretched too far. There’s a risk that while searching for leaner processes some aspects related to the optimal handling of a project may become too superficial. That could ultimately compromise the quality of project deliveries and the image of the implementing organization.

So which route should you ultimately take? Whichever route most benefits the business. You can view the original post here:–Help-or-Hindrance-

John Friscia

John Friscia was the Editor of Computer Aid's Accelerating IT Success from 2015 through 2018. He began working for Computer Aid, Inc. in 2013 and grew in every possible way in his time there. John graduated summa cum laude from Shippensburg University with a B.A. in English.

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button

We use cookies on our website

We use cookies to give you the best user experience. Please confirm, if you accept our tracking cookies. You can also decline the tracking, so you can continue to visit our website without any data sent to third party services.