Program management

Last updated

Program management is the process of managing several related projects, often with the intention of improving an organization's performance. It is distinct from project management. [1]

Contents

In practice and in its aims, program management is often closely related to systems engineering, industrial engineering, change management, and business transformation. In the defense sector, it is the dominant approach to managing large projects. Because major defense programs entail working with contractors, it is also called acquisition management, indicating that the government buyer acquires goods and services by means of contractors.

The program manager has oversight of the purpose and status of the projects in a program and can use this oversight to support project-level activity to ensure the program goals are met by providing a decision-making capacity that cannot be achieved at project level or by providing the project manager with a program perspective when required, or as a sounding board for ideas and approaches to solving project issues that have program impacts. The program manager may be well-placed to provide this insight by actively seeking out such information from the project managers, although in large and/or complex projects, a specific role may be required. However this insight arises, the program manager needs this in order to be comfortable that the overall program goals are achievable.

Overview and definition

Many programs focus on delivering a capability to change and are normally designed to deliver the organization's strategy or business transformation. Program management also emphasizes the coordinating and prioritizing of resources across projects, managing links between the projects and the overall costs and risks of the program.

The Project Management Institute, an American nonprofit professional association for project management, thusly summarizes: "a Program is a group of related projects managed in a coordinated manner to obtain benefits and control NOT available from managing them individually. Programs may include elements of related work outside of the scope of the discrete projects in the program... Some projects within a program can deliver useful incremental benefits to the organization before the program itself has completed." [2]

In public sector work in Europe, the term normally refers to multiple change projects: projects that are designed to deliver benefits to the host organization, for example, the Office of Government Commerce for the UK government.

Many organizations only run one program at a time in the form of an overarching program containing all their projects. In Project Management Institute terminology, this is more likely to be a project portfolio than a program. Some larger organizations may have multiple programs each designed to deliver a range of improvements. Some organizations use the concept of systems engineering where others use program management.

Standards

Key factors

Benefits
The key difference between a project and a program is that benefits are delivered within the program lifecycle compared to a project when they are delivered after the project has finished. [3]
Governance
The structure, process, and procedure to control internal operations and changes to performance objectives. Governance must include a set of metrics to indicate the health and progress of the program in the most vital areas.
Alignment
The program must support a higher-level vision, goals, and objectives. These are set out in the program vision and blueprint, which defines the future state for the organization, sector or community that will be significantly changed. [4]
Transformation
A program will deliver major change, whether it is within an organization, a sector or a community. As such, the management of change and transition is a key characteristic of a program, not just the building a major capability. [4] [ clarification needed ]
Assurance
Verify and validate the program, ensuring adherence to standards and alignment with the vision. Programs should always have an assurance strategy. [5]
Management
Ensure accountability through regular reviews, and that management of projects, stakeholders and suppliers is in place.
Integration
Ensure that component parts fit together properly to make the intended whole. Optimize performance across the program value chain, functionally and technically.
Finances
Track basic costs together with wider costs of administering the program and also the costs of change and transition to achieve benefits.
Infrastructure
Allocation of resources influences the cost and success of the program. Infrastructure might cover offices, version control, and IT.
Planning
Develop the plan bringing together the information on projects, resources, timescales, monitoring, and control. [6]
Improvement
Continuously assess performance; research and develop new capabilities, and systemically apply learning and knowledge to the program. [7]

Comparison with project management

There are two different views of how programs differ from projects. In one view, projects deliver outputs, discrete parcels or "chunks" of change; [8] programs create outcomes. [9] In this view, a project might deliver a new factory, hospital or IT system. By combining these projects with other deliverables and changes, their programs might deliver increased income from a new product, shorter waiting lists at the hospital or reduced operating costs due to improved technology. The other view [10] is that a program is nothing more than either a large project or a set (or portfolio) of projects. In this second view, the point of having a program is to exploit economies of scale and to reduce coordination costs and risks. The project manager's job is to ensure that the project succeeds. The program manager, on the other hand, is concerned with the aggregate outcome(s) or end-state result(s) of the collection of projects in a particular program. For example, in a financial institution, a program may include one project that is designed to take advantage of a rising market and another that is designed to protect against the downside of a falling market. The former seeks to leverage the potential upside; the latter to limit the possible downside. A simple analogy is Fix-a-Flat: this highly pressurized aerosol product injects a leak sealant into a punctured tire to stop the outflow of air (project A) and concurrently re-inflates the tire (project B), resulting together in the outcome that a tire that is once again functional (the program comprised projects A and B). [11]

