Too many executives have the impression that a PSO is mostly a clerical function and that establishing one is not too difficult. Nothing could be further from the truth. J. Kent Crawford provides a compelling discussion of some of those challenges in The Strategic Project Office: A Guide to Improving Organizational Performance (Marcel Dekker, 2001). According to Crawford, the challenges to implementing a PSO are as follows:
Effectively deploying a PSO can require two to five years for full implementation. That is a long time. According to the Standish Group research, the longer the project is, the higher the probability of project failure. The way out of this apparent dilemma is to plan the PSO deployment in stages. Begin by prioritizing the support functions according to the level of need, and partition their deployment into stages. Each stage must deliver visible and measurable value to the process and practice of project management.
A popular approach to putting a PSO in place is a bottom-up strategy. At the department or project level, you must demonstrate value by showing the results that a department-level PSO can achieve. Then, by way of example, others in the organization will see that success and ask how they can achieve it in their own areas. This grassroots effort will be contagious, and it is one of the keys to a successful PSO implementation over time.
This goes to the very heart of a PSO contributing at the corporate level. At some point in the implementation of the PSO, senior managers will begin to see how an effectively managed project portfolio can contribute to corporate goals. Senior managers begin to think about the portfolio and not just the projects that comprise it. This transition from Level 3 to Level 4 maturity is the result of a major discovery by senior management as they begin to think in terms of a systems perspective.
This characteristic is clearly one of a Level 4 organization. The integration of the project data into the other corporate databases provides senior managers with the tools they need to make enterprise-wide business decisions where projects are the strategic components of their business plans. Making this jump from a single-project focus to a strategic-portfolio focus is the sign of a Level 4 PSO.
To drive thinking to the enterprise-wide level requires sophisticated corporate databases, standardization of data capture, and the applications systems to extract knowledge from information. Even today, only a few organizations have implemented something as simple as a database of best practices and lessons learned. Part of the reason for the lack of this kind of database is because modern project management is in its infancy. It is only about 50 years old. Standards exist at the project level, but there are few standards at the portfolio level.
Most organizations have not taken the education and training of project managers very seriously. That fact has to change if the PSO is expected to make an impact on project success. A comprehensive curriculum with a variety of delivery approaches is needed. Currently, career and professional development programs for project managers are few and far between. The PSO is positioned to deliver, but senior management must first make the commitment and provide the needed resources. In addition, it would be very helpful if senior management could avail themselves of a one-day briefing to understand project management from their perspective. Most project management–training vendors offer one-day programs focusing on what the executive needs to know about project management.
Communications between and among projects and from first-line managers through to executive levels must be open and free. The PSO can establish and maintain the channels of communications and offer support for report preparation and distribution.
18.225.156.158