Understand the frameworks used to plan, manage, and deliver projects within organizations. This subtheme explores project governance, delivery models, and decision structures used in complex initiatives.
Flashcards combined with spaced repetition improve active recall. You review at the right time, retain knowledge longer, and track progress card by card.
Card 1
To deliver a temporary, unique outcome aligned to a specific objective
Explanation
Projects exist to achieve a defined goal and then end once the result is delivered.
Common mistake
Confusing projects with ongoing operations that have no formal end point.
Card 2
To provide ongoing value to customers or users over time
Explanation
Products are enduring offerings that evolve to keep delivering value in the market or internally.
Common mistake
Treating a product as finished once a first release is delivered.
Card 3
Project management focuses on delivery within constraints; product management on long-term value
Explanation
Project managers optimize scope, time, and cost, while product managers optimize ongoing value and outcomes.
Common mistake
Assuming project managers own the product roadmap and lifecycle decisions.
Card 4
To coordinate related projects to achieve benefits not available if managed separately
Explanation
Programs align and manage multiple related projects to realize broader strategic benefits.
Common mistake
Thinking a program is simply a very large project rather than a group of related projects.
Card 5
Selecting and balancing initiatives to maximize strategic value within constraints
Explanation
Portfolio management decides which projects and programs to start, continue, or stop to meet strategy.
Common mistake
Confusing portfolio management with tracking status reports for a single program.
Card 6
Portfolios align all initiatives to strategy; programs coordinate related projects for specific benefits
Explanation
Portfolios are chosen for strategic fit and value, while programs are grouped by related outcomes.
Common mistake
Assuming every program automatically forms its own separate portfolio.
Card 7
Initiation, where feasibility and high-level objectives are defined
Explanation
Predictive lifecycles begin with initiation to justify and authorize the project before planning in detail.
Common mistake
Jumping straight into planning or execution without a formal initiation phase.
Card 8
To justify, authorize, and broadly define the project and its objectives
Explanation
Initiation confirms there is a valid business case and grants formal authorization to proceed.
Common mistake
Treating initiation as optional administrative work instead of a formal go/no-go decision.
Card 9
To define how scope, schedule, and resources will achieve the project objectives
Explanation
Planning turns high-level intent into a coherent, realistic plan that guides execution.
Common mistake
Jumping into execution with only vague plans, assuming details can be fixed later.
Card 10
To carry out planned work and create the agreed deliverables
Explanation
Execution consumes the majority of project resources to turn plans into tangible outputs.
Common mistake
Believing execution is independent of ongoing monitoring and change control.
Create your Memia account to unlock this deck and start focused practice sessions with progress tracking.