PMI CAPM (Certified Associate in Project Management) Examination Content Outline flashcards

A document that provides a detailed description of the project and product scope. It includes the project deliverables, requirements, boundaries, and acceptance criteria.

• Defines what is and is not included in the project.
• Forms part of the scope baseline.
• Often includes or references the Work Breakdown Structure (WBS).

Memory trick: Scope Statement states the work, WBS breaks it down.

The Project Management Plan is a comprehensive document that defines how the project will be executed, monitored, controlled, and closed. It integrates all subsidiary management plans and baselines.

• Comprehensive and integrated document
• Guides project execution, monitoring, control, and closure
• Includes subsidiary plans (e.g., scope, schedule, cost)
• Contains performance measurement baselines

Memory trick: The 'Master Plan' guides all project 'Parts'.

A temporary endeavor undertaken to create a unique product, service, or result.

• Temporary: Has a definite beginning and end.
• Unique: Creates something new or different.
• Driven by objectives: Aims to achieve specific goals.

Memory trick: Temporary Unique Endeavor Gets Results.

An adaptive life cycle, also known as agile, is suitable for projects with high uncertainty and evolving requirements, delivering value incrementally and frequently incorporating feedback.

• High uncertainty and changing requirements
• Frequent delivery of value
• Continuous feedback loops
• Flexible and responsive to change

Memory trick: Uncertainty's waves, adaptive sails.

The project charter is a high-level document that formally authorizes a project, providing its purpose, objectives, and assigning the project manager, but not typically detailed financial justification.

• Authorizes the project.
• High-level purpose and objectives.
• Identifies key stakeholders.
• Often relies on a separate business case for detailed justification.

Memory trick: Charter authorizes, not calculates every financial detail.

In a functional organization, the project manager typically has a limited role, often acting as a project coordinator or expediter, with little formal authority over resources.

• Relies heavily on negotiation and influence.
• Formal communication channels are crucial.
• Functional managers retain ultimate control over resources.

Memory trick: Functional PM Persuades, Prioritizes, and Plans.

Key documents and information required to create the comprehensive Project Management Plan.

• Project Charter: Provides high-level project information.
• Outputs from other processes: E.g., requirements, risk list.
• Enterprise Environmental Factors (EEFs): Organizational culture, market conditions.
• Organizational Process Assets (OPAs): Templates, policies, historical information.

Memory trick: Charter's content fuels the plan's creation.

The Monitoring and Controlling process group involves tracking, reviewing, and regulating the progress and performance of the project; identifying any areas in which changes to the plan are required; and initiating the corresponding changes.

• Tracks, reviews, and regulates project progress
• Identifies variances from the project management plan
• Takes corrective and preventive actions
• Manages changes to the project

Memory trick: I Plan, Execute, Monitor, Close.

The process of communicating and working with stakeholders to meet their needs/expectations, address issues, and foster appropriate stakeholder involvement.

• Requires continuous monitoring and adaptation.
• Stakeholder Register is a key input and is updated throughout.
• Engagement strategies must be flexible.

Memory trick: Register, Plan, Engage, Monitor, Adapt.

The first process group in project management, focused on defining and authorizing a new project or a new phase of an existing project.

• Authorizes the project or phase.
• Defines initial scope and objectives.
• Identifies key stakeholders.

Memory trick: I Plan Every Morning Control and Close

In matrix organizations, project managers often struggle to secure dedicated resources from functional departments.

• Functional managers retain authority over personnel.
• Resources may be assigned part-time to projects.
• Project managers need strong negotiation and influencing skills.

Memory trick: Matrix means many managers, making resource access a constant battle.

A Stakeholder Register is a project document containing the list of identified project stakeholders, along with their key information, assessment, and classification, used to manage their engagement effectively.

• Identifies all project stakeholders
• Records key information (e.g., roles, interests, influence)
• Classifies stakeholders (e.g., internal/external, power/interest)
• Helps in planning stakeholder engagement strategies

Memory trick: Register their names, 'Stake' their claim.

The Communications Management Plan is a component of the Project Management Plan that describes how, when, and by whom project information will be administered and distributed.

• Defines communication requirements of stakeholders
• Specifies information to be communicated (format, content, level of detail)
• Identifies who is responsible for communicating information
• Determines communication frequency and methods

Memory trick: Plan your 'Comms', avoid the 'storms'.

