the-standard-for-portfolio-management

The Standard for Portfolio Management

  • The Standard for Portfolio Management describes a suite of best practices for portfolio management with respect to projects, programs, and organizational strategy.
  • The Standard for Portfolio Management defines vocabulary that portfolio managers can use in their professional careers. SfPfM uses a combination of well-established and process-specific terms.
  • The Standard for Portfolio Management is predominantly focused on helping businesses attain goals and objectives. This can be facilitated by considering six key areas that detail resource allocation, alignment, and risk management.
AspectExplanation
DefinitionThe “Standard for Portfolio Management” is a set of guidelines and best practices developed by professional organizations, such as the Project Management Institute (PMI), to facilitate effective portfolio management within organizations. It provides a structured framework for selecting, prioritizing, and managing a portfolio of projects and programs to align with an organization’s strategic goals and objectives. This standard outlines principles, processes, and techniques to optimize resource allocation, monitor performance, and ensure that investments deliver value and contribute to overall success.
Key ConceptsPortfolio Management: The practice of overseeing and controlling a collection of projects and programs to achieve strategic objectives. – Alignment: Ensuring that the portfolio aligns with the organization’s strategic goals. – Prioritization: The process of selecting and ranking projects based on their potential impact and contribution to strategic objectives. – Resource Optimization: Balancing resource allocation across projects and programs for optimal utilization. – Performance Monitoring: Continuously monitoring project and program performance to make informed decisions. – Value Delivery: Ensuring that projects and programs deliver value to the organization.
CharacteristicsStrategic Focus: Portfolio management is driven by the organization’s strategic direction and objectives. – Continuous Evaluation: Ongoing assessment and adjustments are made to the portfolio as conditions change. – Resource Allocation: Effective allocation and reallocation of resources based on portfolio priorities. – Risk Management: Addressing risks and uncertainties associated with projects and programs. – Value Maximization: Maximizing the value generated from the portfolio investments. – Alignment with Strategy: Ensuring that every project contributes to the strategic goals.
ImplicationsStrategic Execution: Effective portfolio management ensures that the organization executes its strategy through the right projects and programs. – Resource Efficiency: Optimizing resource allocation leads to better resource utilization and cost control. – Risk Mitigation: Identifying and mitigating risks at the portfolio level reduces potential disruptions. – Value Realization: Ensuring that the organization derives value from its investments by selecting and managing projects effectively. – Competitive Advantage: Portfolio management can give an organization a competitive edge by aligning its efforts with its strategic objectives.
AdvantagesStrategic Alignment: Ensures that the portfolio of projects and programs supports the organization’s strategic objectives. – Resource Optimization: Balances resource allocation to maximize efficiency and minimize waste. – Risk Management: Identifies and addresses risks at the portfolio level, reducing potential disruptions. – Value Delivery: Ensures that projects and programs contribute to the organization’s value creation. – Performance Monitoring: Continuously assesses performance to make informed decisions and adjustments.
DrawbacksComplexity: Implementing portfolio management can be complex, requiring significant organizational change. – Resource Constraints: Limited resources may challenge the allocation and execution of projects. – Resistance to Change: Stakeholders may resist changes to existing project selection and management processes. – Initial Investment: Establishing portfolio management processes and tools may require an initial investment. – Data Quality: Relies on accurate and timely data for effective decision-making.
ApplicationsBusiness: Used in business environments to manage a portfolio of projects, product development, and initiatives. – Government: Applied in government organizations to align projects and programs with public policies and objectives. – Nonprofits: Used by nonprofit organizations to optimize resource allocation and achieve their missions. – Healthcare: Applied in healthcare to prioritize and manage projects and programs that improve patient care and services. – IT: Used in IT departments to select and manage a portfolio of technology projects and initiatives.
Use CasesProject Selection: Prioritizing and selecting projects that align with the organization’s strategic goals. – Resource Allocation: Allocating resources efficiently across projects and programs. – Risk Management: Identifying and addressing risks that could impact the portfolio’s success. – Value Measurement: Measuring and quantifying the value delivered by the portfolio investments. – Performance Monitoring: Continuously assessing the performance of projects and programs.
Future TrendsData Analytics: Increasing use of data analytics and artificial intelligence for portfolio optimization and decision-making. – Agile Portfolio Management: Adoption of agile practices in portfolio management to enhance flexibility and responsiveness. – Digital Transformation: Integration of digital tools and platforms for portfolio management processes. – Sustainability Focus: Greater emphasis on integrating sustainability and environmental factors into portfolio decision-making. – Economic Uncertainty: Strategies to adapt portfolios to economic uncertainties and disruptions.

