Change by any means is difficult, time-consuming and costly when applied to any organization. Altering the status quo takes a lot of effort, conversation, convincing, negotiation, influencing and when all those items are overcome the change might still fail and the old ways returns. However, I think change needs to be handled in a very systematic and pragmatic way. By making small changes, incremental steps and targeting the proper audience in the beginning adoption of a new methodology can be possible. The change I’m talking about in this case is embracing a Project Management methodology in the workplace.
First of all I don’t think it’s a viable move to shift an entire organization’s project development policy from something (not project management style) to Project Management style of producing services and products. A few of the ways to convince upper management and stakeholders to accept this practice is by selecting a project that might not be mission critical, independent and isolated project from the main business needs. I say this because it will allow the project and the process to grow organically within the team or business area without the cloud of other projects dependence over it and vice-versa. Regardless if it’s a success or a failure the Project Management process that was utilized during development can stand on its own merit.
I will point out two reasons for implementing a Project Management style in the workplace. The first is maximum effectiveness of planning and control. While it is hard to predict the success of any given project (because project managers are not soothsayers); you can improve the chances of success by employing a Project Management method. This is due to the fact that the PM guidelines allow you to address many important aspects of a project early in development: scope, time, cost and quality. Another critical characteristic of Project Management is it provides a structured approach to approaching, handling, and maintaining of projects. The advantages of a controlled process are it affords the stakeholders a well define structure of authority and responsibility. This method is not limited to the tech industries but can be practiced in various businesses. A few more added benefits is it improves the chance of meeting schedule deadlines, budget constraints and quality milestones while mitigating risks.