A key advantage of adaptive (Agile) project life cycles is the ability to incorporate change and feedback continuously, leading to higher stakeholder satisfaction.

• Iterative and incremental development.
• High stakeholder involvement.
• Suitable for projects with evolving requirements.

Memory trick: Adaptive life cycles: Agile feedback, Happy stakeholders.

In a project-oriented (or projectized) organization, the project manager has full authority over project resources, and team members are dedicated to working on the project.

• Project manager has full authority
• Resources are dedicated to the project
• Team members report directly to the PM
• Resources are released upon project completion

Memory trick: Project-focused, like a 'dedicated' team.

A project environment characterized by evolving requirements, unclear final product features, and the need for frequent adaptation and feedback.

• Often seen in innovative or research-oriented projects.
• Requires adaptive or iterative life cycles.
• Emphasizes learning and continuous adjustment.

Memory trick: Uncertainty means 'U'nknowns 'U'pon 'U'nknowns.

The Project Charter's primary purpose is to formally authorize a project, grant the project manager authority, and establish a shared understanding of the project's purpose and high-level objectives among stakeholders.

• Formal project authorization.
• Grants PM authority.
• Establishes common understanding of purpose.
• Defines high-level objectives.

Memory trick: The Charter is the 'Chief Handshake' for project start and PM power.

The Predictive (Waterfall) life cycle is best suited for projects where requirements are stable, the final product is well-understood, and the cost of change is high.

• Common in construction, manufacturing, and highly regulated industries.
• Emphasizes upfront planning and sequential phases.
• Minimizes changes during execution due to high cost of rework.

Memory trick: Construction is 'C'arefully 'C'hronological, like a 'C'ardinal rule.

A characteristic of projects where future events, outcomes, or impacts are not known or predictable, requiring proactive risk management and adaptability.

• Projects operate in environments of varying certainty.
• Unforeseen events are common.
• Requires risk identification and response planning.

Memory trick: Projects are Unique, Temporary, and full of Uncertainty.

The project manager is primarily responsible for identifying, analyzing, and engaging all project stakeholders, addressing their concerns, and fostering their participation to ensure project success.

• Central point of communication.
• Manages expectations.
• Develops engagement strategies.
• Resolves conflicts and concerns.

Memory trick: PM leads the team, manages stakeholders, delivers the dream.

The approved version of a scope statement, work breakdown structure (WBS), and its associated WBS dictionary, which is used as a basis for comparison.

• Part of the Project Management Plan.
• Defines what is and is not included in the project.
• Crucial for preventing and managing scope creep.

Memory trick: The Scope Baseline is the 'B'oundary fence for your 'B'uilding project.

A project environment characterized by high uncertainty, rapidly evolving requirements, and the need for frequent feedback and adjustments.

• High degree of uncertainty.
• Requirements are dynamic and change frequently.
• Emphasizes iterative and incremental delivery.
• Relies on continuous stakeholder feedback.

Memory trick: Adaptive projects dance with change, not fight it.

Project success measured by the realization of benefits, including financial, strategic, social, and environmental, rather than solely by adherence to the triple constraint.

• Broader view beyond scope, time, cost.
• Focuses on benefits and long-term impact.
• Includes stakeholder satisfaction and social responsibility.

Memory trick: Value delivers beyond the Triple Constraint.

The Project Management Plan is a comprehensive document that integrates all subsidiary plans, while other project information is stored in separate project documents.

• PMP is comprehensive and integrated.
• Subsidiary plans are part of the PMP.
• Project documents are separate from the PMP.

Memory trick: PMP is the master plan, subsidiary plans fit inside, documents are separate files.

Project success is measured not only by adherence to scope, schedule, and budget, but also by the achievement of business value, stakeholder satisfaction, and the quality of the final product or service.

• Triple constraint (scope, schedule, cost)
• Quality of deliverables
• Achievement of business objectives/value
• Stakeholder satisfaction (especially end-users)

Memory trick: Beyond the 'Triple Constraint', look for 'Value' and 'Smiles'.

Agile principle emphasizing continuous and close collaboration with customers throughout the project to ensure the delivered product meets their evolving needs and provides maximum value.

• Prioritizes ongoing dialogue over rigid contracts.
• Ensures product relevance and value.
• Facilitates timely feedback and adaptation.

Memory trick: Collaborate with customers, hear their needs, hit the target.

