Project management is one area that CIOs tend to take for granted and assume that adequate training is being delivered throughout the IT organization. As a former CIO, I know CIOs believe project management methodologies are important, its just that we have so many other pressing issues on our plate. Many of us assume that the staff continues to be adequately trained and that projects are being run within a standard discipline. As the project management maturity level increases, so does the success rate in delivering projects.
Methodologies come in many standard formats. There are industry standards for application development and infrastructure projects (CMMI, RUP, ITIL), and approaches to use these methodologies within an IT environment (Waterfall, Iterative, Agile), as well as adjunct methodologies to help deliver a project within a full lifecycle (Quality, Six Sigma). CIOs need to ask their direct reports if they really understand the methodology that was implemented and if it is being used to the fullest extent for all initiatives.
If your organization is a victim of high failure rates in project delivery, then consider reviewing how the organization is being trained and how your resources are utilizing a standard project methodology.
Most organizations hire skilled project managers and immediately give them high-visibility initiatives. This seems logical when someone comes into an organization with a much needed skill set. We then start an initiative and rely on luck and believe that these individuals will deliver on-time and on-budget. Weve all been involved in this type of hiring scenario, either through our own human resources department or through a vendor, but it is not a guarantee to successfully deliver a project. Organizational factors and environments can make or break a projects success.
Many IT organizations also make the mistake of not having a training program for their project managers. The reason this is important is most companies modify a methodology for their use and circumstance. Organizations change and evolve and so should the project management lifecycle. Changes within an organization can lead to failed projects if the methodology isnt reviewed or modified along with any other changes.
A classic example of when changes to a methodology are needed is when the business creates their own project management office (PMO) and now needs to co-exist with the IT PMO. This scenario also ponders the question if the business and IT are using the same methodology. Delivering a project is much easier, if both groups are utilizing the same project methodology.
Relying on existing project managers to train the other project managers is typically not adequate in relaying valuable information regarding the use of a methodology. Having these seasoned project managers serve as mentors to a new project manager is a great way to keep everyone in check. Good project managers are typically very busy running initiatives and may not have an adequate amount of time to train new or unskilled project managers.
The Unofficial PM
Have you also considered how many other people in your organization may be functioning as a project manager, but not have the requisite skill set? In these instances, resources are expected to wear multiple hats and to perform the role of a project manager.
In this scenario, developers, architects, engineers, quality technicians or business analysts are expected to deliver a portion of a project within a projects lifecycle. CIOs and their staff should not make the assumption that everyone across the organization has a full understanding of the project management methodology and how to use it within an initiative.