According to the view that "programs deliver outcomes, but projects deliver outputs," program management is concerned with doing the right projects. The program manager has been described as 'playing chess' and keeping the overview in mind, with the pieces to be used or sacrificed being the projects. [12] In contrast, project management is about doing projects right. In other words, a successful project delivers on time, to budget, and to specification, whereas a successful program delivers long-term improvements to an organization. An organization should select the group of programs that most take it towards its strategic aims while remaining within its capacity to deliver the changes. On the other hand, the view that programs are simply large projects or sets of projects allows for when a program may need to deliver tangible benefits quickly.

According to one source, the key difference between a program and a project is the finite nature of a project [13] – a project must always have a specific end date, else it is an ongoing program.

One view of the differences between a program and a project in business is that:

  1. A project is unique and is of definite duration. A program is ongoing and implemented within a business to consistently achieve certain results for the business.
  2. A project is designed to deliver an output or deliverable and its success will be in terms of delivering the right output at the right time and to the right cost.
  3. Program management includes management of projects which, together, improve the performance of the organization. A program's success will be measured in terms of benefits.
  4. Benefits are the measures of improvement of an organization and might include increased income, increased profits, decreased costs, improved market position (ability to compete), reduced wastage or environmental damage, more satisfied customers. In central or local government organizations, benefits might include providing a better service to the community.
  5. In the course of achieving required results, business programs will normally understand related business constraints and determine the processes required to achieve results based on resources allocated. Improvement of processes is a continuous operation that very much contrasts a program from a project.
  6. In the course of achieving required results, business programs will normally understand related business constraints and determine the processes required to achieve results based on resources allocated. Improvement of processes is a continuous operation that is in contrast to the temporary nature of a project.
  7. At the lowest level project managers coordinate individual projects. They are overseen by the program manager who accounts to the program sponsor (or board).
  8. There will normally be a process to change the predetermined scope of a project. Programs often have to react to changes in strategy and changes in the environment in which the organization changes.

Another view and another successful way of managing does not see any of the factors listed above as distinguishing projects from programs, but rather sees the program as being about portfolio management. On this view, program management is about selecting projects, adjusting the speed at which they run, and adjusting their scope, in order to the maximize the value of the portfolio as a whole, and as economic or other external conditions change. Still, some emphasize that whereas a portfolio consists of independent projects, a program is a collection of interdependent projects, adding a dimension of complexity to the management task.

Yet another view is that a program management is nothing more than a large, complex project, where the integration aspect of project management is more important than in smaller projects. Integration management is a key feature of the Project Management Institute's approach to project management. Yet again, some accept there is a distinction related to interdependencies between the elements of a project and a program. In this view, a program is a comparably loosely coupled system, whereas large, complex projects are tightly coupled. This difference makes the project program a more ambiguous task to manage, [14] with more uncertainty, [14] reflecting a higher degree of freedom and a management task more open to exploit opportunities as they arise or the program management becomes aware of them.

In practice, it is not clear that there is a clear-cut distinction. Projects (or programs) vary from small and simple to large and complex; what needs to be managed as a program in one culture or organization may be managed as a project in another.

See also

Related Research Articles

Project management is the process of supervising the work of a team to achieve all project goals within the given constraints. This information is usually described in project documentation, created at the beginning of the development process. The primary constraints are scope, time, and budget. The secondary challenge is to optimize the allocation of necessary inputs and apply them to meet pre-defined objectives.

<span class="mw-page-title-main">Risk management</span> Identification, evaluation and control of risks

Risk management is the identification, evaluation, and prioritization of risks followed by coordinated and economical application of resources to minimize, monitor, and control the probability or impact of unfortunate events or to maximize the realization of opportunities.