Agile techniques (e.g., WSJF, Kano Model) used to objectively order Product Backlog items based on their perceived value, cost of delay, and effort, especially when facing diverse items and conflicting stakeholder interests.

• Aids in making informed decisions about 'what to build next'.
• Considers multiple dimensions beyond just 'importance'.
• Promotes transparency and alignment on value.

Memory trick: To prioritize right, weigh value and effort with all your might, making sure the best items take flight.

The process by which an Agile team develops a shared understanding and consistent relative sizing for story points, often by comparing new items to previously completed 'reference stories'.

• Essential for consistent and reliable velocity.
• Involves discussing complexity, effort, and risk.
• Often uses techniques like Planning Poker.

Memory trick: For estimation to be sound, a shared understanding must be found, with sizes relative, not profound.

The process of collaboratively re-evaluating and potentially modifying the Sprint Goal or Sprint Backlog when unforeseen circumstances threaten the Sprint's objective.

• Involves the Development Team, Product Owner, and Scrum Master.
• Prioritizes transparency and adaptation.
• Aims to maintain value delivery despite challenges.

Memory trick: When a roadblock hits, the Agile team unites, re-plans, and then ignites.

A consensus-based, gamified technique used in Agile to estimate the effort or relative size of user stories or Product Backlog Items, typically using a modified Fibonacci sequence.

• Promotes discussion and shared understanding.
• Mitigates anchoring bias.
• Facilitates quick consensus or highlights disagreements.
• Uses relative sizing (e.g., Story Points).

Memory trick: Estimate with poker for details, T-shirts for quick, affinity for groups.

Agile emphasizes continuous collaboration with stakeholders throughout the project lifecycle to ensure requirements are clear, expectations are aligned, and feedback is incorporated early.

• Ongoing dialogue with stakeholders.
• Clarifies requirements and expectations.
• Incorporates feedback early.
• Reduces surprises at reviews.

Memory trick: To avoid surprises at the show, keep the stakeholders in the continuous flow.

Agile teams focus their collective efforts on a limited number of items at a time to maximize throughput and achieve the Sprint Goal. This means avoiding context switching and prioritizing completion.

• Concentrate on limited items.
• Avoid context switching.
• Prioritize completion over starting new work.
• Essential for achieving Sprint Goal.

Memory trick: To hit the Sprint Goal, the team must focus its sight, not scatter its efforts left and right.

A high-level visual summary that outlines the product's vision, strategic direction, and expected evolution over time, typically showing key milestones or features without rigid timelines.

• Communicates 'why' and 'what' of the product.
• Aligns stakeholders and provides strategic context.
• Fluid and evolves with new information.
• Focuses on outcomes, not just outputs.

Memory trick: Communicate clearly: vision on the roadmap, details in stories, progress on charts.

A visual technique for organizing user stories into a coherent narrative that describes the user's journey through a product, helping to discover and prioritize features for a product backlog.

• Visual representation of user journey.
• Collaborative discovery tool.
• Organizes user stories.
• Helps prioritize features and build shared understanding.

Memory trick: To map out the user's journey and discover new features, a Story Map clears all the product's fuzzy blurs.

A Scrum event where the Scrum Team inspects itself and creates a plan for improvements to be enacted during the next Sprint.

• Occurs at the end of each Sprint.
• Focuses on process, tools, interactions, and definitions of 'Done'.
• Aims for continuous improvement.

Memory trick: Each Scrum event has a distinct role, from planning to improving the whole.

A core Kanban principle to restrict the number of items being worked on at any given time, forcing a focus on completing existing work before starting new tasks.

• Reduces context switching and improves focus.
• Increases throughput and reduces lead time.
• Reveals bottlenecks in the workflow.

Memory trick: Too much WIP? Just stop and limit, then flow will start to transmit.

The ongoing process of adding detail, estimates, and order to Product Backlog items, which is critical for accurate forecasting and realistic Sprint commitments.

• Collaborative activity involving the Product Owner and Development Team.
• Ensures items are 'ready' for Sprint Planning.
• Improves clarity, reduces ambiguity, and enhances estimation accuracy.

Memory trick: To commit with precision and gain, refine your backlog to avoid the pain.

The ongoing process during Sprint Planning where the Development Team breaks down selected Product Backlog Items into smaller, more manageable tasks and creates a detailed plan for how to deliver the Sprint Goal.