Standard/Framework for Portfolio ManagementDescriptionKey Insights
Project Management Institute (PMI) Standard for Portfolio ManagementDeveloped by PMI, it provides guidance and best practices for portfolio managementEmphasizes aligning portfolio decisions with organizational strategy and objectives.
The Standard for Portfolio Management by The Portfolio Management Institute (PfMI)Published by PfMI, it offers a comprehensive framework for portfolio managementFocuses on governance, optimization, and strategic alignment of portfolios.
The Portfolio, Programme, and Project Management Maturity Model (P3M3)An assessment framework that evaluates an organization’s maturity in portfolio managementHelps organizations identify areas for improvement and enhance portfolio management capabilities.
PRINCE2 (Projects IN Controlled Environments)A process-driven project management methodology that includes portfolio managementIntegrates portfolio management as part of its project and program management approach.
The Open Group Architecture Framework (TOGAF)An enterprise architecture methodology that includes portfolio management aspectsEnsures alignment of IT portfolios with business objectives and architectural standards.
ISO 21504:2015 (Guidance on Portfolio Management)An international standard offering guidance on portfolio management practicesProvides a globally recognized framework for effective portfolio management.
A Guide to the Project Management Body of Knowledge (PMBOK Guide)Developed by PMI, it covers portfolio management within its project management frameworkAddresses portfolio management processes, governance, and alignment with strategic objectives.
Agile Portfolio Management Frameworks (e.g., SAFe, Disciplined Agile)Frameworks that adapt agile principles to portfolio managementSupport agile organizations in managing portfolios with flexibility and responsiveness.
COBIT (Control Objectives for Information and Related Technologies)A framework for governance and management of enterprise IT, including portfolio managementEnsures IT portfolios align with business goals, risks are managed, and resources are optimized.
Benefits Realization Management (BRM) FrameworkFocuses on tracking and realizing expected benefits from portfoliosEnhances accountability for delivering value and benefits.
ITIL (Information Technology Infrastructure Library)A set of practices for IT service management that includes portfolio managementEnsures IT services and projects align with business needs and objectives.
The Agile Practice GuidePublished by PMI and the Agile Alliance, it addresses portfolio management in agile environmentsPromotes flexibility, adaptability, and value delivery in agile portfolio management.
Organizational Project Management (OPM)An approach that integrates portfolio, program, and project managementAligns all levels of organizational work with strategic objectives.
Strategic Portfolio Management (SPM)An approach that focuses on aligning portfolios with an organization’s strategic goalsPrioritizes projects and initiatives that contribute most to strategic objectives.
IT Portfolio Management (ITPM)A specialized approach for managing IT portfoliosEnsures that IT investments support the organization’s IT strategy and objectives.
Lean Portfolio Management (LPM)Part of the SAFe framework, it applies lean and agile principles to portfolio managementMaximizes the flow of value, minimizes delays, and fosters collaboration in portfolio management.

The Standard for Portfolio Management (SfPfM) describes a suite of portfolio management processes concerning programs, projects, and organizational strategy. The Standard for Portfolio Management is a creation of the Project Management Institute (PMI).

Understanding The Standard for Portfolio Management

In compiling a list of portfolio management processes, the PMI ensured that each approach satisfied two criteria:

Must be “generally recognized”

They must be “generally recognized” in the sense that knowledge and practices apply to most portfolios most of the time.

