CAPM
Certified Associate in Project Management.
Getting Started: Navigating the CAPM Exam
Free knowledge base
Everything from the course in one searchable place: 343 entries. Use it to review before a practice test or look up a word you forgot.
343 results · showing first 300, refine your search
Certified Associate in Project Management.
Getting Started: Navigating the CAPM Exam
Project Management Institute, governing body.
Getting Started: Navigating the CAPM Exam
Project Management Body of Knowledge standard.
Getting Started: Navigating the CAPM Exam
Requirements for exam eligibility.
Getting Started: Navigating the CAPM Exam
Hours of formal PM education.
Getting Started: Navigating the CAPM Exam
High school diploma or equivalent.
Getting Started: Navigating the CAPM Exam
Formal recognition of qualification.
Getting Started: Navigating the CAPM Exam
CAPM: Competence Assured, Projects Managed! Think of a 'CAP' that covers all your project management basics.
Getting Started: Navigating the CAPM Exam
The CAPM exam is based on the Project Management Body of Knowledge (PMBOK® Guide) and the PMI's Examination Content Outline. Remember, 23 contact hours of project management education are mandatory.
Getting Started: Navigating the CAPM Exam
Confusing the CAPM with the PMP; CAPM is entry-level, PMP is for experienced PMs.
Getting Started: Navigating the CAPM Exam
Underestimating the 23 contact hours requirement; it's mandatory for eligibility.
Getting Started: Navigating the CAPM Exam
Believing the CAPM is only for IT; it's applicable across all industries.
Getting Started: Navigating the CAPM Exam
A question format with several options, only one of which is correct.
Getting Started: Navigating the CAPM Exam
Unscored questions used by PMI for future exam development.
Getting Started: Navigating the CAPM Exam
A statistical method used to determine the passing score.
Getting Started: Navigating the CAPM Exam
The global network of testing centers where the CAPM exam is administered.
Getting Started: Navigating the CAPM Exam
The process of planning and controlling how much time is spent on specific activities.
Getting Started: Navigating the CAPM Exam
Questions that describe a scenario and ask for the best project management action.
Getting Started: Navigating the CAPM Exam
To remember the exam structure: '1-5-0 questions, 3 hours to go, 1-3-5 scored, 1-5 for show!' (150 total, 3 hours, 135 scored, 15 unscored).
Getting Started: Navigating the CAPM Exam
Memorize that the CAPM exam has 150 questions total, with 135 scored and 15 unscored, and a total duration of 3 hours (180 minutes). These numbers are fixed and frequently tested.
Getting Started: Navigating the CAPM Exam
Spending too much time on a single difficult question, leading to not finishing the exam.
Getting Started: Navigating the CAPM Exam
Not practicing with timed mock exams, which can lead to poor time management on exam day.
Getting Started: Navigating the CAPM Exam
Trying to memorize answers instead of understanding the underlying project management principles.
Getting Started: Navigating the CAPM Exam
Temporary endeavor creating a unique product, service, or result.
Foundations of Project Management
Ongoing, repetitive work to sustain the business, not temporary.
Foundations of Project Management
Applying knowledge, skills, tools, techniques to meet project requirements.
Foundations of Project Management
Series of phases a project passes through from start to finish.
Foundations of Project Management
Sequential, plan-driven approach; requirements defined upfront.
Foundations of Project Management
Iterative, incremental approach; requirements evolve with feedback.
Foundations of Project Management
Combines elements of both predictive and adaptive approaches.
Foundations of Project Management
Repeating a process to refine or improve an outcome.
Foundations of Project Management
P.L.A.N.C. - Project Life cycles Are Not Constant! (Helps remember there are different types)
Foundations of Project Management
The exam frequently distinguishes between projects and operations. Remember: projects are temporary and unique, while operations are ongoing and repetitive. Also, know the characteristics and best use cases for Predictive (Waterfall) vs. Adaptive (Agile) life cycles.
Foundations of Project Management
Confusing projects with ongoing operational work. Projects have a defined end; operations do not.
Foundations of Project Management
Applying a Predictive (Waterfall) life cycle to a project with highly uncertain or evolving requirements, leading to costly rework.
Foundations of Project Management
Believing that all projects must follow the exact same set of phases or life cycle type, ignoring project context.
Foundations of Project Management
Internal and external factors influencing a project.
Foundations of Project Management
Conditions not controlled by the project team that influence it.
Foundations of Project Management
Internal plans, processes, and knowledge bases of an organization.
Foundations of Project Management
Structure where employees are grouped by specialty.
Foundations of Project Management
Blends functional and projectized structures.
Foundations of Project Management
Structure where teams are dedicated to projects.
Foundations of Project Management
Shared values and beliefs within an organization.
Foundations of Project Management
To remember the spectrum of PM authority: 'F-W-B-S-P' (Functional, Weak, Balanced, Strong, Projectized) – think 'Few Will Be Strong Project Managers' to recall the increasing authority.
Foundations of Project Management
Memorize the key characteristics and project manager authority levels for functional, weak matrix, balanced matrix, strong matrix, and projectized organizational structures. The exam often presents scenarios and asks you to identify the structure or its implications.
Foundations of Project Management
Confusing EEFs (external/uncontrollable) with OPAs (internal/controllable/updatable).
Foundations of Project Management
Underestimating the impact of organizational culture on project success.
Foundations of Project Management
Assuming the project manager always has full authority, regardless of the organizational structure.
Foundations of Project Management
Leads the project team to achieve project objectives.
Foundations of Project Management
Authorizes the project, provides resources, and champions it.
Foundations of Project Management
Anyone affected by or who can affect the project.
Foundations of Project Management
Formally authorizes a project and gives PM authority.
Foundations of Project Management
Comprehensive document defining project execution and control.
Foundations of Project Management
Framework guiding project management to meet organizational goals.
Foundations of Project Management
Detailed description of what the project must deliver.
Foundations of Project Management
To remember the main documents: C.P.R. - Charter, Plan, Requirements. These three are vital for project life!
Foundations of Project Management
The CAPM exam frequently tests the distinct responsibilities of the Project Manager versus the Project Sponsor. Memorize that the Sponsor authorizes and funds, while the PM manages the daily project work.
Foundations of Project Management
Confusing the Project Manager's responsibilities with the Project Sponsor's.
Foundations of Project Management
Underestimating the importance of a comprehensive Project Management Plan.
Foundations of Project Management
Failing to identify and engage all relevant stakeholders early in the project.
Foundations of Project Management
Comprehensive document guiding project execution, monitoring, control, and closure.
Foundations of Project Management
Approved version of a work product, changed only through formal control.
Foundations of Project Management
Approved version of the project scope statement, WBS, and WBS dictionary.
Foundations of Project Management
Approved version of the project schedule.
Foundations of Project Management
Approved version of the time-phased project budget.
Foundations of Project Management
Integrated scope, schedule, and cost baselines for measuring performance.
Foundations of Project Management
Component of the PMP detailing how a specific area will be managed.
Foundations of Project Management
Formal process for managing changes to project documents and baselines.
Foundations of Project Management
PMP = Plan My Project. Think of it as your personal project roadmap, guiding every step and keeping you on track.
Foundations of Project Management
The CAPM exam frequently tests your understanding of the Project Management Plan's purpose as the central, approved document. Keywords to spot include 'how the project will be managed' or 'integrates all subsidiary plans.' Remember that baselines are fixed points for measurement unless formally changed.
Foundations of Project Management
Treating the Project Management Plan as a static document that's created once and never updated.
Foundations of Project Management
Making changes to project scope, schedule, or cost without going through a formal change control process.
Foundations of Project Management
Defining project success solely by 'on time, on budget' without considering value delivery or stakeholder satisfaction.
Foundations of Project Management
Hierarchical decomposition of project scope.
Predictive Project Management Deep Dive
Uncontrolled expansion of project scope.
Predictive Project Management Deep Dive
Identifies longest sequence of activities.
Predictive Project Management Deep Dive
Process to review and approve changes.
Predictive Project Management Deep Dive
Links requirements to their origin.
Predictive Project Management Deep Dive
Imagine a 'S.I.S.' (Scope, Integration, Schedule) who is always 'P.L.A.N.N.I.N.G.' (Planning, Leading, Adjusting, Navigating, Negotiating, Integrating, Guiding) to keep projects on track!
Predictive Project Management Deep Dive
The CAPM exam frequently tests the order of processes within each knowledge area. Memorize the sequence for Integration, Scope, and Schedule Management. Pay close attention to inputs, tools & techniques, and outputs for 'Develop Project Management Plan' and 'Perform Integrated Change Control'.
Predictive Project Management Deep Dive
Failing to involve stakeholders in scope definition, leading to missed requirements.
Predictive Project Management Deep Dive
Allowing changes to the project without going through a formal change control process.
Predictive Project Management Deep Dive
Not creating a detailed Work Breakdown Structure (WBS), resulting in an unclear understanding of project deliverables.
Predictive Project Management Deep Dive
Method to measure project performance.
Predictive Project Management Deep Dive
Process of auditing quality requirements.
Predictive Project Management Deep Dive
Monitoring to assess performance and recommend changes.
Predictive Project Management Deep Dive
Availability of resources during a project.
Predictive Project Management Deep Dive
Document for team values and operating guidelines.
Predictive Project Management Deep Dive
Costs incurred to prevent, appraise, and fail.
Predictive Project Management Deep Dive
Comparing actual to planned performance.
Predictive Project Management Deep Dive
For Cost, Quality, and Resources, remember 'P-M-C': Plan, Manage, Control. It's the typical flow for these areas!
Predictive Project Management Deep Dive
The CAPM exam often tests your understanding of the differences between 'Plan,' 'Manage,' and 'Control' processes within each knowledge area. For example, 'Plan Quality Management' defines standards, 'Manage Quality' implements them, and 'Control Quality' verifies them. Look for keywords like 'define,' 'implement,' or 'verify' in the questions.
Predictive Project Management Deep Dive
Confusing Quality Assurance (process improvement) with Quality Control (product verification).
Predictive Project Management Deep Dive
Underestimating the importance of soft skills in Resource Management, especially team development.
Predictive Project Management Deep Dive
Failing to update the cost baseline after approved changes, leading to inaccurate budget tracking.
Predictive Project Management Deep Dive
Document outlining how project information will be managed.
Predictive Project Management Deep Dive
Two-way exchange with immediate feedback, e.g., meetings.
Predictive Project Management Deep Dive
Information sent to recipients, e.g., emails, reports.
Predictive Project Management Deep Dive
Information accessed by recipients, e.g., intranets.
Predictive Project Management Deep Dive
Uncertain event affecting project objectives (positive or negative).
Predictive Project Management Deep Dive
Document detailing identified risks, analysis, and responses.
Predictive Project Management Deep Dive
Strategy to reduce probability or impact of a threat.
Predictive Project Management Deep Dive
Strategy to ensure a positive opportunity occurs.
Predictive Project Management Deep Dive
To remember the threat responses: 'A M T A' - Avoid, Mitigate, Transfer, Accept. Just think 'A Mighty Threat Averted!'
Predictive Project Management Deep Dive
The CAPM exam often tests your understanding of communication methods and risk response strategies. Pay close attention to the differences between interactive, push, and pull communication, and memorize the primary strategies for both threats (avoid, mitigate, transfer) and opportunities (exploit, enhance, share). Keywords like 'reduce impact' point to mitigation, while 'eliminate' points to avoidance.
Predictive Project Management Deep Dive
Failing to tailor communication to the audience, leading to misunderstandings or information overload.
Predictive Project Management Deep Dive
Ignoring positive risks (opportunities) or only focusing on negative risks (threats).
Predictive Project Management Deep Dive
Not formally documenting risks or communication plans, leading to confusion later.
Predictive Project Management Deep Dive
Acquiring goods/services from outside the project.
Predictive Project Management Deep Dive
Seller agrees to a set price for a defined scope.
Predictive Project Management Deep Dive
Buyer pays seller's actual costs plus a fee.
Predictive Project Management Deep Dive
Hybrid contract, pays for time and materials.
Predictive Project Management Deep Dive
Strategies to involve stakeholders in project decisions.
Predictive Project Management Deep Dive
Document requesting bids from potential sellers.
Predictive Project Management Deep Dive
For Stakeholder Engagement: I.A.P.M.M. - Identify, Analyze, Plan, Manage, Monitor. It's like a five-step dance with your project's people!
Predictive Project Management Deep Dive
The CAPM exam emphasizes understanding the different contract types and their associated risk allocation. Memorize that Fixed-Price is high seller risk, Cost-Reimbursable is high buyer risk, and Time & Material is a hybrid.
Predictive Project Management Deep Dive
Assuming all stakeholders have the same level of interest or influence; always tailor engagement.
Predictive Project Management Deep Dive
Not involving procurement specialists early enough in the planning phase for external acquisitions.
Predictive Project Management Deep Dive
Failing to document contract terms clearly, leading to disputes later in the project lifecycle.
Predictive Project Management Deep Dive
Document outlining 4 values and 12 principles for Agile development.
Agile Project Management Essentials
A popular Agile framework for developing and sustaining complex products.
Agile Project Management Essentials
Agile method visualizing workflow, limiting WIP, maximizing efficiency.
Agile Project Management Essentials
A short, time-boxed iteration in Scrum, typically 1-4 weeks.
Agile Project Management Essentials
An ordered list of all known work for a product, maintained by the Product Owner.
Agile Project Management Essentials
Principles focused on maximizing customer value while minimizing waste.
Agile Project Management Essentials
Agile methodology emphasizing technical practices for quality.
Agile Project Management Essentials
Agile's 4 Values: I Work Continuously Responding. (Individuals, Working software, Customer collaboration, Responding to change).
Agile Project Management Essentials
The exam often tests your understanding of the Agile Manifesto's four values. Memorize them and understand what each 'over' statement implies. Keywords like 'iterative', 'incremental', 'adaptable', and 'customer collaboration' are strong indicators of Agile concepts.
Agile Project Management Essentials
Confusing Agile with a specific methodology like Scrum; Agile is the mindset, Scrum is a framework.
Agile Project Management Essentials
Believing Agile means 'no planning'; it means adaptive planning, not a lack of it.
Agile Project Management Essentials
Thinking Agile is only for software development; its principles apply to many project types.
Agile Project Management Essentials
Maximizes product value, manages Product Backlog.
Agile Project Management Essentials
Facilitates Scrum, removes impediments, coaches team.
Agile Project Management Essentials
Cross-functional professionals delivering product increments.
Agile Project Management Essentials
Selected items for current Sprint, plus delivery plan.
Agile Project Management Essentials
Relative measure of effort, complexity, and risk.
Agile Project Management Essentials
Consensus-based estimation technique using Story Points.
Agile Project Management Essentials
Sum of 'Done' work from current and previous Sprints.
Agile Project Management Essentials
POSD (Product Owner, Scrum Master, Development Team) - Remember the core Scrum roles by thinking of a 'POSD' system for project success!
Agile Project Management Essentials
The CAPM exam often tests your understanding of the distinct responsibilities of the Product Owner and Scrum Master. Remember: Product Owner focuses on 'what' (product value), Scrum Master on 'how' (process and team enablement).
Agile Project Management Essentials
Confusing the Product Owner's role with the Scrum Master's; they have distinct responsibilities.
Agile Project Management Essentials
Trying to estimate agile work in absolute hours instead of relative Story Points, which often leads to inaccurate predictions.
Agile Project Management Essentials
Failing to continuously refine the Product Backlog, leading to stale or irrelevant requirements for the team.
Agile Project Management Essentials
Visualizes remaining work against time in a sprint or release.
Agile Project Management Essentials
Measure of work a team completes in a sprint, used for forecasting.
Agile Project Management Essentials
Meeting for team to inspect process and plan improvements.
Agile Project Management Essentials
Usable product portion ready for release at iteration end.
Agile Project Management Essentials
Time from when work starts on an item to when it's done.
Agile Project Management Essentials
Visual display making project status and metrics visible.
Agile Project Management Essentials
To remember the key Scrum events: 'P-D-R-R' - Planning, Daily, Review, Retrospective. Like a 'PDRR' (pioneer) blazing a trail!
Agile Project Management Essentials
The CAPM exam often tests your understanding of agile metrics and ceremonies. Memorize the purpose of burn-down/up charts, velocity, and the key events in a Scrum sprint (planning, daily scrum, review, retrospective). Look for keywords like 'inspect and adapt' and 'continuous improvement'.
Agile Project Management Essentials
Treating sprint commitments as rigid, unchangeable contracts rather than flexible forecasts.
Agile Project Management Essentials
Focusing solely on individual tasks instead of collaborating to achieve the sprint goal.
Agile Project Management Essentials
Skipping retrospectives or not implementing agreed-upon improvements, hindering continuous learning.
Agile Project Management Essentials
Releasing product increments frequently and reliably.
Agile Project Management Essentials
A short, time-boxed investigation to gain knowledge.
Agile Project Management Essentials
Visualizes remaining risks over time (less common in agile).
Agile Project Management Essentials
Analyzes steps to deliver value, identifying waste.
Agile Project Management Essentials
Mechanisms for gathering input to improve.
Agile Project Management Essentials
R.I.S.K. F.A.C.T.S.: Risks Identified, Solutions Known, Feedback Applied, Continuous Testing, Stakeholder Satisfaction. Remember this for agile risk and value!
Agile Project Management Essentials
The CAPM exam emphasizes that agile risk management is iterative and continuous, not a one-time event. Look for keywords like 'adaptive planning,' 'continuous feedback,' and 'early and frequent delivery' when answering questions about agile value.
Agile Project Management Essentials
Treating agile risk management as a separate, upfront activity rather than an integrated, continuous process.
Agile Project Management Essentials
Delaying value delivery until all features are complete, missing opportunities for early feedback.
Agile Project Management Essentials
Ignoring stakeholder feedback during sprint reviews, leading to less valuable product increments.
Agile Project Management Essentials
Tasks and techniques to identify business needs and solutions.
Business Analysis for Project Success
Liaison between stakeholders, eliciting and managing requirements.
Business Analysis for Project Success
Document outlining BA activities, deliverables, and approach.
Business Analysis for Project Success
Conditions or capabilities needed by stakeholders or solution.
Business Analysis for Project Success
Adapting BA approach to fit specific project needs.
Business Analysis for Project Success
Specific way of satisfying one or more needs in a context.
Business Analysis for Project Success
Remember 'PLAN' for Business Analysis Planning: P-Purpose, L-Liaison, A-Activities, N-Needs.
Business Analysis for Project Success
The CAPM exam emphasizes understanding the 'why' behind business analysis – its purpose, objectives, and the value it brings to projects. Look for questions about the benefits of early BA involvement and the components of a BA plan.
Business Analysis for Project Success
Assuming all projects require the same level of business analysis effort.
Business Analysis for Project Success
Skipping BA planning and jumping directly into requirements gathering.
Business Analysis for Project Success
Not involving key stakeholders early enough in the business analysis process.
Business Analysis for Project Success
Process of discovering and gathering information from stakeholders.
Business Analysis for Project Success
One-on-one conversation to gather detailed requirements.
Business Analysis for Project Success
Facilitated session with multiple stakeholders for collaborative requirement definition.
Business Analysis for Project Success
Technique for generating a large number of ideas quickly.
Business Analysis for Project Success
Reviewing existing documents to understand current processes.
Business Analysis for Project Success
Watching users perform tasks to understand their workflow.
Business Analysis for Project Success
Prioritization method: Must, Should, Could, Won't have.
Business Analysis for Project Success
To Elicit Great Requirements, Remember: I Fought With Big Old Dogs! (Interviews, Focus groups, Workshops, Brainstorming, Observation, Document analysis)
Business Analysis for Project Success
The CAPM exam expects you to recognize various elicitation techniques and understand their appropriate application. Keywords like 'interviews,' 'workshops,' 'brainstorming,' and 'document analysis' are often associated with elicitation. Remember that elicitation is an iterative process.
Business Analysis for Project Success
Assuming you know what stakeholders want without asking or verifying.
Business Analysis for Project Success
Using only one elicitation technique for all requirements, missing diverse perspectives.
Business Analysis for Project Success
Failing to prioritize requirements, leading to scope creep and missed deadlines.
Business Analysis for Project Success
High-level document outlining business needs.
Business Analysis for Project Success
Details what a system must do.
Business Analysis for Project Success
Describe how a system should perform.
Business Analysis for Project Success
Requirement from an end-user's perspective.
Business Analysis for Project Success
Confirming requirements meet business needs.
Business Analysis for Project Success
Checking requirements for quality and consistency.
Business Analysis for Project Success
Formal approval and freezing of requirements.
Business Analysis for Project Success
Links requirements to other project artifacts.
Business Analysis for Project Success
V&V: Verify it's right (internal check), Validate it's right for them (external check).
Business Analysis for Project Success
The CAPM exam distinguishes between verification ('Are we building the product right?') and validation ('Are we building the right product?'). Memorize this distinction and the purpose of baselining requirements for scope control.
Business Analysis for Project Success
Confusing requirements verification with requirements validation; they address different aspects of quality.
Business Analysis for Project Success
Skipping formal baselining, leading to uncontrolled scope creep and project delays.
Business Analysis for Project Success
Failing to involve key stakeholders in the requirements validation process, resulting in a product that doesn't meet their true needs.
Business Analysis for Project Success
Describes how requirements will be defined, analyzed, documented, and managed.
Business Analysis for Project Success
A formal group responsible for reviewing, evaluating, and approving/rejecting changes.
Business Analysis for Project Success
Tracking a requirement from its origin through its implementation and testing.
Business Analysis for Project Success
A document linking requirements to other project artifacts.
Business Analysis for Project Success
To manage requirements, remember 'PLAN-DO-CHECK-ACT' for changes: Plan the RMP, Do the work, Check for changes, Act on approvals.
Business Analysis for Project Success
The CAPM exam frequently tests your understanding of the Requirements Management Plan's purpose and contents, as well as the formal change control process. Look for keywords like 'baseline,' 'change request,' and 'CCB' when answering questions about managing changes.
Business Analysis for Project Success
Allowing informal changes to requirements without proper documentation or approval, leading to scope creep.
Business Analysis for Project Success
Failing to involve all relevant stakeholders in requirements review and approval, causing dissatisfaction later.
Business Analysis for Project Success
Not establishing a clear traceability between requirements and test cases, making it hard to verify completion.
Business Analysis for Project Success
Identifying quality requirements and standards for the project and its deliverables.
Ensuring Quality & Continuous Improvement
Auditing quality requirements and results to ensure appropriate standards are used.
Ensuring Quality & Continuous Improvement
Monitoring and recording results of quality activities to assess performance.
Ensuring Quality & Continuous Improvement
A document outlining how quality requirements will be met and managed.
Ensuring Quality & Continuous Improvement
A structured review to determine if project activities comply with policies.
Ensuring Quality & Continuous Improvement
Examining a work product to determine if it conforms to standards.
Ensuring Quality & Continuous Improvement
Deliverables confirmed to meet quality requirements through control activities.
Ensuring Quality & Continuous Improvement
P-A-C: Plan, Assure, Control. P is for 'Plan' the map. A is for 'Assure' the journey. C is for 'Control' the destination.
Ensuring Quality & Continuous Improvement
Memorize the distinct focus of each process: Planning (what to do), Assurance (how to do it right, process focus), Control (did we do it right, deliverable focus). The exam often tests your ability to differentiate these three.
Ensuring Quality & Continuous Improvement
Confusing quality assurance (process focus) with quality control (deliverable focus).
Ensuring Quality & Continuous Improvement
Failing to integrate quality activities throughout the entire project lifecycle, treating it as a final step.
Ensuring Quality & Continuous Improvement
Not documenting quality requirements and metrics clearly, leading to subjective quality assessments.
Ensuring Quality & Continuous Improvement
Ongoing effort to enhance products, services, or processes.
Ensuring Quality & Continuous Improvement
Maximizes customer value by minimizing waste in processes.
Ensuring Quality & Continuous Improvement
Any activity that consumes resources but adds no value.
Ensuring Quality & Continuous Improvement
Data-driven approach to minimize defects and variation.
Ensuring Quality & Continuous Improvement
Define, Measure, Analyze, Improve, Control; Six Sigma roadmap.
Ensuring Quality & Continuous Improvement
Inconsistency or deviation in a process or its output.
Ensuring Quality & Continuous Improvement
Lean is for 'Less Effort, Awesome Now!' Six Sigma is for 'Superb Insights, Xact Goals, Great Results, Measurable Accuracy!'
Ensuring Quality & Continuous Improvement
The CAPM exam expects you to distinguish between Lean's focus on waste elimination and Six Sigma's focus on variation reduction. Keywords like 'efficiency,' 'speed,' and 'waste' point to Lean, while 'defects,' 'variance,' and 'data-driven' suggest Six Sigma.
Ensuring Quality & Continuous Improvement
Confusing Lean's primary goal (waste reduction) with Six Sigma's (variation reduction).
Ensuring Quality & Continuous Improvement
Applying Six Sigma to problems that are primarily about inefficiency rather than defects.
Ensuring Quality & Continuous Improvement
Failing to involve process owners and team members in continuous improvement initiatives.
Ensuring Quality & Continuous Improvement
Systematic examination of a process to identify inefficiencies.
Ensuring Quality & Continuous Improvement
Improving process efficiency, effectiveness, and adaptability.
Ensuring Quality & Continuous Improvement
Visual diagram showing steps and decisions in a process.
Ensuring Quality & Continuous Improvement
Lean tool to visualize flow and identify waste in a process.
Ensuring Quality & Continuous Improvement
Technique to identify underlying reasons for problems.
Ensuring Quality & Continuous Improvement
Iterative questioning technique to explore cause-and-effect relationships.
Ensuring Quality & Continuous Improvement
Visual tool for categorizing potential causes of a problem.
Ensuring Quality & Continuous Improvement
Radical redesign of processes for dramatic improvement.
Ensuring Quality & Continuous Improvement
To OPTIMIZE, you must ANALYZE. Think of a detective (analyze) finding clues to make things better (optimize).
Ensuring Quality & Continuous Improvement
The exam often tests your ability to differentiate between various process analysis tools and their appropriate application. Remember that 'optimization' focuses on making processes better, while 'analysis' is about understanding them first.
Ensuring Quality & Continuous Improvement
Skipping the 'as-is' mapping: Trying to optimize a process without fully understanding its current state often leads to ineffective or even detrimental changes.
Ensuring Quality & Continuous Improvement
Ignoring stakeholder input: Not involving the people who actually perform the process can lead to proposed changes that are impractical or met with resistance.
Ensuring Quality & Continuous Improvement
Focusing only on symptoms: Failing to conduct root cause analysis means you might fix a problem temporarily, but the underlying issue will likely resurface.
Ensuring Quality & Continuous Improvement
Executing the quality management plan during project work.
Ensuring Quality & Continuous Improvement
Selecting a subset for inspection to infer quality of the whole.
Ensuring Quality & Continuous Improvement
A tool to ensure all necessary steps or requirements are met.
Ensuring Quality & Continuous Improvement
Deliverables confirmed to meet quality requirements through QC.
Ensuring Quality & Continuous Improvement
To remember the flow of quality implementation: 'Plan, Do, Check, Act' (PDCA). Plan your quality, Do the work, Check for quality, Act to improve.
Ensuring Quality & Continuous Improvement
The CAPM exam often tests your understanding of where specific quality activities occur. Remember that 'implementing quality' and 'performing quality control' are primarily executed during the project's execution phase, while 'quality planning' is done earlier. Keywords like 'inspecting,' 'testing,' and 'correcting defects' point to quality control.
Ensuring Quality & Continuous Improvement
Confusing quality control (inspecting deliverables) with quality assurance (auditing processes).
Ensuring Quality & Continuous Improvement
Viewing quality as a one-time check instead of an ongoing process.
Ensuring Quality & Continuous Improvement
Failing to conduct root cause analysis, leading to recurring problems.
Ensuring Quality & Continuous Improvement
Uncertain event affecting objectives, positive or negative.
Managing Risks and Ensuring Compliance
Process of finding and documenting potential project risks.
Managing Risks and Ensuring Compliance
Prioritizing risks based on probability and impact.
Managing Risks and Ensuring Compliance
Numerically analyzing risk effect on project objectives.
Managing Risks and Ensuring Compliance
Computer-based simulation modeling probability of outcomes.
Managing Risks and Ensuring Compliance
Investigating underlying reasons for potential problems.
Managing Risks and Ensuring Compliance
Examining Strengths, Weaknesses, Opportunities, Threats.
Managing Risks and Ensuring Compliance
To remember the key steps of risk analysis, think: 'I Qualify Quantitatively, then Register.' I for Identify, Qualify for Qualitative, Quantitatively for Quantitative, Register for Risk Register.
Managing Risks and Ensuring Compliance
The CAPM exam often tests your ability to distinguish between qualitative and quantitative risk analysis. Remember that qualitative is about prioritizing (high/medium/low), while quantitative is about numerical impact (e.g., cost, schedule). Look for keywords like 'prioritize,' 'rank,' 'subjective' for qualitative, and 'numerical,' 'probabilistic,' 'financial impact' for quantitative.
Managing Risks and Ensuring Compliance
Confusing qualitative and quantitative analysis: Qualitative prioritizes, quantitative measures numerically.
Managing Risks and Ensuring Compliance
Treating risk identification as a one-time activity: It's an iterative process throughout the project.
Managing Risks and Ensuring Compliance
Not documenting identified risks: All risks, even low-priority ones, should be in the risk register.
Managing Risks and Ensuring Compliance
Document outlining planned responses to risks.
Managing Risks and Ensuring Compliance
Actions if a primary risk response fails.
Managing Risks and Ensuring Compliance
Alternative actions if contingency fails.
Managing Risks and Ensuring Compliance
Event indicating a risk is about to occur.
Managing Risks and Ensuring Compliance
Review of risk management process effectiveness.
Managing Risks and Ensuring Compliance
Time/money for known-unknown risks.
Managing Risks and Ensuring Compliance
Time/money for unknown-unknown risks.
Managing Risks and Ensuring Compliance
Risk remaining after response implementation.
Managing Risks and Ensuring Compliance
For threats, remember 'AMTA': Avoid, Mitigate, Transfer, Accept. For opportunities, remember 'EESA': Exploit, Enhance, Share, Accept.
Managing Risks and Ensuring Compliance
The exam frequently tests your knowledge of the four primary strategies for threats (Avoid, Mitigate, Transfer, Accept) and opportunities (Exploit, Enhance, Share, Accept). Remember that 'Accept' is a valid strategy for both, meaning you acknowledge the risk but take no proactive action.
Managing Risks and Ensuring Compliance
Failing to assign clear ownership for risk responses, leading to inaction.
Managing Risks and Ensuring Compliance
Not monitoring risks after implementing a response, assuming the problem is solved.
Managing Risks and Ensuring Compliance
Ignoring opportunities, focusing only on negative risks and missing potential benefits.
Managing Risks and Ensuring Compliance
Adherence to laws, regulations, standards, policies, and contracts.
Managing Risks and Ensuring Compliance
Structured rules and guidelines by authorities for specific industries.
Managing Risks and Ensuring Compliance
General Data Protection Regulation, EU law on data privacy and security.
Managing Risks and Ensuring Compliance
California Consumer Privacy Act, US law on consumer data rights.
Managing Risks and Ensuring Compliance
Systematic, independent examination to determine compliance.
Managing Risks and Ensuring Compliance
Failure to adhere to required laws, regulations, or standards.
Managing Risks and Ensuring Compliance
To remember the importance of compliance, think 'C.A.R.E.': Consequences Are Really Expensive!
Managing Risks and Ensuring Compliance
The CAPM exam often tests your understanding of the *types* of compliance (e.g., environmental, safety, data privacy) and the *consequences* of non-compliance. Memorize that compliance is a continuous process, not a one-time event.
Managing Risks and Ensuring Compliance
Assuming compliance is only a legal team's responsibility; project managers own it.
Managing Risks and Ensuring Compliance
Waiting until project completion to check for compliance, leading to costly rework.
Managing Risks and Ensuring Compliance
Ignoring minor compliance issues, which can escalate into major problems.
Managing Risks and Ensuring Compliance
Moral principles guiding behavior.
Managing Risks and Ensuring Compliance
Formal statement of ethical principles.
Managing Risks and Ensuring Compliance
Adherence to moral and ethical principles.
Managing Risks and Ensuring Compliance
Situation requiring a difficult choice.
Managing Risks and Ensuring Compliance
Openness and accountability in actions.
Managing Risks and Ensuring Compliance
Personal interest influencing professional duty.
Managing Risks and Ensuring Compliance
Reporting unethical practices.
Managing Risks and Ensuring Compliance
Remember 'RRHF': Responsible, Respectful, Honest, Fair. These are the four pillars of ethical project management, like the four legs of a sturdy table.
Managing Risks and Ensuring Compliance
The CAPM exam often tests your ability to apply ethical principles to specific scenarios. Look for keywords like 'integrity,' 'fairness,' 'honesty,' 'responsibility,' and 'conflict of interest.' Remember that the best ethical choice often prioritizes the project's and stakeholders' long-term well-being over short-term gains or personal benefits.
Managing Risks and Ensuring Compliance
Ignoring minor ethical breaches, which can escalate into larger problems.
Managing Risks and Ensuring Compliance