Question 1. Define an IT project.
Model answer: A temporary undertaking to create or change an IT product, service or organisational capability with defined objectives and constraints.
CBE NEXUS · UNDERGRADUATE TEXTBOOK SERIES
Information Systems
Comprehensive undergraduate notes, project diagrams, applied case studies and university assessment.
Learning outcomes: Explain project governance and life cycles; develop scope, schedules, budgets and risk responses; compare Agile and predictive delivery; elicit and model requirements; plan testing, deployment and transition; and evaluate project performance and ethics.
An IT project is a temporary undertaking that creates or changes an information technology product, service or organisational capability. Examples include implementing an enterprise platform, developing a mobile application, migrating infrastructure, strengthening cybersecurity or integrating business systems. Projects have defined objectives, constraints, stakeholders and an intended end state, while the products they create may continue to operate for many years.
Project management applies knowledge, methods, tools and leadership to plan and coordinate work so that agreed outcomes can be delivered. It is not merely schedule administration. It includes value definition, scope, people, procurement, quality, risk, communication, change and transition to operations. Technical completion does not necessarily mean business success if users cannot adopt the solution or expected benefits are not realised.
IT projects are particularly challenging because requirements may evolve, technology can become obsolete, integrations are uncertain and different stakeholder groups may define success differently. A project manager must create enough structure to control uncertainty without preventing learning. The management approach should fit the scale, criticality, regulatory environment and volatility of the work.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
A project life cycle divides work into stages that provide decision points and management controls. A typical life cycle includes initiation, planning, execution, monitoring and control, and closure. Some organisations use more detailed phases such as discovery, design, build, test, deployment and stabilisation. Each phase should produce evidence that supports a decision to continue, revise, pause or stop.
Predictive delivery defines much of the scope and plan early, then controls execution against an approved baseline. It can suit stable requirements, fixed compliance obligations and work with substantial physical or contractual dependencies. Its weakness is that assumptions made early may prove wrong, and late discovery of user needs can make changes costly.
Adaptive approaches deliver work in short cycles, obtain feedback and revise priorities as evidence emerges. Hybrid approaches combine predictive governance with iterative design and delivery. The choice is not a contest between rigid and flexible management: teams should select practices that make uncertainty visible, preserve accountability and deliver usable outcomes at an appropriate pace.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
Initiation establishes why a project should exist, what problem it addresses and who is accountable. A project proposal should describe the current situation, affected users, strategic alignment, expected outcomes, major constraints, alternatives and initial risks. It should distinguish the problem from a preferred technical solution so that other options can be considered fairly.
A business case compares costs, benefits, risks and alternatives over a defined period. Financial measures may include net present value, internal rate of return and payback period, but non-financial benefits such as safety, service quality, accessibility, compliance and resilience also matter. Assumptions should be explicit and tested through sensitivity analysis rather than presented as certain forecasts.
Governance bodies should decide whether the proposed investment is justified, affordable and feasible. A project should not be approved solely because a technology is fashionable or because a supplier offers a discount. The sponsor remains accountable for the business rationale and should identify benefit owners who will measure whether the intended value is achieved after delivery.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
Scope defines the work and outcomes included in a project, as well as what is excluded. A scope statement should identify deliverables, boundaries, assumptions, constraints, acceptance conditions and dependencies. Ambiguous scope creates conflict: a stakeholder may expect a feature that the delivery team believed was outside the agreement.
A requirements baseline records the approved needs against which design, delivery and acceptance can be assessed. Requirements should be prioritised and traceable to business objectives. Scope should be decomposed into manageable deliverables using a work breakdown structure, which makes responsibilities, estimates and progress easier to manage.
Scope control does not mean rejecting every change. It means evaluating the effect of a proposed change on benefits, cost, time, quality, risk, architecture and operations before approval. A change log should record the request, rationale, impact assessment, decision, owner and resulting baseline update.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
A stakeholder is a person, group or organisation that can affect a project, is affected by it or believes it may be affected. Stakeholders may include sponsors, users, customers, operational teams, suppliers, regulators, auditors, data protection officers and communities. Their interests, authority, knowledge and exposure to change can differ substantially.
Stakeholder analysis identifies influence, impact, expectations, concerns and preferred communication. A power-interest or impact-influence matrix can help determine engagement effort, but it should not become a substitute for listening. Front-line employees may have limited formal authority while possessing essential knowledge about exceptions, workarounds and service realities.
Engagement should be continuous and purposeful. Workshops, interviews, demonstrations, surveys, prototype reviews and user testing provide different kinds of evidence. Record decisions and unresolved concerns. When stakeholders disagree, make trade-offs visible and use agreed governance to decide rather than allowing the loudest voice or most senior individual to define every requirement.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
Project governance defines decision rights, accountability, escalation and oversight. Common roles include project sponsor, steering committee, project manager, product owner, business analyst, technical lead, quality lead, security specialist, change manager and workstream leads. In smaller projects one person may perform several roles, but conflicting responsibilities should still be recognised.
A responsibility assignment matrix clarifies who is responsible for performing work, accountable for outcomes, consulted for expertise and informed of decisions. The project manager coordinates delivery but does not automatically own every business decision. The sponsor secures organisational support and resolves issues beyond the project manager's authority.
Governance should be proportionate. Excessive committees slow decisions, while weak governance allows scope drift, unresolved risks and unclear ownership. Establish meeting purpose, decision thresholds, reporting cadence, escalation deadlines and a record of decisions. Independent assurance may be appropriate for high-value, safety-critical or regulated projects.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
A Work Breakdown Structure decomposes project scope into deliverables and manageable work packages. It should cover the complete agreed scope without unnecessary duplication. Work packages can be estimated, assigned, scheduled and tracked. Decomposition improves visibility, but excessively small tasks create administrative overhead and can hide the larger outcome.
A schedule identifies activities, dependencies, durations, resources and milestones. A network diagram shows logical relationships such as finish-to-start dependencies. The critical path is the longest-duration path through the network and determines the earliest possible completion under the stated assumptions. Activities on the critical path have no available schedule float without affecting the completion date.
Estimates should state assumptions and confidence. Techniques include expert judgement, analogous estimation, parametric estimation, bottom-up estimation and three-point estimation. A three-point estimate uses optimistic, most likely and pessimistic values to represent uncertainty. Teams should update estimates as actual performance and new information become available rather than treating early estimates as guarantees.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
Project cost estimates may include labour, software licences, cloud services, hardware, connectivity, consulting, data migration, training, testing, security, support and contingency. Whole-life cost matters because a low implementation price may create high recurring subscriptions, specialist support costs or expensive exit requirements.
A budget allocates approved funding across work packages and time periods. A cost baseline provides the reference for monitoring expenditure, while management reserves may be held for uncertainty outside the baseline according to organisational policy. Contingency should be based on identified risks and estimation uncertainty, not used as an unexplained allowance.
Cost control compares actual and committed expenditure with planned expenditure and forecast completion cost. Earned Value Management integrates scope, schedule and cost information through planned value, earned value and actual cost. Variances are useful signals, but their interpretation requires reliable progress measurement and awareness of quality, remaining work and forecast uncertainty.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
A project risk is an uncertain event or condition that could affect objectives positively or negatively. Risk management identifies uncertainty, analyses likelihood and impact, selects responses, assigns owners and monitors changes. Risks differ from issues: a risk may occur in the future, whereas an issue is already happening and requires action.
Qualitative analysis ranks risks using defined likelihood and consequence scales. Quantitative analysis may estimate financial exposure, schedule effects or probability distributions where sufficient data exists. A risk register records description, cause, event, effect, rating, owner, response, trigger and status. Avoid vague entries such as 'technology risk' that cannot guide action.
Responses to threats include avoiding, mitigating, transferring or accepting risk; opportunities may be exploited, enhanced, shared or accepted. A response needs an accountable owner, resources and a trigger for action. Review residual risk after treatment and escalate exposure that exceeds the organisation's tolerance.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
An issue is a current problem affecting delivery, such as a failed interface test, unavailable specialist or delayed approval. An issue log records impact, priority, owner, actions, due date and escalation. A decision log records important choices and their rationale so that teams can understand why a particular approach was selected.
Dependencies are relationships in which one task, team, supplier or external event relies on another. They may be internal or external, mandatory or discretionary. Dependency mapping helps reveal critical hand-offs, approval lead times and supplier commitments. A dependency should have an owner and a plan for managing delay or failure.
Assumptions are conditions treated as true for planning but not yet fully verified. Examples include expected data quality, availability of a system interface or timely access to users. Record assumptions with validation dates and consequences if they prove false. Converting important assumptions into early experiments reduces the chance of late project disruption.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
Agile approaches emphasise frequent delivery of useful outcomes, collaboration with customers, adaptation to evidence and sustainable work. Agile is not an absence of planning or documentation. It changes the planning horizon and feedback rhythm, using short cycles to learn and adjust while maintaining clear product goals and quality standards.
Scrum is a framework using a Product Owner, Scrum Master and Developers. Work is organised into Sprints, with events such as Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective. The Product Backlog is an ordered list of work, while the Sprint Backlog describes the selected work and plan for the Sprint.
Scrum does not guarantee success. Poor product ownership, oversized work items, unstable teams, hidden technical debt and absent stakeholder feedback can undermine delivery. Teams should use a clear Definition of Done, maintain tested increments and inspect outcomes. The framework should be understood accurately rather than reduced to daily meetings and task boards.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
Kanban visualises work and manages flow through explicit workflow stages. A board may show items waiting, in progress, under review and completed. Work-in-progress limits reduce excessive multitasking and reveal bottlenecks. Teams can use cycle time, throughput, work-item age and cumulative flow diagrams to understand delivery behaviour.
Lean thinking seeks to maximise customer value while reducing waste. Common waste categories include waiting, unnecessary hand-offs, over-processing, defects, excess inventory, unnecessary movement and underused human capability. In digital work, waste may include unused features, repeated data entry, avoidable approvals and long queues for specialist review.
Continuous flow requires attention to the whole system rather than optimising one department in isolation. Increasing development output may worsen testing queues or operational defects. Improve the constraint that limits end-to-end delivery, make policies visible and review whether changes improve customer outcomes, quality and sustainable workload.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
The Software Development Life Cycle describes organised activities used to create, modify and maintain software. Common activities include feasibility, requirements, analysis, design, coding, testing, deployment, operation and maintenance. Different life-cycle models arrange these activities differently, but quality, security, user needs and operational readiness should be considered throughout.
A waterfall model sequences major phases with formal hand-offs and can suit stable, well-understood requirements. Iterative and incremental models deliver in repeated cycles, allowing feedback and progressive refinement. Spiral development emphasises risk-driven cycles, while DevOps integrates development and operations through automation, collaboration and continuous feedback.
The chosen life cycle should match project uncertainty, technical complexity, compliance obligations and stakeholder availability. Regardless of model, maintain traceability from objectives to requirements, design, code, tests and release evidence. A lifecycle diagram should represent feedback loops and maintenance, not imply that software development ends permanently at deployment.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
Systems development methodologies provide structured ways to investigate problems, design solutions and manage change. Structured methods may use process models, data-flow diagrams, entity-relationship models and documented stages. Object-oriented approaches model interacting objects and classes, while agile methods emphasise iterative delivery and evolving backlogs.
Modelling reduces ambiguity by representing a system from particular viewpoints. A context diagram shows the system boundary and external actors; a data-flow diagram represents processes, data stores and flows; UML use-case diagrams show actor goals; sequence diagrams show interactions over time; and class diagrams represent static structures and relationships.
A model is a purposeful simplification, not the whole reality. State its scope, assumptions and level of detail. Validate it with users and technical specialists, and keep it consistent with requirements and implementation. Multiple diagrams should complement one another rather than use conflicting names or incompatible boundaries.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
Business analysis investigates organisational needs, problems, opportunities and possible changes. Analysts connect strategy to operational work by examining stakeholders, processes, information, rules, capabilities and constraints. The aim is to recommend a solution that creates value, which may involve process redesign or policy change rather than new software alone.
Elicitation techniques include interviews, facilitated workshops, observation, document analysis, surveys, focus groups, interface analysis and prototyping. Each method reveals different evidence. Observation can expose workarounds that people forget to mention; workshops reveal disagreement; and prototypes help users respond to concrete interactions instead of abstract descriptions.
Analysts should distinguish stated requests from underlying needs. A request for an extra spreadsheet field may indicate a missing workflow, unclear policy or poor report. Validate findings with stakeholders, record conflicting needs and define measurable acceptance criteria. Maintain traceability so that each requirement has a source, rationale and validation method.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
Functional requirements specify behaviours or services, such as creating a user account, approving a purchase or calculating a fee. They should be specific, testable and expressed in terms of observable outcomes. User stories may describe a role, need and reason, while use cases describe interactions and alternative paths.
Non-functional requirements describe qualities and constraints such as response time, availability, security, usability, accessibility, interoperability, maintainability, scalability and recoverability. They should include measurable thresholds and operating conditions. 'The system must be fast' is weak; a measurable response-time target under a defined workload is more useful.
Transition requirements are temporary capabilities needed to move from the current state to the future state. Examples include data conversion, staff training, temporary interfaces, parallel operations and cutover support. They are often overlooked even though a technically sound target system can fail if the organisation cannot move safely into it.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
A prototype is an early representation of a system used to explore requirements, interactions, feasibility or design alternatives. Low-fidelity sketches are inexpensive and encourage discussion; high-fidelity prototypes can test navigation, content and realistic interactions. A prototype should be labelled clearly so that stakeholders do not mistake an incomplete concept for a production-ready system.
User-centred design involves understanding users, tasks and contexts, developing alternatives, evaluating designs and iterating. Personas and journey maps can summarise research, but they should be grounded in real evidence rather than stereotypes. Include users with different abilities, devices, languages, connectivity conditions and levels of digital confidence.
Usability testing asks representative participants to complete realistic tasks while researchers observe errors, hesitation and comprehension. Measure task completion, time, error rate and user confidence, but also investigate why difficulties occur. Accessibility evaluation should include keyboard use, screen-reader compatibility, contrast, captions and clear error messages.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
Software architecture describes the major components of a solution, their responsibilities, interfaces, deployment relationships and quality attributes. Architectural decisions affect performance, security, reliability, maintainability, integration and cost. A design should explain why important choices were made and which constraints influenced them.
Architectural styles include layered, client-server, event-driven, service-oriented and microservices architectures. A monolithic application may be simpler to deploy and operate for a small system, while distributed services can support independent scaling and deployment at the cost of network, observability and data-consistency complexity.
Design reviews should consider failure modes, identity, data protection, availability, recovery, logging, scalability and operational support. Architecture decision records capture context, alternatives, decision and consequences. Avoid choosing fashionable patterns without evidence that they solve the problem or that the organisation can operate them responsibly.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
Information systems projects depend on data structures that reflect business meaning. Conceptual models identify entities and relationships; logical models define attributes, keys and constraints; physical models specify implementation details such as indexes and data types. Good modelling helps prevent duplication, update anomalies and ambiguous definitions.
Data ownership, classification, quality and retention should be designed into the solution. Identify authoritative sources, unique identifiers, permitted values, validation rules and lineage. Projects that migrate data must consider duplicates, missing fields, incompatible formats, historical records and legal obligations before finalising the target design.
Database changes should be version-controlled and tested against representative data volumes. Backup and recovery plans should be verified, not merely documented. Performance tuning must preserve correctness and security. A data dictionary and clear entity definitions help developers, analysts, users and auditors interpret information consistently.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
IT projects often connect new applications to existing services, devices, databases and external providers. Integration requirements should define data ownership, message format, frequency, latency, authentication, error handling, reconciliation and service expectations. A successful interface transfers correct meaning, not just bytes between endpoints.
Legacy systems may contain essential business rules and historical information. Modernisation options include retaining and wrapping, rehosting, replatforming, refactoring, replacing or retiring. The choice depends on business criticality, technical condition, vendor support, migration complexity, security exposure and the value of change.
Use contract tests, integration tests and monitoring to detect incompatibility. Plan for timeouts, duplicate messages, delayed events, unavailable partners and partial transactions. A migration strategy should preserve continuity and provide a controlled fallback. Do not decommission a legacy platform until records, dependencies, controls and recovery requirements have been addressed.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
Configuration management identifies and controls the versions and settings of project products, environments and supporting components. It helps teams know which requirements, designs, code, libraries, infrastructure definitions and documents belong to a particular release. Uncontrolled configuration creates uncertainty about what was tested and what is running in production.
Version control records changes to source code and other text-based artefacts. Branching, merging, code review, tags and release notes support collaboration and traceability. Teams should protect repositories, review permissions, scan dependencies and avoid storing secrets in source history. Infrastructure-as-code can make environments more repeatable when changes are reviewed and tested.
A configuration baseline provides an agreed reference point. Change records should identify the item affected, reason, approval, implementation and verification. Environment differences should be minimised and documented. Reproducible builds and automated deployment reduce manual variation, but production changes still require appropriate authorisation and monitoring.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
Quality assurance is the planned set of activities that provides confidence that processes and deliverables meet agreed requirements. Quality control examines actual outputs to identify defects. Quality should be built into requirements, design, coding, data management, supplier work and operations rather than inspected only at the end.
Testing levels include unit, component, integration, system, acceptance, regression, performance, security and usability testing. Test design should cover normal cases, boundaries, invalid inputs, permissions, concurrency, failure recovery and accessibility. Risk-based testing prioritises features whose failure would cause the greatest harm or business disruption.
A test strategy defines scope, roles, environments, data, tools, entry and exit criteria, defect severity, evidence and reporting. Test coverage is not simply the number of test cases executed. Review whether tests represent real business risks and whether critical end-to-end journeys work under realistic conditions.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
DevOps promotes collaboration between software development and IT operations, supported by automation and shared responsibility for service outcomes. Continuous Integration encourages frequent code integration with automated builds and tests. Continuous Delivery keeps software in a releasable state, while Continuous Deployment automatically releases changes when required controls pass.
A delivery pipeline may include source checks, dependency scanning, compilation, unit tests, integration tests, security checks, packaging, deployment to staging, acceptance tests and controlled production release. Pipeline permissions and secrets must be protected. Build artefacts should be traceable to source revisions and approvals.
Deployment strategies include rolling releases, blue-green deployment, canary releases and feature flags. These techniques can reduce risk but require observability and a rollback or mitigation plan. Release success should be judged by service health and user outcomes, not only by whether an automated pipeline turned green.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
Security must be integrated into project governance and the system development life cycle. Threat modelling identifies assets, trust boundaries, likely adversaries, attack paths and controls. Secure requirements may include strong authentication, least privilege, encryption, audit logs, input validation, secure session handling and recovery capability.
Secure development practices include code review, dependency management, static and dynamic analysis, secrets management, secure configuration and penetration testing. Security testing should be proportionate to exposure and impact. A project should define how vulnerabilities are triaged, fixed, retested and communicated before and after release.
Security is a shared responsibility across product owners, developers, infrastructure teams, suppliers and users. A system can be technically secure but operationally unsafe if staff share accounts, ignore alerts or use insecure workarounds. Include training, incident response, patch ownership and security monitoring in the operational handover.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
A change request proposes an alteration to scope, requirements, design, schedule, cost, configuration or release. A disciplined process records the request, assesses impacts, obtains the appropriate decision and updates affected baselines. Emergency changes may use an accelerated route, but retrospective review and evidence are still necessary.
A change control board may review significant changes, while delegated owners approve low-risk decisions within defined limits. The objective is not bureaucracy: it is to ensure that the consequences of change are understood and that incompatible modifications do not undermine quality or control.
Traceability helps identify which requirements, designs, code, tests, documentation, training and operational procedures need revision. After implementation, verify the result and close the request with evidence. Monitor cumulative change because many individually small requests can materially alter the original project or increase technical debt.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
IT procurement may include software, cloud services, devices, consulting, implementation, support and managed services. Procurement planning identifies what should be sourced externally, what capability should remain internal and how supplier performance will be evaluated. A request for proposal should describe outcomes, constraints, service levels, security, integration and evidence requirements.
Supplier evaluation should examine functional fit, technical architecture, financial stability, delivery capability, references, accessibility, support, data handling and exit arrangements. Proofs of concept should use representative scenarios. Contract terms should cover scope, milestones, acceptance, intellectual property, confidentiality, data processing, subcontracting, service credits and dispute resolution.
Vendor management continues after contract signature. Track deliverables, risks, service performance, changes, invoices, security evidence and dependency exposure. Avoid becoming dependent on undocumented customisations or inaccessible data formats. Define transition assistance and test data export before a supplier relationship becomes critical.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
IT project teams combine different disciplines and professional languages. Effective leadership creates shared purpose, clear expectations, psychological safety and accountability. The project manager should remove obstacles, facilitate decisions and support collaboration while respecting the expertise of developers, analysts, testers, operations staff and users.
Communication planning identifies audiences, information needs, channels, frequency, owners and escalation routes. A sponsor may need concise decisions and risk exposure, while developers need detailed interface contracts and users need practical guidance. Status reports should distinguish completed work, forecast, blockers, decisions and emerging risks.
Conflict can arise over priorities, design, workload, ownership or resource allocation. Address it early by clarifying interests and evidence, exploring alternatives and recording decisions. Escalation is appropriate when authority or risk exceeds the team's remit. Blame-oriented cultures hide defects; learning-oriented reviews help teams improve without removing accountability.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
Resource planning identifies the skills, roles, equipment, environments and supplier capacity required to complete work. A resource breakdown structure can group people and non-human resources. Skills matrices reveal gaps in architecture, security, data migration, testing, user research and operational support before those gaps become critical.
Capacity planning should consider availability, competing assignments, leave, specialist bottlenecks and the cost of context switching. Assigning one expert to many simultaneous projects can create queues and unpredictable delays. External consultants may provide scarce expertise but require knowledge transfer and a sustainable handover.
Resource levelling adjusts schedules to address over-allocation, while resource smoothing uses available float where possible. Neither technique removes the need to prioritise work. Monitor actual workload and wellbeing because chronic overwork increases defects, turnover and delivery risk.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
Monitoring compares actual project performance with approved plans and expected outcomes. Useful measures include milestone achievement, completed deliverables, open defects, risk exposure, forecast cost, schedule variance, change volume, user readiness and benefits indicators. A single red-amber-green status can hide important differences, so explain the evidence behind it.
Earned Value Management uses Planned Value (PV), Earned Value (EV) and Actual Cost (AC). Schedule variance is EV minus PV; cost variance is EV minus AC. The Schedule Performance Index is EV divided by PV, and the Cost Performance Index is EV divided by AC. These indicators require consistent rules for measuring earned progress.
A forecast should consider remaining work, risk, resource availability and quality. An apparently favourable cost index may result from incomplete work being reported as finished or from deferred testing. Reports should be honest, timely and decision-oriented. Escalate forecast breaches early enough for leaders to take meaningful action.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
Deployment moves a solution into its intended operating environment. A release plan should define sequence, responsibilities, communication, access, data migration, validation, monitoring, support and rollback conditions. Cutover may involve a maintenance window, final data extraction, conversion, reconciliation, configuration and controlled opening to users.
Operational readiness includes trained support teams, documented procedures, service ownership, monitoring, backup, recovery, capacity, security controls, supplier contacts and known-error records. A service should not be handed over merely because the development team has completed its checklist. Operational teams need the access and knowledge to support it safely.
Stabilisation or hypercare provides focused support after go-live. Track incidents, user feedback, data exceptions and performance against thresholds. Define exit criteria for the stabilisation period and transfer unresolved work into normal service management with owners and priorities. Maintain a rollback decision point for critical failures.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
Closure confirms that deliverables have been accepted, contracts and financial records are reconciled, documentation is handed over, resources are released and outstanding obligations are assigned. A closure report compares outcomes with the original business case, scope, schedule, cost, quality and risk expectations.
Lessons learned should be collected throughout delivery, not only at the end. A useful review examines what happened, why it happened, what evidence supports the conclusion and what should change in future work. Include successes and systemic causes rather than focusing only on individual mistakes.
The project may close while benefits continue to emerge. Assign benefit owners, measurement dates and reporting routes to the operational organisation. Archive decisions, requirements, designs, test evidence and supplier records according to retention rules. A clear handover prevents knowledge loss when temporary project teams disband.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
IT project decisions can affect privacy, access to services, employment, safety, public trust and environmental resources. Ethical analysis should consider who benefits, who bears risk, whether users have meaningful choice and whether the system may disadvantage particular groups. Compliance is a minimum obligation, not a complete ethical assessment.
Projects should identify applicable privacy, cybersecurity, accessibility, records, procurement, intellectual property and sector rules. Requirements should be translated into design controls, testing evidence, contracts and operational responsibilities. Seek qualified legal or regulatory advice where obligations depend on jurisdiction or industry.
Sustainability includes energy and infrastructure use, device lifecycle, repairability, e-waste, cloud resource efficiency and inclusive access. Evaluate whether a project creates unnecessary hardware replacement or excludes users with limited connectivity. Document trade-offs and make responsible design a visible project objective.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
A portfolio is a collection of projects and programmes managed to achieve strategic objectives and balance investment, risk and organisational capacity. Portfolio management considers value, urgency, dependencies, resource constraints, regulatory obligations and strategic fit. It helps prevent every department from treating its own project as the highest priority.
Projects may be compared using weighted criteria, investment thresholds, risk appetite and scenario analysis. Scores should inform judgement rather than create false precision. Portfolio reviews should examine whether assumptions remain valid and whether a project should continue, change direction or stop as new evidence emerges.
Strategic alignment requires traceability from organisational objectives to programmes, projects, deliverables and measurable benefits. Portfolio managers should consider cumulative change load on staff and operations. Too many simultaneous initiatives can reduce adoption and create resource competition even when each project appears reasonable in isolation.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
AI-enabled tools can assist with code suggestions, test generation, documentation, backlog refinement, log analysis and summarisation. They can improve productivity in suitable tasks, but generated output may be incorrect, insecure, biased or incompatible with project context. Teams remain responsible for review, testing, licensing and protection of confidential information.
Product management focuses on sustained user and business outcomes rather than treating delivery as a sequence of temporary projects. Product teams manage discovery, roadmaps, prioritisation, experimentation, adoption and continuous improvement. Project governance remains useful for time-bound investment, but product thinking helps ensure that the resulting service continues to create value.
Responsible adoption requires approved tools, data handling rules, human review, source verification and measurement of actual benefit. Do not place secrets, personal data or restricted source code into unapproved services. Evaluate AI assistance using quality, rework, security and user outcomes rather than counting generated lines or automated suggestions.
In applying this topic, identify the accountable owner, evidence required, decision threshold and consequences of failure. Connect the activity to the project objectives and maintain a record that another team member can understand. Review the approach with affected users and technical specialists, then update plans when new evidence changes the assumptions. A sound project practice is proportionate, repeatable and focused on protecting outcomes rather than producing paperwork for its own sake.
A university plans to replace disconnected admissions, registration, examination and fee applications. The academic calendar creates strict deadlines, historical records are inconsistent and departments disagree about who owns student identity data. A failed launch could disrupt enrolment and examination processing.
The sponsor should establish a business case, governance board and benefit owners. Analysts should map end-to-end student journeys and define a common student identifier, data owners, access roles and acceptance criteria. A phased implementation by faculty or process may reduce cutover risk, provided temporary interfaces and reconciliation are planned.
Pilot migration using representative historical and current records. Reconcile student counts, course registrations, grades and fee balances. Test peak registration, role permissions, result approval, accessibility, backup restoration and incident escalation. Train registry staff and lecturers using realistic scenarios and maintain a staffed support period after launch.
Measure registration completion, record correction rates, time to publish results, unresolved support cases and unauthorised access. Review the first academic cycle against the business case and assign continuing benefits to operational owners.
A financial institution wants to introduce a mobile service for account enquiries, transfers and customer support. Marketing requests many features for launch, security specialists require strong controls and operations teams are concerned about peak demand and fraud.
Define a product vision and prioritised backlog around safe, valuable customer journeys. Use short delivery cycles with a product owner empowered to make priority decisions. Establish architecture and security guardrails early, including identity verification, transaction limits, audit logging, encryption, fraud monitoring and recovery requirements.
Build and test a thin end-to-end increment before adding advanced features. Include automated unit, integration, security and regression tests, independent penetration testing and operational simulations. Use controlled pilot cohorts and monitor latency, failed transactions, fraud signals, accessibility and support demand.
Release progressively with feature flags and a documented rollback route. Review customer feedback and operational evidence after each release. Defer features that cannot meet security or quality requirements rather than compromising critical controls to meet an arbitrary launch date.
A government agency intends to replace paper licensing with an online service. Applicants have different levels of digital access, multiple departments must approve applications and the legal framework requires retention of decision records. The supplier proposes a fixed-price project with a short delivery schedule.
The agency should conduct user research and map the full licensing process, including exceptional cases and offline support. The business case should compare process redesign, shared services and technology options. Procurement should require accessibility, security, interoperability, data portability, audit evidence and transparent service-level commitments.
Deliver a pilot for a limited licence category and test identity verification, payments, document uploads, approval routing, appeals, notifications and records retention. Include security threat modelling, load tests and user testing with people using assistive technology or low-bandwidth connections.
Scale only after measuring completion rates, processing time, error rates, user support demand and decision quality. Maintain assisted service channels and independent oversight so digital convenience does not become a barrier to eligible applicants.
A logistics company relies on an ageing dispatch application that has limited vendor support. It exchanges files overnight with finance and warehouse systems. A complete replacement appears attractive, but the dispatch platform contains undocumented business rules and supports time-critical operations.
Inventory interfaces and business rules before selecting a modernisation route. Assess rehosting, wrapping the legacy system with APIs, incremental replacement and full redevelopment. Prioritise security vulnerabilities and continuity risks. Document critical workflows with experienced dispatch staff and identify external carrier dependencies.
Use a staged migration with contract tests, parallel reconciliation and realistic peak-load simulations. Preserve event history and define duplicate-message handling. Train operational users and provide a controlled fallback to the existing dispatch process until the new service proves reliable.
Track dispatch accuracy, delivery delays, system availability, interface failures and support costs. Retire the old platform only after data retention, supplier dependencies, recovery procedures and business acceptance have been verified.
Answer using clear definitions, calculations where appropriate and justified examples. The model answers provide concise marking guidance for core concepts.
Model answer: A temporary undertaking to create or change an IT product, service or organisational capability with defined objectives and constraints.
Model answer: A project is temporary and creates a change or deliverable; operations are ongoing activities that sustain products and services.
Model answer: Initiation, planning, execution, monitoring and control, and closure.
Model answer: A documented justification comparing expected value, costs, risks and alternatives for an investment.
Model answer: The agreed work and deliverables included in a project, together with boundaries, exclusions and acceptance conditions.
Model answer: A hierarchical decomposition of project scope into manageable deliverables and work packages.
Model answer: The longest-duration sequence of dependent activities that determines the earliest possible project completion under current assumptions.
Model answer: A risk is uncertain and may occur; an issue is a current condition requiring action.
Model answer: Avoid, mitigate, transfer and accept.
Model answer: Identifying stakeholders and assessing their interests, influence, impact, expectations and engagement needs.
Model answer: A matrix clarifying who performs work, who is accountable, who is consulted and who is informed.
Model answer: Predictive delivery plans much of the work upfront; adaptive delivery uses short cycles and feedback to refine priorities and solutions.
Model answer: Product Owner, Scrum Master and Developers.
Model answer: An ordered list of work and changes needed to improve a product.
Model answer: A constraint on the number of items allowed in a workflow stage to reduce multitasking and expose bottlenecks.
Model answer: The ability to link requirements to their sources, objectives, design, implementation, tests and acceptance evidence.
Model answer: Functional requirements describe system behaviours; non-functional requirements describe qualities such as security, usability and performance.
Model answer: Exploring and validating requirements, user interactions, feasibility and design alternatives before or during implementation.
Model answer: Unit, integration, system and acceptance testing.
Model answer: Frequent integration of code changes supported by automated builds and tests to detect problems early.
Model answer: Identifying, recording and controlling versions and settings of project products, environments and components.
Model answer: A measure of the budgeted value of work actually completed by a specified date.
Model answer: CPI = EV/AC = 80,000/100,000 = 0.80. The project earns 0.80 units of budgeted value per unit spent, indicating cost inefficiency.
Model answer: SV = EV − PV = 90,000 − 100,000 = −10,000. The negative value indicates less work has been earned than planned.
Model answer: Business users verify that the delivered solution supports agreed requirements and realistic business scenarios.
Model answer: Rolling deployment, blue-green deployment, canary release and feature-flagged release.
Model answer: It ensures support, monitoring, security, documentation, backup, recovery and ownership are in place before the service enters routine operation.
Model answer: A record of delivery, acceptance, cost, schedule, unresolved obligations, lessons and handover to operations.
Model answer: A portfolio balances investments and initiatives strategically; a programme coordinates related projects to achieve combined benefits.
Model answer: Privacy, accessibility, fairness, transparency, security, inclusion and environmental sustainability.
Use these official organisations for curriculum guidance, examinations and further learning information.