There must also be relatively widespread agreement regarding their value and usefulness.

Must be “good practice”

They must be “good practice”, with general agreement that the combination of tools, skills, and techniques can contribute to the success of many different portfolios.

Here, good practice does not mean that knowledge or methods are applied uniformly.

Must share a common vocabulary

There is still a requirement that portfolio managers identify what is most appropriate to their needs.

The Standard for Portfolio Management also details a common vocabulary that professionals can use when discussing or applying aspects of portfolio management.

The Standard for Portfolio Management definitions

Here are some of the core definitions of SfPfM:

Portfolio

A collection of programs and projects grouped to facilitate the completion of work in meeting strategic goals and objectives.

Projects and programs do not need to be related or interdependent.

Portfolio management

The coordinated and continuous management of one or more portfolios using interrelated processes that support decision making.

The business must consistently evaluate, prioritize, and allocate resources to ensure that portfolios meet strategic goals.

Aligning Process Group

A group of individuals that determine how portfolio components will be categorized, evaluated, and managed for potential inclusion in a portfolio.

Monitoring and Controlling Process Group

Who periodically review portfolio KPIs to determine whether they are contributing to company success.

Portfolio management and organizational strategy

The PMI note that the ultimate goal of SfPfM is to link it with organizational strategy to establish a business plan that is both balanced and executable.

Businesses can develop this plan by addressing six different areas:

Maintaining portfolio alignment

While each portfolio should be aligned to strategic objectives, this alignment cannot occur if the business does not understand what its objectives are.

Each new or pre-existing portfolio component must support the fulfillment of company strategy.

Allocating financial resources

Resource allocation is tied to the prioritization of portfolio components.

Allocating human resources

High-priority portfolio components receive funding for resource planning, recruitment, scheduling, and the training or upskilling of talent long-term.

Allocating material or equipment resources

Each component must be allocated information, equipment, or space.

This includes capital investment to ensure that the needs of each component are met at the organizational level – including needs related to constraints.

Measuring portfolio component performance

Portfolio performance must only be measured in the context of whether the portfolio helped achieved a strategic goal.

Managing risk

Each component should be routinely evaluated for internal and external risks that might prevent strategic goals from being achieved.

Key takeaways

  • The Standard for Portfolio Management (SfPfM): The Standard for Portfolio Management is a set of best practices created by the Project Management Institute (PMI) that outlines portfolio management processes related to programs, projects, and organizational strategy.
  • Criteria for Portfolio Management Processes: The PMI established two criteria for including portfolio management processes in the standard:
    • Processes must be “generally recognized,” meaning they apply to most portfolios most of the time and have widespread agreement on their value.
    • Processes must be “good practice,” indicating that a combination of tools, skills, and techniques can contribute to the success of various portfolios.
  • Common Vocabulary: The SfPfM provides a common vocabulary that professionals can use to discuss and apply portfolio management concepts.
  • Core Definitions in SfPfM:
    • Portfolio: A collection of programs and projects grouped to achieve strategic goals and objectives. Components need not be related or interdependent.
    • Portfolio Management: Coordinated and continuous management of one or more portfolios through interrelated processes to support decision-making.
    • Aligning Process Group: A group that categorizes, evaluates, and manages portfolio components for potential inclusion.
    • Monitoring and Controlling Process Group: Periodically reviews portfolio Key Performance Indicators (KPIs) to determine their contribution to company success.
  • Linking Portfolio Management and Organizational Strategy: The ultimate goal of SfPfM is to link portfolio management with organizational strategy to establish a balanced and executable business plan.
  • Six Areas for Business Plan Development:
    • Maintaining Portfolio Alignment: Ensure each portfolio component supports fulfilling company strategy.
    • Allocating Financial Resources: Allocate resources based on component prioritization.
    • Allocating Human Resources: Prioritize high-priority components for resource planning, recruitment, and training.
    • Allocating Material or Equipment Resources: Allocate resources including capital investment to meet component needs.
    • Measuring Portfolio Component Performance: Measure portfolio performance in the context of achieving strategic goals.
    • Managing Risk: Evaluate each component for internal and external risks that could impact strategic goal achievement.
  • Key Takeaways: The Standard for Portfolio Management provides best practices for portfolio management processes, offering a common vocabulary for professionals. It aims to help businesses achieve their goals and objectives by considering resource allocation, alignment, and risk management across six key areas.