• Occurs during Sprint Planning.
• Involves the Development Team.
• Breaks PBIs into actionable tasks.
• Essential for accurate estimation and clear work.

Memory trick: Product Backlog is the wish list, Sprint Backlog is the plan, Increment is the gift.

Focus on improving the overall system and value stream, rather than optimizing individual components, to ensure continuous flow and value delivery.

• Improve the entire value stream.
• Avoid local optimization.
• Identify and resolve bottlenecks.
• Ensures continuous flow.

Memory trick: To keep the value flowing, optimize the whole river, not just one struggling boat.

WSJF is a prioritization model used to sequence work to provide the maximum economic benefit. It's calculated as Cost of Delay divided by duration (or size).

• Maximizes economic benefit.
• Cost of Delay / Job Duration.
• Prioritizes high value, low effort.
• Used in SAFe, Lean-Agile.

Memory trick: To maximize value, weigh the delay and pick the shortest path to economic gain.

A prioritization technique used to categorize requirements into four categories: Must have, Should have, Could have, and Won't have, to help teams understand the relative importance of each item.

• Must Have: Critical for the solution to be viable.
• Should Have: Important, but not essential.
• Could Have: Desirable, but less critical or impactful.
• Won't Have: Not included in the current iteration/release.

Memory trick: Prioritize with clear categories, weigh options, aim for impact.

The Daily Scrum is a 15-minute time-boxed event for the Development Team to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. It is not a problem-solving session.

• 15-minute time-box.
• Development Team only.
• Inspects progress, adapts plan.
• Problem-solving occurs separately.

Memory trick: Keep the daily huddle short and sweet; park the deep dives for a separate meet.

An ongoing, collaborative activity in Scrum where the Product Owner and Development Team add detail, estimates, and order to Product Backlog Items, preparing them for future Sprints.

• Not a formal Scrum event, but an ongoing activity.
• Involves Product Owner and Development Team.
• Aims to make PBIs 'ready' for Sprint Planning.
• Typically consumes no more than 10% of the Development Team's capacity.

Memory trick: Plan the Sprint, daily sync, refine the backlog, review, then retrospect.

Agile methodologies prioritize adapting to changing requirements and environments over strictly adhering to an initial, fixed plan. Change is seen as an opportunity for competitive advantage.

• Embrace change.
• Adapt quickly to new requirements.
• Flexibility over rigid planning.
• Change as an opportunity.

Memory trick: When the winds of change blow, an Agile ship adjusts its flow.

The Product Owner is accountable for managing the Product Backlog, including its content, availability, and ordering, to maximize the value of the product resulting from the work of the Development Team.

• Accountable for Product Backlog.
• Maximizes product value.
• Manages content, availability, ordering.
• Works with Dev Team on refinement.

Memory trick: The Product Owner's crown jewel is a backlog ordered to maximize value, not a chaotic jumble.

When a significant impediment threatens the Sprint Goal, the Development Team collaborates with the Product Owner and Scrum Master to assess, decide on the best course of action, and potentially renegotiate the Sprint Backlog or cancel the Sprint.

• Significant impediment threatens Sprint Goal.
• Collaborative decision (Dev Team, PO, SM).
• May lead to Sprint Backlog renegotiation.
• Product Owner can cancel Sprint if Goal obsolete.

Memory trick: When a critical bug crashes the Sprint party, the team, PO, and SM must huddle and chart a new start-y.

A core Lean principle focused on identifying and removing any activity or resource that does not add value to the customer, thereby improving efficiency and effectiveness.

• Identifies and removes non-value-adding activities.
• Common types of waste (Muda): Overproduction, Waiting, Transport, Over-processing, Inventory, Motion, Defects (TIMWOOD).
• Improves flow and reduces lead time.

Memory trick: Lean means smooth flow: build quality, reduce waste, deliver fast, respect people, optimize the whole, defer commitment.

An ongoing activity where the Product Owner and Development Team collaborate to add detail, estimates, and order to Product Backlog Items, making them 'Ready' for future Sprints.

• Ongoing activity, not an event.
• Collaboration between PO and Dev Team.
• Adds detail, estimates, and order.
• Ensures PBIs are 'Ready' for Sprint Planning.

Memory trick: To make the Sprint plan clear and sound, the Backlog must be refined all around.

A comprehensive, hybrid Agile framework that provides guidance for organizations to choose and evolve their Way of Working (WoW) based on their context, encompassing various Agile methods and practices for enterprise-level scaling.