<span class="mw-page-title-main">Management accounting</span> Field of business administration, part of the internal accounting system of a company

In management accounting or managerial accounting, managers use accounting information in decision-making and to assist in the management and performance of their control functions.

A project is a type of assignment, typically involving research or design, that is carefully planned to achieve a specific objective.

A business case captures the reasoning for initiating a project or task. Many projects, but not all, are initiated by using a business case. It is often presented in a well-structured written document, but may also come in the form of a short verbal agreement or presentation. The logic of the business case is that, whenever resources such as money or effort are consumed, they should be in support of a specific business need. An example could be that a software upgrade might improve system performance, but the "business case" is that better performance would improve customer satisfaction, require less task processing time, or reduce system maintenance costs. A compelling business case adequately captures both the quantifiable and non-quantifiable characteristics of a proposed project. According to the Project Management Institute, a business case is a "value proposition for a proposed project that may include financial and nonfinancial benefit."

Financial risk management is the practice of protecting economic value in a firm by managing exposure to financial risk - principally operational risk, credit risk and market risk, with more specific variants as listed aside. As for risk management more generally, financial risk management requires identifying the sources of risk, measuring these, and crafting plans to mitigate them. See Finance § Risk management for an overview.

<span class="mw-page-title-main">Business process re-engineering</span> Business management strategy

Business process re-engineering (BPR) is a business management strategy originally pioneered in the early 1990s, focusing on the analysis and design of workflows and business processes within an organization. BPR aims to help organizations fundamentally rethink how they do their work in order to improve customer service, cut operational costs, and become world-class competitors.

Business analysis is a professional discipline focused on identifying business needs and determining solutions to business problems. Solutions may include a software-systems development component, process improvements, or organizational changes, and may involve extensive analysis, strategic planning and policy development. A person dedicated to carrying out these tasks within an organization is called a business analyst or BA.

Project portfolio management (PPM) is the centralized management of the processes, methods, and technologies used by project managers and project management offices (PMOs) to analyze and collectively manage current or proposed projects based on numerous key characteristics. The objectives of PPM are to determine the optimal resource mix for delivery and to schedule activities to best achieve an organization’s operational and financial goals, while honouring constraints imposed by customers, strategic objectives, or external real-world factors. Standards for Portfolio Management include Project Management Institute's framework for project portfolio management, Management of Portfolios by Office of Government Commerce and the PfM² Portfolio Management Methodology by the PM² Foundation.

A project management office is a group or department within a business, government agency, or enterprise that defines and maintains standards for project management within the organization. The PMO strives to standardize and introduce economies of repetition in the execution of projects. The PMO is the source of documentation, guidance, and metrics on the practice of project management and execution.

IT portfolio management is the application of systematic management to the investments, projects and activities of enterprise Information Technology (IT) departments. Examples of IT portfolios would be planned initiatives, projects, and ongoing IT services. The promise of IT portfolio management is the quantification of previously informal IT efforts, enabling measurement and objective evaluation of investment scenarios.

Project governance is the management framework within which project decisions are made. Project governance is a critical element of any project, since the accountabilities and responsibilities associated with an organization's business as usual activities are laid down in their organizational governance arrangements; seldom does an equivalent framework exist to govern the development of its capital investments (projects). For instance, the organization chart provides a good indication of who in the organization is responsible for any particular operational activity the organization conducts. But unless an organization has specifically developed a project governance policy, no such chart is likely to exist for project development activity.

Val IT is a governance framework that can be used to create business value from IT investments. It consists of a set of guiding principles and a number of processes and best practices that are further defined as a set of key management practices to support and help executive management and boards at an enterprise level. The latest release of the framework, published by IT Governance Institute (ITGI), based on the experience of global practitioners and academics, practices and methodologies was named Enterprise Value: Governance of IT Investments, The Val IT Framework 2.0. It covers processes and key management practices for three specific domains and goes beyond new investments to include IT services, assets, other resources and principles and processes for IT portfolio management.

