IS5540 Project Management and Quality Assurance
The Complete Exam Bible · Semester A, 2026/27IS5540 Overview
- City University of Hong Kong
- Semester A, 2026/27
- Three credit units
- Postgraduate
- Two-hour final examination
What this course asks you to manage
IS5540 is a practical course in information systems project management. It begins with the distinction between temporary project work and continuing operations, then asks how projects, programs and portfolios support different levels of organisational decision making.
- Assessment structure Continuous assessment contributes 60% and the final examination contributes 40%.
- Pass condition Coursework and examination must each be passed for an overall course pass. Their pass-mark thresholds are unpublished in the captured sources. Attendance contributes through participation, but the captured sources publish no separate attendance pass threshold. Confirm current operational details on the current course Canvas page.
- Project boundary The client project is planned predictively while the student team manages its reports through Scrum and Jira.
What you get in the full IS5540 Exam Bible
- 8 chapters, 37 pages — every examinable topic
- 26 original practice questions, each with a model answer in the Final Exam format
- 8 worked examples, solved the way IS5540 marks
- 8 computed figures, redrawn from the course’s own numbers
- Exam-morning plan for the Final Exam (40%) — what to revise last, where marks are lost
Free on this page: assessment table, chapter map, one worked example, key terms, FAQ. The rest is in the full exam bible.
How IS5540 is assessed
| Component | Weight | Format |
|---|---|---|
| Class and Tutorial Participation | 10% | Active class and online contributions |
| Tutorial Submissions and Scrum Board Participation | 10% | Tutorial submissions 6% and Scrum board participation 4% |
| Two Online Quizzes | 10% | Ten multiple-choice questions in each quiz, covering Sessions 1 to 6 and Sessions 7 to 10 |
| Group Project | 30% | Final Report Part I 20%, Final Report Part II 7%, Presentation 3% |
| Final Exam · hurdle | 40% | Two-hour examination with the permitted-materials wording to be confirmed on Canvas |
| Coursework · hurdle | The coursework hurdle must also be passed; the threshold is not published in the captured materials |
The official catalogue and Semester A outline agree on 60% continuous assessment and a 40% final examination. Coursework and examination must each be passed, but the pass-mark thresholds are unpublished. The captured sources publish no separate attendance pass threshold; attendance contributes through participation, and an unapproved absence receives zero participation credit for that session. The outline calls the examination open-book and permits one handwritten double-sided A4 notes sheet, an abridged hardcopy dictionary and one CityU-approved calculator. Session 1 slides instead call it closed-book while allowing the notes sheet. Confirm the book-status wording and operational pass details on the current course Canvas page. The assignment instructions mention three in-class assignments but list only two quizzes; the assessment table and schedule also publish two quizzes.
Assessment structure
The segment widths reproduce the published weights and total 100%.
What other students are asking about IS5540
- Where can I find lecture notes or study guides for IS5540 at CityU?
- The IS5540 study guide in AskSia Library covers Project Management and Quality Assurance in 8 chapters, with the assessment table, a chapter-by-chapter topic map, key terms and a worked example, free to read on this page.
- Is there a final exam in IS5540, and how much is it worth?
- Yes. In the offering this AskSia Library guide is built from, Final Exam carries 40% of the IS5540 mark; the full split is Class and Tutorial Participation 10%, Tutorial Submissions and Scrum Board Participation 10%, Two Online Quizzes 10%, Group Project 30%, Final Exam 40%.
- What does IS5540 cover on predictive, agile and hybrid?
- In AskSia Library's IS5540 guide, the Predictive, Agile and Hybrid chapter explains scope clarity, incremental release, expected change, hybrid boundaries and deliberate tailoring.
- What does IS5540 cover on governance, charters and change control?
- In AskSia Library's IS5540 guide, the Governance, Charters and Change Control chapter explains authority, project initiation, impact analysis, approval, implementation and re-baselining.
- What does IS5540 cover on scope, work breakdown and schedules?
- In AskSia Library's IS5540 guide, the Scope, Work Breakdown and Schedules chapter explains deliverables, scope boundaries, WBS dictionaries, dependency logic, critical paths and baselines.
What IS5540 covers
Eight chapters move from project value and delivery approach through governance, scope, schedules, cost, quality, risk, people, Jira and verified closure.
Project Foundations, Value and Success
project attributes, operations, constraints, sponsors, success evidence and portfolio focusStart with the boundary
This chapter distinguishes temporary project work from continuing operations, then separates project, program and portfolio decisions.
- Project attributes and operational work
- Projects, programs and portfolios
- Scope, schedule and cost constraints
- Sponsor responsibilities
- Delivery success and value success
- Evidence for accepted results
Predictive, Agile and Hybrid
scope clarity, incremental release, expected change, hybrid boundaries and deliberate tailoringChoose from uncertainty
This chapter compares predictive delivery, adaptive delivery and hybrid boundaries using scope clarity, expected change, release pattern and control cost. It then applies deliberate tailoring to governance and process.
- Predictive planning and constrained change
- Adaptive delivery and small releases
- Hybrid boundaries
- Scope clarity and uncertainty
- Four-stage tailoring
- Client plan versus student delivery
Governance, Charters and Change Control
authority, project initiation, impact analysis, approval, implementation and re-baseliningMake authority visible
This chapter links the project charter to the detailed management plan and then traces a change from request through logging, impact analysis, decision, implementation and re-baselining.
- Governance and strategic alignment
- Charter authority
- Sponsor and manager roles
- Change request logging
- Impact analysis
- Change control decisions
Scope, Work Breakdown and Schedules
deliverables, scope boundaries, WBS dictionaries, dependency logic, critical paths and baselinesDecompose before sequencing
This chapter moves from accepted deliverables to a detailed scope statement, work breakdown structure, WBS dictionary, scheduled activities and an approved schedule baseline.
- Scope inclusions and exclusions
- Product and project deliverables
- Work breakdown structures
- WBS dictionaries
- Activity sequencing
- Duration and resource estimating
Cost, Quality and Risk Controls
performance-index status bands, quality control, quality assurance, risk ownership and response evidenceUse evidence to trigger action
This chapter links quantitative status bands to reporting and corrective decisions, then separates quality control from quality assurance and risk from issue management.
- Cost ownership and budget authority
- Performance-index status bands
- Variance interpretation
- Quality control
- Quality assurance
- Acceptance metrics
Stakeholders, Resources and Communication
stakeholder influence, resource authority, communication routes, decision audiences and retained recordsRoute information to authority
This chapter treats stakeholder analysis, resource planning and communication design as one system.
- Stakeholder interests and influence
- Sponsor and user roles
- Matrix resource authority
- Resource calendars
- Communication requirements
- Decision audiences
Scrum Delivery with Jira
backlog decomposition, sprint planning, workflow truth, review evidence and the student-project boundaryUse the board as evidence
This chapter applies Scrum and Jira to the student team's reports and presentation.
- Client and student project boundary
- Product manager and Scrum master
- Backlog decomposition
- Tasks and subtasks
- Sprint planning
- Workflow states
Monitoring, Closing and Project Evidence
baseline comparison, corrective decisions, acceptance, transition, lessons learned and report proofComplete the control loop
This chapter separates observation from control and task completion from project closure. Actual performance must be compared with an approved baseline or standard before a response is chosen.
- Monitoring actual performance
- Baseline comparison
- Corrective decisions
- Deliverable acceptance
- Transition ownership
- Open issue and risk transfer
The central skill is not recalling a list of tools. It is choosing the right control for a particular uncertainty, naming the person with authority and showing the evidence that lets another person review the decision.
Two delivery systems run through the assessment
The group project deliberately gives students two hats.
Under the consultant hat, the team creates a predictive plan for a pseudo-client's information technology project, covering initiation, governance, scope, schedule, resources, cost, quality, risk, stakeholders and communication. Under the student hat, the team uses Scrum and Jira to manage the production of its reports and presentation.
The source warns that applying agile delivery to the pseudo-client implementation is a mistake. Keeping the two management objects separate is therefore both a conceptual and assessment requirement.
Control means comparison and decision
Baselines, quality standards, risk registers, communication matrices and Jira boards are useful because they expose a comparison.
Actual performance is compared with an approved plan; a deliverable is compared with an acceptance standard; uncertainty is compared with a tolerance; current work is compared with the team's sprint commitment. The comparison does not make the decision.
It produces evidence for the project manager, sponsor, change control body, functional manager or acceptance owner who holds the relevant authority.
Attendance, participation and the pass rule
Coursework and examination must each be passed, while their pass-mark thresholds are unpublished in the captured sources.
Attendance supports participation without being identical to it: the outline describes active contributions, and the assignment guidance says an unapproved absence receives zero participation credit for that session. No separate attendance pass threshold is published in the captured materials.
Use the current course Canvas page for live operational instructions and any threshold clarification.
How to study the course
Use one original project scenario across the chapters.
Classify it, select an approach, draft its governance path, decompose scope into work packages, sequence activities, define quality and risk controls, route stakeholder information and then close the result through acceptance and learning. This makes every term perform a job and shows where two artefacts that look similar answer different questions.
Worked example · free
Repair an informal change request
- 2Record the request and identify its strategic reason.
- 3Assess scope, security, schedule, cost, resource and risk effects.
- 3Route the evidence to the approval body and update baselines only after approval.
Key terms
- Project
- A temporary initiative in a unique context undertaken to create value.
- Program
- Related projects and activities managed together to obtain benefits unavailable from managing them separately.
- Portfolio
- Projects, programs and operations managed as a group to achieve strategic objectives.
- Project Sponsor
- The role that provides direction and funding, removes obstacles and remains accountable for enabling project success.
- Predictive Approach
- A delivery approach that plans most work up front, constrains change and aims at a defined final result.
- Adaptive Approach
- A delivery approach that expects change and develops value through small releases and frequent feedback.
- Tailoring
- Deliberate adaptation of project approach, governance and process to the organisation and project context.
- Scope Baseline
- The approved scope reference used to judge requested work and control change.
- Work Breakdown Structure
- A deliverable-oriented decomposition of project work into manageable work packages.
- Schedule Baseline
- The approved schedule reference used to compare actual progress and assess change.
- Quality Assurance
- Planned activity that tests whether project processes can produce work meeting approved standards.
- Risk Register
- The controlled record of identified risks, causes, impacts, owners, responses and status.
- Change Control Board
- The named body that reviews analysed change requests and approves or rejects them within its authority.
IS5540 FAQ
How is the course assessed?
Continuous assessment contributes sixty per cent and the final examination contributes forty per cent. The continuous block includes participation, tutorial and Scrum board work, two online quizzes and the group project. The numeric weights total one hundred per cent, and the official sources add a separate double-pass condition.
What does the double-pass condition mean?
The catalogue and course outline state that coursework and examination must each be passed for an overall course pass. The pass-mark thresholds are unpublished in the captured materials. Attendance contributes through participation, but the captured sources publish no separate attendance pass threshold. Treat both blocks as protected requirements and confirm operational details on the current course Canvas page.
How long is the final examination and what can I bring?
The official catalogue publishes a two-hour examination. The outline permits one handwritten double-sided A4 notes sheet, an abridged hardcopy dictionary and one CityU-approved calculator, with no other electronic device. Session 1 slides use a conflicting closed-book label, so confirm the live book-status instruction on Canvas.
Why does the group project use both predictive planning and Scrum?
They manage different objects. The team acts as a consultant and produces a predictive plan for the pseudo-client's project. The same students use Scrum and Jira to manage production of their reports and presentation. Applying agile implementation to the client project is explicitly identified as a mark-losing error.
Where are marks won in the group project?
The published Part I allocation rewards visible deliverables and analysis across the charter, governance, scope, schedule, critical path, resources, cost, quality, risk and communication. Strong sections connect the method to an artefact, explain a decision and identify the person who approves or accepts the result.
What counts as useful Jira evidence?
A maintained backlog, truthful workflow state, named owners, dependencies, attachments, sprint decisions and review history show how the team managed work. A final screenshot proves appearance only. The Part II report should explain what changed, why it changed and how the Jira record supports that account.
Do I need critical-path and earned-value calculations?
The course schedule includes a critical-path tutorial and an earned-value exercise, and the captured planning resource uses quantitative performance-index bands. The mine does not contain the tutorial solutions or formula derivations, so use current class materials for the calculation method and use this guide for control logic.
What is the fastest way to revise the course?
Carry one original project across the chapters. Classify it, choose an approach, build the governance and scope chain, identify schedule and control evidence, route stakeholder decisions, manage the student deliverables in Jira and close through acceptance. Retrieval across one coherent case exposes gaps better than rereading definitions.
Questions students ask in each IS5540 chapter
- When does recurring work become a project?
- Recurring work becomes project work when it is organised around a unique change result with a temporary boundary, sponsor, constrained resources and acceptance criteria. A deadline on an otherwise repeated operational process is not sufficient by itself. Chapter 01 · Project Foundations, Value and Success
- Is adaptive delivery always the safest modern choice?
- No. Adaptive delivery fits uncertain scope, expected change and work that can release in small increments. Fixed external rules, a single cutover or expensive partial delivery can make predictive control stronger for all or part of the initiative. Chapter 02 · Predictive, Agile and Hybrid
- Can a sponsor bypass change control?
- A sponsor may hold significant authority, but the request still needs a record and impact analysis so the consequence is visible. The applicable governance design determines who makes the decision and which baselines require authorised updates. Chapter 03 · Governance, Charters and Change Control
- Why should durations stay out of the WBS?
- The WBS defines the work packages needed for deliverables, while the schedule adds activity order, duration, dates and resources. Mixing the two hides the distinction between what must be delivered and how the team currently plans to deliver it. Chapter 04 · Scope, Work Breakdown and Schedules
- Does a critical performance status require immediate re-baselining?
- No. Critical status requires reporting and corrective action under the supplied example. The manager still explains the variance, evaluates options and routes any change to the proper authority. Re-baselining before approval would erase the evidence of poor performance. Chapter 05 · Cost, Quality and Risk Controls
- Why is a stakeholder list not enough?
- A list identifies people but does not show interests, influence, information needs or engagement actions. Management begins when those attributes are connected to a decision route and evidence showing how stakeholder input can affect requirements, risk, priority or acceptance. Chapter 06 · Stakeholders, Resources and Communication
- Why should the board start from deliverable requirements?
- Starting from required report sections and presentation outputs protects coverage. The team can then decompose, assign and review work without losing the connection to the final deliverable. Starting from convenient personal tasks can leave mandatory content unowned. Chapter 07 · Scrum Delivery with Jira
- Why is task completion not the same as project closure?
- Tasks can finish while deliverables remain unaccepted, operating ownership is unclear or risks remain unresolved. Closure requires authorised acceptance, transition, record preservation and a controlled decision about remaining issues and risks rather than a completed percentage alone. Chapter 08 · Monitoring, Closing and Project Evidence
How to study for the exam
Study through artefacts rather than isolated definitions. Begin with a charter and scope statement, then build a WBS, dictionary and schedule logic. Add one change request, one quality failure and one risk so you have to use the approval, assurance and response routes. For the agile side, maintain a small backlog with owners, dependencies, review work and truthful workflow states.
After each pass, close every claim with the evidence that could disprove it and the person who can accept the consequence. Keep the final notes sheet compact: contrasts, triggers, authority and evidence are more useful than copied paragraphs. The final-exam question structure is not published in the captured materials, so revise transferable decision chains and confirm any live format announcement on Canvas.
Your AI Project Management tutor for IS5540
Stuck on a hard IS5540 question? Sia is AskSia’s AI Project Management tutor — ask any IS5540 Project Management and Quality Assurance question and get a clear, step-by-step explanation grounded in how the course is actually taught and assessed. Read this whole study guide free, then take your hardest questions to Sia.