What are the premises of portfolio management?

What the definitions of portfolio management?

How do you align portfolio management and organizational strategy?

Connected Agile Frameworks

AIOps

aiops
AIOps is the application of artificial intelligence to IT operations. It has become particularly useful for modern IT management in hybridized, distributed, and dynamic environments. AIOps has become a key operational component of modern digital-based organizations, built around software and algorithms.

Agile Methodology

agile-methodology
Agile started as a lightweight development method compared to heavyweight software development, which is the core paradigm of the previous decades of software development. By 2001 the Manifesto for Agile Software Development was born as a set of principles that defined the new paradigm for software development as a continuous iteration. This would also influence the way of doing business.

Agile Project Management

agile-project-management
Agile project management (APM) is a strategy that breaks large projects into smaller, more manageable tasks. In the APM methodology, each project is completed in small sections – often referred to as iterations. Each iteration is completed according to its project life cycle, beginning with the initial design and progressing to testing and then quality assurance.

Agile Modeling

agile-modeling
Agile Modeling (AM) is a methodology for modeling and documenting software-based systems. Agile Modeling is critical to the rapid and continuous delivery of software. It is a collection of values, principles, and practices that guide effective, lightweight software modeling.

Agile Business Analysis

agile-business-analysis
Agile Business Analysis (AgileBA) is certification in the form of guidance and training for business analysts seeking to work in agile environments. To support this shift, AgileBA also helps the business analyst relate Agile projects to a wider organizational mission or strategy. To ensure that analysts have the necessary skills and expertise, AgileBA certification was developed.

Business Model Innovation

business-model-innovation
Business model innovation is about increasing the success of an organization with existing products and technologies by crafting a compelling value proposition able to propel a new business model to scale up customers and create a lasting competitive advantage. And it all starts by mastering the key customers.

Continuous Innovation

continuous-innovation
That is a process that requires a continuous feedback loop to develop a valuable product and build a viable business model. Continuous innovation is a mindset where products and services are designed and delivered to tune them around the customers’ problem and not the technical solution of its founders.

Design Sprint

design-sprint
A design sprint is a proven five-day process where critical business questions are answered through speedy design and prototyping, focusing on the end-user. A design sprint starts with a weekly challenge that should finish with a prototype, test at the end, and therefore a lesson learned to be iterated.

Design Thinking

design-thinking
Tim Brown, Executive Chair of IDEO, defined design thinking as “a human-centered approach to innovation that draws from the designer’s toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success.” Therefore, desirability, feasibility, and viability are balanced to solve critical problems.

DevOps

devops-engineering
DevOps refers to a series of practices performed to perform automated software development processes. It is a conjugation of the term “development” and “operations” to emphasize how functions integrate across IT teams. DevOps strategies promote seamless building, testing, and deployment of products. It aims to bridge a gap between development and operations teams to streamline the development altogether.

Dual Track Agile

dual-track-agile
Product discovery is a critical part of agile methodologies, as its aim is to ensure that products customers love are built. Product discovery involves learning through a raft of methods, including design thinking, lean start-up, and A/B testing to name a few. Dual Track Agile is an agile methodology containing two separate tracks: the “discovery” track and the “delivery” track.

Feature-Driven Development

feature-driven-development
Feature-Driven Development is a pragmatic software process that is client and architecture-centric. Feature-Driven Development (FDD) is an agile software development model that organizes workflow according to which features need to be developed next.

eXtreme Programming

