Trends in ICT Project management
Open in the Padhaiko app14.1 Agile project management
Traditional predictive (Waterfall) models assume requirements can be fully frozen upfront—an assumption that frequently fails in fast-moving software, cloud, and AI initiatives. Agile Project Management embraces iterative, incremental delivery, continuous customer feedback, and adaptive planning.
14.1.1 Agile Manifesto and Scrum Framework
The Agile Manifesto rests on four core values:
- Individuals and interactions over processes and tools.
- Working software over comprehensive documentation.
- Customer collaboration over contract negotiation.
- Responding to change over following a plan.
(While the items on the right have value, Agile teams value the items on the left more.)
Scrum is the most widely adopted Agile framework in ICT:
- Three Roles: Product Owner (maximizes value and manages the Product Backlog), Scrum Master (coaches the team and removes impediments), and Developers (cross-functional engineers building the Increment).
- Three Artifacts: Product Backlog (prioritized feature list), Sprint Backlog (selected items + delivery plan for the current sprint), and Increment (usable deliverable meeting the Definition of Done).
- Five Events: The Sprint (time-boxed container), Sprint Planning, Daily Scrum ( sync), Sprint Review (demo with stakeholders), and Sprint Retrospective (team process improvement).
Other Agile/Lean tools include Kanban (visualizing workflow boards, limiting Work-in-Progress WIP, and optimizing cycle time) and Agile Velocity (average Story Points completed per sprint, used to forecast remaining sprints).
| Aspect | Predictive (Waterfall) | Agile Project Management |
|---|---|---|
| Scope & Requirements | Fixed upfront in detailed SRS; formal change control | Evolving backlog; welcomes changing requirements |
| Delivery Cadence | Single major release at the end of the project | Frequent working increments every Sprint |
| Planning Horizon | Detailed end-to-end plan upfront | Progressive elaboration (release roadmap + sprint plan) |
| Customer Involvement | High at kickoff and UAT; low during coding | Continuous collaboration at every Sprint Review |
| Best Suited For | Hardware rollouts, regulated fixed-spec contracts | Web/mobile apps, SaaS platforms, AI/R&D systems |
14.2 Balanced scorecard and ICT project management
Developed by Robert Kaplan and David Norton, the Balanced Scorecard (BSC) is a strategic management framework that translates an organization's vision into balanced quantitative metrics across four perspectives, preventing managers from focusing solely on short-term financial cost at the expense of quality, customers, or team capability.
| Perspective | Core Strategic Question | Representative ICT Project Metrics |
|---|---|---|
| Financial | How do we create economic value and control costs? | ROI, Net Present Value (NPV), , Total Cost of Ownership (TCO) reduction |
| Customer | How do users and clients perceive our ICT solution? | Customer Satisfaction (CSAT/NPS), SLA uptime (), user adoption rate, ticket resolution time |
| Internal Business Process | Which engineering and operational workflows must we excel at? | Deployment frequency, lead time for changes, Defect Removal Efficiency (), audit compliance |
| Learning and Growth | How do we sustain innovation and team capability? | Cloud/AI upskilling hours, DevOps automation maturity, team retention rate, reusable code assets |
In ICT project management, the Balanced Scorecard serves two vital roles:
- Project Selection & Portfolio Prioritization: Scoring candidate IT initiatives across all four dimensions so strategic long-term infrastructure upgrades are not unfairly rejected in favor of quick cost cuts.
- Post-Implementation Value Evaluation: Measuring whether a delivered system genuinely improved customer outcomes, internal speed, and staff capability—not just whether it stayed within budget.
14.3 Project management maturity models
A Project Management Maturity Model provides a structured benchmark assessing how consistently, predictably, and effectively an organization applies project management processes across all its projects. Moving up maturity levels reduces cost overruns, rework, and schedule slippage.
Three Major Maturity Frameworks
- Kerzner's Project Management Maturity Model (PMMM — 5 Levels):
- Level 1 — Common Language: Basic PM terminology recognized informally.
- Level 2 — Common Processes: Repeatable processes defined and shared across projects.
- Level 3 — Singular Methodology: All corporate processes integrated around one unified PM methodology.
- Level 4 — Benchmarking: Quantitative comparison against industry peers to improve competitiveness.
- Level 5 — Continuous Improvement: Lessons from benchmarking feed back to refine the singular methodology.
- PMI's OPM3 (Organizational Project Management Maturity Model): Integrates Project, Program, and Portfolio management maturity along four improvement stages (SMCI): Standardize Measure Control Continuously Improve.
- CMMI (Capability Maturity Model Integration — 5 Levels): Widely used in software/ICT engineering:
- Level 1 (Initial): Ad-hoc, heroic effort; unpredictable results.
- Level 2 (Managed): Basic project tracking of cost, schedule, and requirements.
- Level 3 (Defined): Organization-wide standardized SDLC and PM processes.
- Level 4 (Quantitatively Managed): Processes controlled via statistical metrics (e.g., control charts, defect density).
- Level 5 (Optimizing): Continuous data-driven innovation and defect prevention.
14.4 Certification process flow
Professional certifications validate a practitioner's mastery of global project management standards (such as PMI's PMP, CAPM, PMI-ACP, PRINCE2, and Scrum Master CSM/PSM). Earning and keeping a formal credential like the PMP (Project Management Professional) or CAPM follows a standardized five-stage certification process flow:
Standard Project Management Certification Process Flow
- Verify Eligibility Requirements: Confirm academic degree, required hours/months of leading and directing projects (for PMP), and mandatory formal PM education hours (e.g., for PMP; for CAPM).
- Submit Application & Eligibility Audit: Document project experience and training in the certifying body's online portal. A percentage of applications undergo a formal audit requiring copies of diplomas, training certificates, and supervisor signatures.
- Pay Fee & Schedule Examination: Once approved, pay the examination fee and book an appointment at an authorized testing center (e.g., Pearson VUE) or via monitored online proctoring.
- Pass the Certification Examination: Complete the standardized scenario-based exam (for PMP, covering three domains: People, Process, and Business Environment).
- Maintain Credential via Continuing Certification Requirements (CCR): Renew the credential periodically (every for PMP) by earning Professional Development Units (PDUs) (e.g., through ongoing education and giving back to the profession) and reaffirming the Code of Ethics.
14.5 Code of ethics
Because ICT project managers control budgets, procurement bids, sensitive user data, and team careers, technical competence alone is insufficient without ethical integrity. The PMI Code of Ethics and Professional Conduct defines both aspirational ideals and mandatory enforceable rules built upon four core values:
| Core Value | Meaning for ICT Project Managers | Concrete Workplace Obligations |
|---|---|---|
| Responsibility | Owning our decisions, actions, and their consequences | Protect confidential data and IP; honor commitments; report unethical or illegal conduct promptly; never accept unapproved scope informally |
| Respect | Showing high regard for ourselves, others, and entrusted resources | Foster inclusive cross-cultural teams; listen openly; negotiate contracts in good faith; never use unlicensed/pirated software |
| Fairness | Making impartial, objective decisions free from bias or favoritism | Disclose and avoid conflicts of interest; run transparent vendor bids; never accept kickbacks, bribes, or gifts from bidders |
| Honesty | Understanding the truth and acting truthfully in communications and conduct | Report true /, defect counts, and schedule delays—never falsify status reports to hide overruns or appease sponsors |
14.6 Future trends
ICT project management continues to evolve rapidly alongside software engineering, cloud computing, and artificial intelligence:
- AI-Assisted & Predictive Project Management: Generative AI automates backlog refinement, test-case generation, and meeting summaries, while machine-learning models analyze historical PMIS logs to predict schedule slippage, cloud cost anomalies, and risk triggers before humans spot them.
- Hybrid & Adaptive Governance: Organizations increasingly combine predictive executive budgeting/compliance milestones with Agile/Lean iterative sprint execution (using frameworks like Disciplined Agile or SAFe).
- DevSecOps & Value Stream Management (VSM): Project success shifts from "completing tasks on a Gantt chart" to measuring end-to-end flow of business value from commit to production via automated CI/CD, Infrastructure as Code (IaC), and continuous security gates.
- Distributed, Remote, and Asynchronous Teams: Global ICT teams collaborate across time zones using digital whiteboards, cloud dev environments, and outcome-based performance metrics rather than physical office presence.
- Green & Sustainable ICT Project Management (ESG): Tracking cloud energy efficiency, carbon footprint of AI/data-center workloads, hardware e-waste recycling, and ethical AI compliance (fairness, explainability, data privacy) as explicit project success criteria.
1
An Agile Scrum team building a digital banking app has a total Product Backlog of . Over the first sprints ( each), the team completed . Calculate: (a) the team's average Agile velocity, (b) the remaining Story Points, and (c) the expected remaining sprints and weeks needed to complete the backlog.
Average Agile Velocity (First Sprints):
Remaining Story Points:
Forecasting Remaining Sprints and Duration:
Since each sprint is long:
- (a) Average Velocity: .
- (b) Remaining Work: .
- (c) Forecasted Completion: ().
2
An enterprise CIO evaluates two competing ICT initiatives using a Balanced Scorecard with weights: Financial (), Customer (), Internal Process (), and Learning & Growth (). Scores (out of ) are:
| BSC Perspective | Weight | Project X (Self-Service Portal) | Project Y (Legacy Server Patch) |
|---|---|---|---|
| Financial (ROI / Cost) | |||
| Customer (UX / Adoption) | |||
| Internal Process (Automation) | |||
| Learning & Growth (Cloud Skills) |
Compute the weighted Balanced Scorecard score for each project and determine which project aligns better with balanced strategic goals.
Computing Weighted BSC Scores:
- Project X (Self-Service Portal):
- Project Y (Legacy Server Patch):
Strategic Interpretation: Although Project Y scores higher on short-term financial cost ( vs. ), Project X outperforms across Customer, Internal Process, and Learning & Growth perspectives, winning overall ().
Project X scores vs. Project Y at . Select Project X (Self-Service Portal) for superior balanced strategic value.
3
Exam-Style Ethics Case: Two weeks before launch, your automated CI suite flags unresolved high-severity security flaws, and your has dropped to . Simultaneously, a bidding cloud vendor offers you an all-expenses-paid "executive conference trip" right before final vendor selection. Your sponsor pressures you to mark the monthly status report "Green" so the steering committee does not delay funding. How should you respond under the PMI Code of Ethics?
Analyzing the Two Ethical Dilemmas Against PMI's Four Core Values:
- Reporting Status Dishonestly (Honesty & Responsibility): Marking the project "Green" violates Honesty (falsifying status/quality truth) and Responsibility (exposing users to security breaches). You must report the true Red/Amber status, disclose the security flaws and , and present corrective options (delay go-live or narrow scope).
- Accepting the Vendor Trip (Fairness & Responsibility): Accepting an all-expenses-paid trip during an active procurement bid creates an unmistakable conflict of interest and undermines Fairness. You must politely decline the gift, disclose the offer per company policy, and evaluate all bids strictly on published source selection criteria.
Decline and disclose the vendor trip (upholding Fairness and Responsibility) and refuse to falsify the status report—communicate the true and security defects transparently with remediation options (upholding Honesty).
Exercises
Practice Exercises — Trends in ICT Project Management
State the four core values of the Agile Manifesto, describe the Scrum roles, artifacts, and events, and explain when a Hybrid model is preferred over pure Waterfall or pure Agile.
Agile Manifesto Core Values:
- Individuals and interactions over processes and tools.
- Working software over comprehensive documentation.
- Customer collaboration over contract negotiation.
- Responding to change over following a plan.
Scrum Elements and Hybrid Preference:
- Roles: Product Owner, Scrum Master, Developers.
- Artifacts: Product Backlog, Sprint Backlog, Increment (with Definition of Done).
- Events: Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective.
- Hybrid Model: Preferred when hardware procurement or regulatory compliance requires predictive milestones/budgets while software modules benefit from iterative Agile sprints.
Agile values people, working software, collaboration, and adaptability. Scrum organizes work via 3 roles, 3 artifacts, and 5 time-boxed events. Hybrid approaches blend predictive budget/milestone governance with iterative Agile software delivery.
A DevOps team has in its release backlog. After completing sprints, it burned down respectively. Compute the average velocity, the remaining Story Points, and the number of remaining sprints needed to finish.
Average Velocity and Completed Points:
Remaining Work and Sprints:
Average velocity , remaining work , and estimated time to finish .
Using the Balanced Scorecard with weights Financial (), Customer (), Internal Process (), and Learning & Growth (), evaluate Project A and Project B . Identify the four BSC perspectives and state which project should be funded.
Balanced Scorecard Computation:
- Project A:
- Project B:
Decision: The four perspectives are Financial, Customer, Internal Business Process, and Learning & Growth. Project A () delivers stronger balanced strategic value.
Project A and Project B across Financial, Customer, Internal Process, and Learning & Growth perspectives; fund Project A.
Compare CMMI and Kerzner's PMMM maturity levels, and outline the five steps of the standard project management certification process flow (such as PMP).
CMMI vs. Kerzner's PMMM:
- CMMI (5 Levels): Initial (ad-hoc) Managed Defined (organization-wide standard) Quantitatively Managed (statistical control) Optimizing (continuous innovation).
- Kerzner's PMMM (5 Levels): Common Language Common Processes Singular Methodology Benchmarking Continuous Improvement.
Certification Process Flow:
- Verify academic, experience, and formal PM training eligibility.
- Submit application (and pass random eligibility audit if selected).
- Pay fee and schedule the proctored exam.
- Pass the examination across required knowledge/process domains.
- Maintain certification via Continuing Certification Requirements (earning PDUs every cycle and upholding ethics).
CMMI progresses from Initial to Optimizing while Kerzner's PMMM progresses from Common Language to Continuous Improvement. The certification flow moves through Eligibility Verification Application/Audit Scheduling Examination Ongoing PDU Maintenance.
List the four core values of the PMI Code of Ethics and Professional Conduct and discuss three major future trends reshaping ICT project management (such as AI analytics, DevSecOps/VSM, and Green ICT).
Four Core Ethical Values:
- Responsibility: Owning decisions, protecting confidential data, honoring commitments.
- Respect: Treating people fairly, respecting cultural diversity and intellectual property.
- Fairness: Impartiality, transparent bidding, avoiding conflicts of interest.
- Honesty: Truthful reporting of costs, schedules, and defects.
Key Future Trends in ICT Project Management:
- AI & Predictive Analytics: AI-assisted backlog drafting, risk prediction, and automated EVM/CI anomaly detection.
- DevSecOps & Value Stream Management: Focusing on automated, secure, continuous flow of customer value rather than isolated task tracking.
- Green / Sustainable ICT (ESG) & Distributed Teams: Optimizing cloud energy/carbon efficiency alongside outcome-based remote collaboration.
The PMI Code of Ethics rests on Responsibility, Respect, Fairness, and Honesty. Future ICT project management is increasingly shaped by AI-assisted predictive analytics, DevSecOps/Value Stream Management, Hybrid governance, distributed teams, and sustainable Green ICT metrics.