Key Fundamentals of Project Management: Concepts, Goals, and Lifecycle Models

Project Definition

A project is a temporary effort to deliver a unique set of products, services, or results. Project goals combine outcome‑based objectives (meeting customer‑specified deliverables) with constraint‑based objectives (time, cost, quality).

Goal Characteristics

Project goals have varying priorities and a hierarchical structure.

Project Characteristics

Temporariness: a defined start and end date.

Uniqueness: creation of distinct deliverables.

Incremental refinement: early scope is coarse; it becomes detailed as the team’s understanding deepens.

Resource constraints: limited budget, personnel, and equipment.

Purpose‑driven: work is aimed at achieving specific results.

Comparison with Routine Operations

Both involve people, limited resources, and require planning, execution, and control. Routine operations are continuous and repetitive; projects are temporary and unique. Operations maintain business, while projects achieve a defined outcome and then terminate.

Triple Constraint

Project managers balance scope, schedule, and cost. Quality depends on trade‑offs among these three factors; a high‑quality project delivers the required product, service, or result on time and within budget.

Strategic Alignment

Projects are often used to implement organizational strategy, which addresses long‑term, holistic business issues. Strategy management includes formulation, implementation, and evaluation.

Typical Information‑System Project Traits

Unclear objectives

Frequent requirement changes

Knowledge‑intensive

Large design teams

Highly specialized personnel

Many contractors

Distributed contractors with complex interactions

Extensive hardware/software development

Short project lifespans

Adoption of many new technologies

Complex usage and maintenance requirements

Project Management Knowledge Areas

Soft skills: effective communication, influencing, leadership, motivation, negotiation, conflict management, problem solving.

PRINCE2: a process‑based structured method.

PRINCE2 elements: principles, processes, themes, and project environment.

PRINCE2 principles: continued business justification, learning from experience, defined roles and responsibilities, stage‑by‑stage management, exception management, focus on products, tailoring to the project environment.

PRINCE2 themes: business case, organization, quality, plans, risk, change, progress.

Project Organization Structure

Information‑System Project Lifecycle

The lifecycle shows low cost and manpower at the start, a peak during execution, and a rapid decline near completion. Risk and uncertainty are highest at initiation and decrease as decisions are made and deliverables are accepted. Early stages allow the greatest flexibility to change product characteristics without significantly affecting cost.

Lifecycle Phases

Each phase has a distinct focus, often involving different organizations, locations, and skill sets. Phase completion is marked by a deliverable hand‑over, review, and a decision point (milestone, gate, or key review).

Typical Lifecycle Models

Waterfall Model

Sequential stages: feasibility (planning), requirements analysis, high‑level and detailed design, coding (including unit testing), testing, and operation/maintenance. Each activity consumes the output of the previous one, produces an output, and undergoes review. Suitable for projects with stable, well‑defined requirements, weaker development teams, solid industry practices, and single‑batch delivery.

Spiral Model

Combines iterative prototyping with the structured control of the waterfall. Development proceeds through repeated cycles of planning, risk analysis, engineering, and customer evaluation, emphasizing risk analysis for large, complex, high‑risk systems.

Iterative Development Model

Four phases:

Initiation – define scope, select architecture, prepare business case.

Refinement – detail concepts, processes, infrastructure, and architecture.

Construction – manage resources, optimize processes, develop components, test against acceptance criteria.

Transition – integrate increments, evaluate against acceptance criteria.

Workload varies over time, but all activities occur throughout the project.

Iterative vs. Incremental Comparison

V‑Model

Left side shows development activities (requirements analysis, high‑level design, detailed design, coding); right side shows corresponding test levels (unit, integration, system, acceptance). Emphasizes equal importance of development and testing; each development stage links to a specific test level. Best suited for projects with clear, stable requirements.

Prototype Method

When user requirements cannot be fully defined upfront, a quick prototype is built based on the developer’s preliminary understanding and iteratively refined to meet final needs. Prototype characteristics: feasible, embody core system features, easy and low‑cost to build. Types include throwaway and evolutionary prototypes.

Agile Development Model

People‑centric, iterative, and incremental. Emphasizes close collaboration between developers and business experts, frequent communication, rapid delivery of small increments (2‑4 weeks), change‑driven development, and self‑organizing teams. Scrum, a popular agile framework, defines three roles, three artifacts, and four ceremonies.

Lifecycle Model Comparison

Project Management Process Groups

Initiating, Planning, Executing, Monitoring & Controlling, Closing. These five groups apply to all projects and map to the PDCA (Plan‑Do‑Check‑Act) cycle. Initiating includes charter creation and stakeholder identification; Closing includes finalizing the project or phase and ending procurements.