Project Management Fundamentals and Core Concepts

Projects, Programs and Portfolios

Project

A project is a temporary endeavor undertaken to create a unique product, service, or result. Projects have defined beginnings and ends, and they are characterized by specific objectives, constraints, and deliverables. For example, developing a new software application is a project that involves planning, executing, and closing phases. Key characteristics of projects include:

• Temporary: Projects have a clear start and finish.
• Unique Deliverables: Each project produces something distinct, whether it’s a product, service, or result.
• Progressive Elaboration: Projects often evolve through iterative processes, allowing for adjustments as more information becomes available.
  Understanding the project lifecycle is essential for effective management, as it guides project managers through initiation, planning, execution, monitoring, and closure.

Program

Portfolio

Projects and Operations

Projects vs Operations

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 aim to achieve strategic objectives and deliver value to the organization. For instance, a company launching a new product line may have several projects: market research, product development, and marketing campaigns. Key aspects of programs include:

• Interdependencies: Projects within a program are interrelated and may share resources or objectives.
• Strategic Alignment: Programs are aligned with organizational goals, ensuring that projects contribute to broader business objectives.
• Benefits Management: Programs focus on delivering benefits and value, often requiring ongoing management and adjustment.
  Effective program management involves balancing project priorities, managing risks, and ensuring stakeholder engagement.

Project Life Cycles

Predictive Life Cycle

A portfolio is a collection of projects and programs that are grouped together to facilitate effective management and meet strategic business objectives. Unlike programs, portfolios may include projects and programs that are not necessarily related but are managed collectively to optimize resource allocation and achieve strategic goals. For example, a technology company may have a portfolio that includes software development projects, infrastructure upgrades, and research initiatives. Key characteristics of portfolios include:

• Strategic Focus: Portfolios are aligned with the organization's strategic objectives, ensuring that all projects and programs contribute to overall goals.
• Resource Management: Portfolios help in optimizing the use of resources across projects and programs, balancing competing demands.
• Performance Monitoring: Portfolio management involves tracking performance metrics to assess the value delivered by the collection of projects and programs.
  Understanding the differences between projects, programs, and portfolios is crucial for effective project management and strategic alignment.

Adaptive Life Cycle

Project Elements

Issues

Understanding the distinction between projects and operations is fundamental in project management. While projects are temporary and aim to create unique outcomes, operations are ongoing and aim to sustain the organization’s core functions. For example, a project might involve developing a new product, while operations would include the ongoing production and delivery of that product. Key differences include:

• Duration: Projects are temporary with a defined start and end, whereas operations are continuous and repetitive.
• Purpose: Projects aim to achieve specific goals and create unique deliverables, while operations focus on efficiency and maintaining business processes.
• Change vs Stability: Projects often introduce change, while operations strive for stability and consistency.
  Recognizing these differences helps project managers allocate resources effectively and manage stakeholder expectations.

Risks

Assumptions

Constraints

Project Scope

Reviewing Project Scope

The predictive life cycle, often referred to as the waterfall model, is a structured approach where project phases are completed sequentially. This methodology is ideal for projects with well-defined requirements and low uncertainty. For example, constructing a building typically follows a predictive life cycle, where each phase (initiation, planning, execution, monitoring, closure) is completed before moving to the next. Key characteristics include:

• Clear Requirements: Requirements are defined upfront, minimizing changes during execution.
• Sequential Phases: Each phase must be completed before the next begins, ensuring thorough documentation and control.
• Risk Management: Predictive approaches allow for detailed risk assessments early in the project.
  While effective for certain projects, the predictive life cycle may be less suitable for projects with evolving requirements.

Professional Ethics

PMI Code of Ethics and Professional Conduct

The adaptive life cycle, often associated with agile methodologies, is an iterative approach that allows for flexibility and responsiveness to change. This methodology is particularly beneficial for projects with high uncertainty or rapidly changing requirements, such as software development. For example, a team developing a mobile app may use sprints to iteratively build and refine features based on user feedback. Key characteristics include:

• Iterative Development: Work is completed in small increments, allowing for regular reassessment and adaptation.
• Stakeholder Engagement: Continuous collaboration with stakeholders ensures that the project aligns with their needs and expectations.
• Emphasis on Value Delivery: The focus is on delivering functional components quickly, providing value throughout the project.
  Adaptive life cycles are ideal for projects where requirements may evolve, enabling teams to pivot as necessary.

Projects as Change Enablers

Projects as a Vehicle for Change

In project management, an issue is an event or situation that has occurred and requires immediate attention. Issues can arise from various sources, such as resource constraints, stakeholder conflicts, or unexpected changes in project scope. For example, if a key team member leaves the project unexpectedly, this creates an issue that must be addressed to avoid delays. Key points regarding issues include:

• Identification: Regular monitoring and communication help identify issues early.
• Resolution: Effective issue resolution involves analyzing the root cause, developing a response plan, and communicating with stakeholders.
• Documentation: Keeping a log of issues and their resolutions aids in future project planning and risk management.
  Proactive issue management is essential for maintaining project momentum and stakeholder trust.