extreme-programming
eXtreme Programming was developed in the late 1990s by Ken Beck, Ron Jeffries, and Ward Cunningham. During this time, the trio was working on the Chrysler Comprehensive Compensation System (C3) to help manage the company payroll system. eXtreme Programming (XP) is a software development methodology. It is designed to improve software quality and the ability of software to adapt to changing customer needs.

Lean vs. Agile

lean-methodology-vs-agile
The Agile methodology has been primarily thought of for software development (and other business disciplines have also adopted it). Lean thinking is a process improvement technique where teams prioritize the value streams to improve it continuously. Both methodologies look at the customer as the key driver to improvement and waste reduction. Both methodologies look at improvement as something continuous.

Lean Startup

startup-company
A startup company is a high-tech business that tries to build a scalable business model in tech-driven industries. A startup company usually follows a lean methodology, where continuous innovation, driven by built-in viral loops is the rule. Thus, driving growth and building network effects as a consequence of this strategy.

Kanban

kanban
Kanban is a lean manufacturing framework first developed by Toyota in the late 1940s. The Kanban framework is a means of visualizing work as it moves through identifying potential bottlenecks. It does that through a process called just-in-time (JIT) manufacturing to optimize engineering processes, speed up manufacturing products, and improve the go-to-market strategy.

Rapid Application Development

rapid-application-development
RAD was first introduced by author and consultant James Martin in 1991. Martin recognized and then took advantage of the endless malleability of software in designing development models. Rapid Application Development (RAD) is a methodology focusing on delivering rapidly through continuous feedback and frequent iterations.

Scaled Agile

scaled-agile-lean-development
Scaled Agile Lean Development (ScALeD) helps businesses discover a balanced approach to agile transition and scaling questions. The ScALed approach helps businesses successfully respond to change. Inspired by a combination of lean and agile values, ScALed is practitioner-based and can be completed through various agile frameworks and practices.

Spotify Model

spotify-model
The Spotify Model is an autonomous approach to scaling agile, focusing on culture communication, accountability, and quality. The Spotify model was first recognized in 2012 after Henrik Kniberg, and Anders Ivarsson released a white paper detailing how streaming company Spotify approached agility. Therefore, the Spotify model represents an evolution of agile.

Test-Driven Development

test-driven-development
As the name suggests, TDD is a test-driven technique for delivering high-quality software rapidly and sustainably. It is an iterative approach based on the idea that a failing test should be written before any code for a feature or function is written. Test-Driven Development (TDD) is an approach to software development that relies on very short development cycles.

Timeboxing

timeboxing
Timeboxing is a simple yet powerful time-management technique for improving productivity. Timeboxing describes the process of proactively scheduling a block of time to spend on a task in the future. It was first described by author James Martin in a book about agile software development.

Scrum

what-is-scrum
Scrum is a methodology co-created by Ken Schwaber and Jeff Sutherland for effective team collaboration on complex products. Scrum was primarily thought for software development projects to deliver new software capability every 2-4 weeks. It is a sub-group of agile also used in project management to improve startups’ productivity.

Scrum Anti-Patterns

scrum-anti-patterns
Scrum anti-patterns describe any attractive, easy-to-implement solution that ultimately makes a problem worse. Therefore, these are the practice not to follow to prevent issues from emerging. Some classic examples of scrum anti-patterns comprise absent product owners, pre-assigned tickets (making individuals work in isolation), and discounting retrospectives (where review meetings are not useful to really make improvements).

Scrum At Scale

scrum-at-scale
Scrum at Scale (Scrum@Scale) is a framework that Scrum teams use to address complex problems and deliver high-value products. Scrum at Scale was created through a joint venture between the Scrum Alliance and Scrum Inc. The joint venture was overseen by Jeff Sutherland, a co-creator of Scrum and one of the principal authors of the Agile Manifesto.

Read Also: Business Models Guide, Sumo Logic Business Model, Snowflake

InnovationAgile MethodologyLean StartupBusiness Model InnovationProject Management.

Main Free Guides:

Scroll to Top

Discover more from FourWeekMBA

Subscribe now to keep reading and get access to the full archive.

Continue reading

FourWeekMBA