Transition management, in the financial sense, is a service usually offered by sell side institutions to help buy side firms transition a portfolio of securities. Various events including acquisitions and management changes can cause the need for a portfolio to be transitioned. A typical example would be a mutual fund that has decided to merge two funds into one larger fund. In doing this, large quantities of securities will need to be bought and sold. Another frequent occurrence is a firm wanting to liquidate a large portfolio. The process of doing this can be very expensive. The costs include commissions, market impact, bid–offer spreads, and opportunity costs.

A vendor management system (VMS) is an Internet-enabled, often Web-based application that acts as a mechanism for business to manage and procure staffing services – temporary, and, in some cases, permanent placement services – as well as outside contract or contingent labor. Typical features of a VMS application include order distribution, consolidated billing and significant enhancements in reporting capability that outperforms manual systems and processes.

IT Application Portfolio Management (APM) is a practice that has emerged in mid to large-size information technology (IT) organizations since the mid-1990s. Application Portfolio Management attempts to use the lessons of financial portfolio management to justify and measure the financial benefits of each application in comparison to the costs of the application's maintenance and operations.

A glossary of terms relating to project management and consulting.

<span class="mw-page-title-main">Eddie Obeng</span>

Edward David Asihene Obeng is a British organisational theorist, educator, and author, who serves as a professor at Henley Business School and Hult International Business School's Ashridge Executive Education. Obeng founded Pentacle and serves as its executive director. Obeng has been described variously as "a leading revolutionary" and "an agent provocateur" by the Financial Times, and by Abbey National as their "secret weapon".

Benefits realization management (BRM), also benefits management, benefits realisation or project benefits management, is a project management methodology, often visual, addressing how time and resources are invested into making desirable changes. BRM is used to manage the investment by organizations in procurement, projects, programmes and portfolios, and has been shown to increase project success across different countries and industries.

VPMi is a cloud-based suite of Project Portfolio Management software. It allows management for schedules, budgets, scope, alignment, and contains strategies, balanced scorecards, resources and documents. The VPMi suite was created to help prevent miscommunication between business units and IT staff. The VPMi suite originally comprised two software tools, VPMi Professional and VPMi Express, later merged into the new application VPMi. The application is developed by VCSonline, a company headquartered in Valley Park, just outside St. Louis, Missouri, with an additional office in Kolkata, India. VCSonline was mentioned in the 2015 Gartner Magic Quadrant for Cloud-Based IT Project and Portfolio Management Services, Worldwide.

References

Notes

  1. Eddy, Nathan (1 February 2023). "Program Manager Skills: Essential Ones for Building a Career". Dice Insights. Retrieved 13 February 2023.
  2. The Standard for Program Management. Global Standard (2nd ed.). Newtown Square, Pa: Project Management Institute. 2008. ISBN   9781933890524.
  3. Sowden 2011, p. 75.
  4. 1 2 Sowden 2011, p. 107.
  5. Sowden 2011, p. 162.
  6. Managing Successful Programmes, Rod Sowden et al. (TSO, 2011), p107
  7. Sowden 2011, p. 155.
  8. Obeng, Eddie (1994). All Change. London: Financial Times Publishing. ISBN   9780273607625.
  9. Reiss, Geoff; Anthony, Malcolm; Chapman, John; Leigh, Geof; Pyne, Adrian; Rayner, Paul (2006). Gower Handbook of Programme Management. Burlington: Gower Publishing. ISBN   978-0-566-08603-8.
  10. Nokes, Sebastian (2007). The Definitive Guide to Project Management. London: Financial Times/Prentice Hall. ISBN   9781408211984.
  11. "How Project Managers Deal With Opposing Projects in a Financial Programme". Project Laneways. Archived from the original on 7 November 2015. Retrieved 1 June 2015.
  12. Obeng, Eddie (1996). Putting Strategy to Work. London: Financial Times Publishing. ISBN   9780273602651.
  13. Prieto, Robert (14 March 2008). "How Program Management Differs from Project Management". The Project Management Hut. Retrieved 17 October 2009.
  14. 1 2 Project Management Institute 2021, X4.4 Organizational Considerations for Product Management.

Sources

Further reading