Introduction
Open in the Padhaiko app1.1 Definition of project and project management
Project (PMI Definition)
According to the Project Management Institute (PMI), a project is a temporary endeavor undertaken to create a unique product, service, or result.
Key defining characteristics of every project:
- Temporary: Has a definite beginning and a definite end (either when objectives are achieved, or when the project is terminated because objectives cannot be met or the need no longer exists). Temporary does not mean short in duration; it means the engagement is bounded in time.
- Unique Deliverable: Produces a distinct product, service, or result (e.g., building a university ERP portal, deploying a campus Wi-Fi network, or migrating a bank's core database). Even when similar projects share templates, each has different stakeholders, locations, requirements, and constraints.
- Progressive Elaboration: Characteristics of the product or service are developed in steps and refined as more information becomes available during planning and execution.
- Cross-Functional & Resource-Constrained: Operates with limited budget, schedule, and skilled personnel, often cutting across organizational departments.
- Uncertainty and Risk: Because the deliverable is unique, every project carries technical, schedule, and cost uncertainties.
A project differs fundamentally from ongoing operations (routine, repetitive activities that sustain the business):
| Aspect | Project | Operations |
|---|---|---|
| Time Horizon | Temporary (fixed start and end dates) | Ongoing and repetitive (continuous) |
| Output | Unique product, service, or capability | Standardized, repetitive products or services |
| Purpose | Attain objective and conclude (drive change) | Sustain the organization's day-to-day business |
| Team Structure | Cross-functional, disbanded upon closure | Functional, permanent departmental teams |
| Risk Profile | Higher uncertainty due to novelty | Lower uncertainty due to established routines |
| ICT Example | Developing and launching an e-commerce mobile app | Daily server uptime monitoring and helpdesk support |
Project Management
Project management is the application of knowledge, skills, tools, and techniques to project activities to meet the project requirements.
Project management is accomplished through the structured integration of process groups (Initiating, Planning, Executing, Monitoring and Controlling, and Closing) while balancing competing constraints—chiefly scope, schedule, budget, quality, resources, and risk.
1.2 Project objectives
Every project is launched to achieve specific, measurable business or technical outcomes. Project objectives specify what must be delivered, when it must be completed, and at what cost and quality.
The Triple Constraint (and Extended Constraints)
Traditionally, project objectives are framed around the Triple Constraint (the Iron Triangle):
- Scope: What work must be done and what unique features/functions the final deliverable must contain.
- Time (Schedule): How long the project is permitted to take and key milestone/completion dates.
- Cost (Budget): The approved financial limit required to complete the project.
In modern ICT project management (PMI), Quality sits at the center of the triangle alongside Resources and Risk—a change in any one constraint inevitably forces an adjustment in at least one other constraint.
Well-formulated project objectives follow the SMART criteria:
1.3 Classification of projects
Projects can be classified along several practical dimensions depending on their industry, uncertainty, size, and sponsorship:
| Classification Criterion | Categories | Characteristics & ICT Examples |
|---|---|---|
| 1. Nature / Output | Construction, Manufacturing, Research & Development (R&D), ICT / Software, Service | ICT projects build software applications, cloud infrastructure, telecom networks, or cybersecurity platforms. |
| 2. Clarity of Goal vs. Method (Turner & Cochrane) | Type 1 (Clear Goal & Method), Type 2 (Clear Goal, Unclear Method), Type 3 (Unclear Goal, Clear Method), Type 4 (Both Unclear) | Infrastructure upgrades are Type 1; new software R&D is Type 2 or Type 3; exploratory AI startups are Type 4. |
| 3. Scale & Complexity | Small, Medium, Large / Mega-projects | Small: departmental web portal; Mega: national digital ID or nationwide 5G rollout. |
| 4. Ownership / Funding | Public (Government), Private, Public–Private Partnership (PPP), NGO / Donor-funded | E-governance portals (Public); fintech apps (Private); smart-city fiber grids (PPP). |
| 5. Urgency & Need | Normal, Crash (Expedited), Disaster Recovery | Normal: planned ERP upgrade; Crash: emergency zero-day patch or compliance deadline; Disaster: post-outage data center rebuild. |
| 6. ICT Project Type | Software Development, Infrastructure & Networking, System Integration, Data Migration / Analytics, Maintenance / Upgrade | Each demands distinct technical skills, risk profiles, and lifecycle choices. |
1.4 Advantages of project management
Adopting formal project management practices provides measurable advantages over ad-hoc execution:
- Better Control of Financial, Physical, and Human Resources: Clear budgeting, resource allocation, and tracking prevent cost overruns and idle team members.
- Improved Customer Relations: Structured communication, requirement sign-offs, and milestone demos align deliverables with client expectations.
- Shorter Development Times: Critical path scheduling, dependency management, and early bottleneck detection compress time-to-market.
- Lower Costs and Higher Profit Margins: Early defect detection, scope control, and risk mitigation prevent expensive late-stage rework.
- Higher Quality and Increased Reliability: Formal quality assurance, testing gates, and configuration management yield more dependable systems.
- Higher Worker Morale and Productivity: Defined roles, realistic workloads, and clear priorities reduce burnout and confusion.
- Sharper Focus on Strategic Alignment: Linking projects to business cases ensures resources fund high-value initiatives rather than pet projects.
1.5 Project management context as per project management institute (PMI)
Projects do not exist in isolation—they operate within a broader organizational, social, technical, and regulatory context. As defined by PMI (PMBOK), the project management context encompasses the environment and foundational concepts within which projects are governed and executed:
Core Elements of PMI Project Management Context
- Program, Portfolio, and Project Hierarchy: Projects often sit inside programs (groups of related projects managed together for shared benefits) and portfolios (collections of programs, projects, and operations aligned to strategic business goals).
- Project Life Cycle and Product Life Cycle: The project life cycle covers the temporary phases from initiation to closure, whereas the product life cycle spans the entire lifespan of the resulting system from conception through retirement.
- Stakeholders: Individuals, groups, or organizations who may affect, be affected by, or perceive themselves to be affected by a project (sponsors, customers, end users, project team, vendors, regulators).
- Organizational Influences: Organizational culture, structure (functional, matrix, projectized), Enterprise Environmental Factors (EEFs), and Organizational Process Assets (OPAs) strongly shape authority and workflow.
- Interpersonal and General Management Skills: Leadership, negotiation, communication, conflict resolution, and domain knowledge complement technical scheduling and budgeting tools.
- Socio-Economic and Regulatory Environment: Standards (ISO, IEEE), data-privacy laws, procurement rules, cultural norms, and economic conditions constrain how ICT projects operate.
1.6 ICT product life cycle and its characteristics
An ICT product life cycle describes the complete progression of an information and communication technology product or system—from initial business idea through development, market deployment, operational support, and eventual decommissioning.
Phases of the ICT Product Life Cycle
A typical ICT product passes through five broad stages:
- Conception & Feasibility: Business need identification, market/technical feasibility study, and initial project chartering.
- Design & Development (Project Phase): Requirements engineering, system architecture, coding/integration, testing, and quality assurance.
- Deployment & Introduction: Installation, data migration, user training, rollout, and transition to operations.
- Operation, Maintenance & Growth: Day-to-day support, bug fixes, security patching, feature updates, and scaling as user adoption grows.
- Maturity & Retirement (Decommissioning): Legacy replacement, data archiving, license termination, and controlled system shutdown.
Relationship Between Project Life Cycle and Product Life Cycle
A single ICT product often spawns multiple sequential projects across its product life cycle: e.g., Project 1 builds Version 1.0, Project 2 migrates the system to the cloud, Project 3 adds a mobile client, and Project 4 executes end-of-life data migration.
Characteristics of the Project Life Cycle
Regardless of domain, most project life cycles share common structural characteristics:
- Cost and Staffing Levels: Start low during initiation, peak rapidly during execution, and drop sharply as the project approaches closure.
- Risk and Stakeholder Influence: Uncertainty and stakeholder ability to influence final product characteristics are highest at the start and decline progressively as the project moves toward completion.
- Cost of Changes: The cost of correcting an error or changing a requirement increases exponentially the later it is discovered in the life cycle.
1.7 Overview of system development methodologies
System development methodologies define how the technical work of building an ICT product is structured across the life cycle. Methodologies fall along a spectrum from predictive (plan-driven) to adaptive (change-driven).
| Methodology | Core Approach | Best Suited For | Key Strengths | Key Limitations |
|---|---|---|---|---|
| Waterfall (Predictive) | Linear sequential phases: Requirements Design Implementation Testing Deployment | Stable, well-understood requirements (e.g., government compliance, embedded firmware) | Clear milestones, thorough documentation, predictable budgets | Poor tolerance for late requirement changes; working software appears late |
| V-Model | Extension of Waterfall pairing each development stage with a corresponding verification/testing stage | Safety-critical and mission-critical systems (healthcare, telecom switches) | Rigorous traceability between requirements and test cases | Rigid; expensive to revise early specifications |
| Iterative & Incremental | Builds the system in repeated cycles (iterations), delivering functional increments in each release | Medium-to-large enterprise systems where core features ship early | Early user feedback, reduced integration risk | Requires careful architecture planning to avoid rework |
| Spiral Model (Boehm) | Risk-driven iterative cycles combining planning, risk analysis, engineering, and customer evaluation | High-risk, large, complex, or unprecedented ICT systems | Explicit risk evaluation in every cycle | Complex to manage; costly risk-assessment overhead for small projects |
| Prototyping / RAD | Rapidly constructs working mockups/prototypes to clarify unclear user interfaces and requirements | Projects with vague UI/UX needs or tight delivery windows | Validates user needs early; high user engagement | Risk of "throwaway" prototype code shipping to production |
| Agile (Scrum / Kanban) | Adaptive, short time-boxed iterations (sprints) with continuous customer collaboration and working software | Dynamic business environments with evolving requirements (web/mobile/SaaS) | Fast value delivery, high adaptability, transparent progress | Hard to fix total scope and cost upfront; relies on active client involvement |
| DevOps / CI-CD | Integrates development and IT operations via automated build, test, deployment, and monitoring pipelines | Cloud-native platforms requiring frequent, reliable production releases | Rapid deployment frequency, lower failure recovery time | Requires cultural shift and significant automation tooling |
Worked Out Examples
1.1
A software firm plans to build a university examination portal (ICT project). Initial estimates show the project requires developers working for working days at a uniform rate of per developer-day.
- Calculate the baseline labor cost of the project.
- During execution, the university requests an additional online-proctoring module that increases total effort by . Compute the revised labor cost if daily rates remain unchanged.
- If the management enforces the original -day deadline despite the scope increase (assuming zero communication overhead), how many developer-days are needed in total, and if the team is expanded to developers, how many days will the revised scope actually take?
Computing the baseline labor effort and cost: Baseline effort in developer-days is:
At per developer-day, the baseline labor cost is:
Applying the scope increase (Triple Constraint impact on Cost):
The revised effort and cost are:
Computing revised duration with an expanded -developer team: With developers working in parallel (ignoring Brooks's Law communication overhead):
Because , expanding the team from to developers accommodates the scope addition within the original -day schedule, at the higher budget of .
- Baseline labor cost: ( developer-days).
- Revised labor cost after scope increase: ( developer-days).
- With developers, the revised scope takes (meeting the -day deadline).
1.2
Exam-Style Scenario (Methodology Selection & Project Classification): A provincial health ministry hires an ICT vendor to build a real-time telemedicine and patient-record platform. Core regulatory compliance and patient data-privacy rules are fixed by law, whereas the clinician mobile UI workflows are still evolving based on doctor feedback.
- Classify this project across three dimensions (nature, ownership, and goal/method clarity).
- Recommend and justify an appropriate system development methodology, comparing why a pure Waterfall approach would fail here.
Classifying the project across three dimensions:
- Nature / Output: ICT / Software Development & System Integration project (involves application software, cloud hosting, and medical data security).
- Ownership / Funding: Public (Government-funded) or Public–Private Partnership (PPP) if operated jointly with a private vendor.
- Goal vs. Method Clarity (Turner & Cochrane): Type 2 / Type 3 hybrid—compliance goals are clear, while optimal clinician UX workflows require iterative discovery.
Selecting and justifying the development methodology:
- Recommended Methodology: Iterative & Incremental (or Hybrid Agile / V-Model)—lock regulatory security and database schemas upfront using structured verification, while delivering clinician UI modules in short -week Agile sprints with doctor feedback.
- Why Pure Waterfall Fails: Pure Waterfall freezes all UI requirements before coding begins. Because clinician workflows are still evolving, late discovery of usability issues under Waterfall would require costly late-stage rework, violating schedule and budget objectives.
The project is a Public (or PPP) ICT Software & Integration project with mixed clarity (fixed regulatory goals, evolving UX). A Hybrid Iterative / Agile methodology is recommended so compliance modules follow strict verification gates while clinician workflows evolve through rapid sprint feedback—avoiding the late-stage rework inherent to pure Waterfall.
Exercises
Practice Exercises — Introduction to ICT Project Management
Define a project and project management according to PMI. Distinguish clearly between a project and ongoing operations with suitable ICT examples.
PMI definitions:
- A project is a temporary endeavor undertaken to create a unique product, service, or result. It has a definite start and end, produces a unique output, and undergoes progressive elaboration.
- Project management is the application of knowledge, skills, tools, and techniques to project activities to meet project requirements.
Key distinctions between a project and operations:
- Duration: Projects are temporary with defined start/end dates; operations are continuous and repetitive.
- Output: Projects produce unique deliverables (e.g., deploying a hospital EHR system); operations deliver repetitive outputs (e.g., daily database backups and user helpdesk support).
- Purpose: Projects drive change and terminate once objectives are met; operations sustain day-to-day business continuity.
A project is a temporary endeavor creating a unique deliverable, and project management applies knowledge, tools, and techniques to meet its requirements. Unlike operations (continuous, repetitive business-sustaining work such as IT support), projects are time-bounded and produce unique outcomes (such as building a new software system).
Explain the Triple Constraint of project objectives and the SMART criteria for writing effective project objectives. Give one SMART objective for an ICT project.
Triple Constraint and SMART framework:
- The Triple Constraint balances Scope (what must be delivered), Time (schedule deadline), and Cost (approved budget), centered around Quality. Changing any one parameter impacts the others.
- SMART stands for Specific, Measurable, Achievable, Relevant, and Time-bound.
Example of a SMART ICT project objective: "Design, test, and deploy the student fee-payment module for the college ERP supporting eSewa and ConnectIPS with transaction response time within a budget of by July 31."
Project objectives are governed by the Triple Constraint (Scope, Time, Cost, plus Quality) and should be SMART (Specific, Measurable, Achievable, Relevant, Time-bound). For example: deploying a college ERP payment module with response time within by July 31.
Describe the ICT product life cycle and explain how it differs from a project life cycle. List four characteristics that make ICT projects uniquely challenging.
ICT Product Life Cycle vs. Project Life Cycle:
- The ICT product life cycle spans the entire existence of a technology system from conception and development through deployment, operational maintenance/growth, and retirement.
- A project life cycle covers only a single temporary endeavor (e.g., initial development or a later cloud migration); thus, one product life cycle may contain multiple distinct project life cycles.
Four distinctive challenges of ICT projects:
- Intangibility: Progress in code and architecture is hard to observe without working builds.
- Requirement volatility: User needs and external APIs change frequently mid-project.
- Rapid technological obsolescence: Tools and frameworks evolve quickly.
- High ongoing maintenance share: Maintenance and adaptation account for of total product lifetime cost.
The ICT product life cycle spans conception, development, deployment, operation/maintenance, and retirement, whereas a project life cycle covers one temporary endeavor within that lifespan. ICT projects are uniquely challenging due to intangibility of progress, rapid requirement volatility, fast technology obsolescence, and high post-launch maintenance costs.
Compare Waterfall, Spiral, and Agile (Scrum) methodologies across requirement stability, risk handling, and customer involvement. State when each is preferred in ICT projects.
Side-by-side comparison:
- Waterfall: Linear sequential phases; requires stable requirements upfront; handles risk late (at integration/testing); low customer involvement after initial sign-off. Preferred for fixed-scope, regulatory, or well-understood hardware/infrastructure rollouts.
- Spiral: Iterative risk-driven cycles; explicitly performs risk analysis before each engineering loop; moderate-to-high customer evaluation per cycle. Preferred for large, high-risk, unprecedented ICT systems.
- Agile (Scrum): Short time-boxed iterations (sprints); embraces changing requirements; mitigates risk via frequent working increments; continuous customer collaboration. Preferred for dynamic web, mobile, and SaaS applications.
Waterfall suits stable, fixed-scope projects with sequential sign-offs; Spiral suits large, high-risk systems through explicit per-cycle risk analysis; Agile (Scrum) suits volatile requirements via short iterative sprints and continuous customer collaboration.
An IT company estimates that building a campus library automation system requires engineers for working days at per engineer-day, plus for cloud server licenses.
- Compute the total baseline project budget.
- Due to newly added RFID integration, total engineering effort increases by , and the client moves the deadline earlier to working days. Assuming linear scaling without communication overhead, how many engineers are required to meet the new -day deadline?
Computing the total baseline project budget:
Computing required team size for higher effort in days:
To finish engineer-days in days:
- Total baseline project budget: .
- Minimum required engineers (exact ): engineers to finish within working days.