Review questions
Integrated summary: Project Management Foundations and Value Delivery
This subject connects four questions: What kind of work is this? What value is intended? Who owns the decision? How should delivery and learning be organized responsibly? Apply them to the fictional training network planning a booking system for three branches over four months, or to an organization you know without using personal or confidential information. The figures and situations are teaching examples, not actual organizational data or promises of results.
A project is a temporary assignment producing a distinctive output; operations sustain a recurring service. Building, accepting and handing over booking software differs from processing bookings every morning. The temporary element is the team’s assignment, not the system’s lifetime. Familiar technology does not prevent an output being distinctive in its context. Specify what will be accepted, who accepts it, the endpoint and the subsequent operations owner. An important supplier email is not automatically a separate project. Authorized early termination can also end a project, so an endpoint alone does not establish success.
Program management becomes clear when related projects require coordination for a shared benefit. In the example, the system project and reception-redesign project have separate commissions; the program aligns their delivery with operational readiness. Testing and training activities inside one system project are not sufficient evidence of a program. A portfolio instead prioritizes investments against strategy and capacity, such as a new branch, booking improvements and equipment renewal. Distinguish coordinating selected work from deciding which work deserves resources in the first place.
The output is the accepted system; the outcome is a changed way of using the service; the benefit is a valuable improvement supported by evidence. Moving from an 18-minute processing baseline to a 12-minute target means a targeted six-minute reduction: six divided by eighteen, multiplied by one hundred, or about 33.3%. Calculating it does not establish realization. An observed 11-minute average after launch, with bookings halved, does not isolate system effects from workload. Define transaction type, timing start and end, measurement period, benefit ownership and assumptions about use and data integration. Do not confuse system acceptance with proof of its effects.
The business case explains why work merits implementation through benefits, costs, risks and alternatives. Reconsider it when information changes or at a decision gate; continuation, revision, deferral or termination can follow. Where the fictional evidence points to conflicting reception roles, revising the procedure and testing it in one suitable branch may address the need more directly than adding technical features. That choice depends on a safe trial and authorized decision-making; it is neither a complete financial appraisal nor spending permission.
Governance establishes authority, accountability, delegation limits and escalation; management coordinates work within them. Objective assurance under the project’s arrangements examines information and controls without replacing the manager. The sponsor considers continuing justification and decisions within their remit; the manager coordinates delivery, dependencies and reporting; the team contributes delivery expertise; users clarify needs and experience; operations takes over service under agreed transition conditions. One person holding several roles does not erase their different responsibilities. Under the case rule reserving budget increases to the sponsor, the manager analyzes and refers a proposal rather than starting it or rejecting it permanently without referral.
A life cycle describes stages and their relationships. A delivery approach addresses planning, learning and making outputs available. Stable requirements and expensive changes can favor predictive planning; uncertainty that can be tested with users supports adaptation. Predictive delivery does not prohibit change, and adaptation does not remove planning. Agile work is neither just a short meeting nor identical to every adaptive technique; the taught application uses regular learning to inform decisions. Hybrid delivery may combine planned installation with iterative booking development, provided interfaces and acceptance are coordinated rather than merely given different labels.
Revising a screen prototype three times without releasing a new function is iterative learning. Making course booking available, then adding usable workshop booking, is incremental delivery. These can coexist but are not the same. In the hybrid example, a complete booking test needs a device, connection, a release that passed functional tests and a prepared staff member. Three out of four conditions do not establish readiness when connectivity is unavailable. Record repair, retest and transition ownership. Unaffected work may continue without being described as integrated service acceptance.
Professional reporting distinguishes executed tests, passed tests and unknown results. Eighteen passed cases out of twenty is numerically 90%, but two critical duplicate-prevention tests remain unperformed, making “90% ready” misleading on its own. Do not call them confirmed defects either. State consequences, the next check, its owner and decision authority. Disclose a potential supplier relationship to the authorized role, follow the procedure and document it; do not assume one universal law or automatic exclusion. An unsupported number remains a claim needing verification, whether supplied by a vendor or an AI tool.
Sustainability, privacy and fitness for use belong in decisions rather than slogans. In the fictional comparison, device A costs 4,000 plus five annual maintenance payments of 300: 5,500 monetary units. Device B costs 3,500 plus five annual payments of 600: 6,500. The 1,000 difference covers purchase and maintenance only, without discounting or residual value. It establishes neither full cost nor environmental superiority and cannot replace specification checks or consideration of missing costs. Use fictional test data; deleting a name does not necessarily prevent identification. Before detailed planning, write a brief covering output, assignment endpoint, benefit and evidence, decision owner and proposed approach. Clarify these elements before adding schedule detail.
Review questions
Test your understanding with these questions. Marking and saved results are available with a free account.
Create a free account to mark your answers and save your progress.