• Goal-driven and context-sensitive.
• Provides a toolkit for process improvement.
• Supports multiple lifecycles (Scrum, Kanban, Lean, Continuous Delivery).
• Focuses on enterprise-level agility, not just development.

Memory trick: Scaling Agile: SAFe for big, DA for custom, LeSS for simple.

The clear and concise description of a feature, function, requirement, enhancement, or fix for a product, including its value and acceptance criteria.

• Expressed as user stories, epics, or themes.
• Includes a clear 'why' (value) and 'what' (acceptance criteria).
• Refined collaboratively by the Product Owner and Development Team.

Memory trick: For a clear backlog item, the 'what' and 'why' must shine, with criteria defined.

A Sprint may be canceled if the Sprint Goal becomes obsolete, usually due to a major change in direction or circumstances. Only the Product Owner has the authority to cancel a Sprint.

• Sprint Goal becomes obsolete.
• Only the Product Owner can cancel.
• Rare event, last resort.
• Collaborative decision with Development Team.

Memory trick: When the Sprint's target shifts, the Owner and Team must confer, or the Sprint's purpose may blur.

An Agile principle advocating for building projects around motivated individuals, providing them with the necessary environment and support, and trusting them to perform their work effectively.

• Fosters self-organization and autonomy.
• Requires trust from leadership.
• Promotes a supportive and enabling environment.

Memory trick: To grow a self-organizing team, plant trust, provide support, and let them bloom.

SAFe is a framework for implementing Lean-Agile practices at enterprise scale. It helps large organizations align multiple Agile teams, manage dependencies, and deliver value consistently.

• For large organizations.
• Aligns multiple Agile teams.
• Manages dependencies.
• Supports consistent value delivery at scale.

Memory trick: When many teams need to align and combine, SAFe creates a harmonious design.

A core Agile practice where the Development Team commits to achieving a specific Sprint Goal, and changes that threaten this goal are carefully managed, often deferred to future Sprints.

• Ensures focus and predictability within a Sprint.
• Prevents scope creep from undermining 'Done' increments.
• Requires negotiation and collaboration with the Product Owner regarding changes.

Memory trick: Agile values guide us, but the Sprint Goal is our compass; protect it to deliver true value.

A formal Scrum event where the Scrum Team presents the 'Done' increment to stakeholders, discusses progress toward the Product Goal, and gathers feedback for future planning.

• Occurs at the end of each Sprint.
• Promotes transparency and inspection of the product.
• Facilitates collaboration and adaptation with stakeholders.

Memory trick: To keep stakeholders aligned and bright, show them the progress with all your might.

A refined understanding of 'Decide late', emphasizing that decisions should be deferred to gather maximum information but made before the cost of not deciding becomes prohibitive, enabling fast delivery.

• Avoids premature commitment in volatile environments.
• Requires identifying the 'last responsible moment' for each decision.
• Aims to maximize flexibility while ensuring timely progress.

Memory trick: Decisions late, but not too late, hit the responsible moment, seal your fate.

The Product Owner is solely accountable for maximizing the value of the product and for managing the Product Backlog, including its content, clarity, and ordering.

• Responsible for Product Backlog management.
• Ensures Product Backlog items are clear and understood.
• Prioritizes items to optimize value.

Memory trick: Each Scrum role has its domain, for backlog clarity, the Product Owner reigns.

A conflict resolution technique where parties work together to find a solution that fully satisfies all their concerns, leading to a 'win-win' outcome.

• Requires open dialogue and mutual respect.
• Focuses on underlying issues, not just positions.
• Best for complex problems and building long-term relationships.

Memory trick: Avoid, force, smooth, compromise, or truly collaborate to solve.

Defined steps within the communication management plan that outline how to raise unresolved issues, risks, or decisions to higher levels of authority when initial attempts fail or are unavailable.

• Ensures timely resolution of critical issues.
• Prevents project delays due to lack of decision.
• A component of the communication management plan.

Memory trick: Urgent issue, missing leader? Check the plan for the right path up.

A component of the project management plan that describes how project communications will be planned, structured, implemented, and monitored for effectiveness.

• Defines information needs of stakeholders.
• Includes methods, formats, content, and frequency.
• Specifies escalation procedures and reporting structures.

Memory trick: Plan communications to keep everyone in the loop, especially when issues escalate.