Agile Certification Vocabulary
Practice Agile certification vocabulary: PSM, PMP, SAFe, PMI-ACP, practical experience requirements, PDUs, and how to talk about Agile credentials professionally.
0 / 45 completed
1 / 45
What does PSM stand for and who issues this certification?
PSM (Professional Scrum Master) is issued by Scrum.org, founded by Scrum co-creator Ken Schwaber. PSM I is the foundational level, PSM II and III are advanced. It's a rigorous knowledge-based assessment — no training required, just passing the exam.
2 / 45
What is the difference between PMP and PMI-ACP?
PMP is PMI's flagship general project management certification. PMI-ACP specifically validates Agile knowledge across multiple frameworks (Scrum, Kanban, SAFe, XP, Lean). Many practitioners hold both. PMI-ACP requires 21 hours of Agile training and Agile project experience.
3 / 45
What does SAFe certification validate?
SAFe (Scaled Agile Framework) certifications (like SAFe Scrum Master, SAFe Release Train Engineer) validate knowledge of scaling Agile across large organizations. SAFe is widely adopted in enterprises that struggle to apply team-level Agile across 50–500 person organizations.
4 / 45
How would you professionally introduce yourself as a certified Scrum Master in a job interview?
Professional credential introduction should include: the specific certification name and issuing body, the level, and relevant practical experience. Just naming a certification without context provides limited signal — pair it with how you've applied it.
5 / 45
What does 'the certification requires X hours of practical experience' mean and why does it matter?
Experience requirements mean you must document actual work hours applying the method. PMI-ACP requires 1,500+ hours of Agile project work. This distinguishes the credential from purely knowledge-based exams — it validates that you've done the work, not just read about it.
6 / 45
Sarah: "Hey team, just pushed a new feature to the `develop` branch – it's supposed to improve user onboarding. I've added a detailed PR description explaining the changes and linking to the relevant Jira ticket.
Mark: "Sounds good, but could you add some acceptance criteria to the PR?"
Which of the following best describes Mark's request regarding acceptance criteria in this scenario?Mark's request highlights the importance of acceptance criteria within an Agile workflow. Acceptance criteria aren't just requirements from Jira—they are specific, measurable conditions that must be satisfied for a feature to be considered 'done.' Failing to include them can lead to misunderstandings and rework later on, demonstrating a key principle of iterative development and reducing ambiguity during code reviews. The options incorrectly imply acceptance criteria only relate to testing or scope; they're crucial for validating the completed work against the desired outcome.
7 / 45
David: 'I've just submitted a pull request for the new API endpoint. I've included screenshots and a brief description of the changes in the PR body, but I wasn't sure if we should be defining specific acceptance criteria at this stage – it feels a bit premature given the ongoing development. Maria: 'No worries, David, just get your code merged!'Maria's response reflects a potentially overly-focused approach to some Agile methodologies, prioritizing speed of delivery above all else. While rapid development is important, acceptance criteria aren't 'premature'; they're *crucial* for defining what constitutes a successful implementation and preventing misunderstandings later on. David's hesitation highlights the importance of balancing velocity with quality assurance – a core principle often misunderstood in some Agile interpretations. Acceptance criteria provide tangible validation points throughout the development lifecycle, ensuring alignment between the developer's understanding and the product owner's vision.
8 / 45
John is a developer reviewing a pull request for a new payment processing integration. The PR description mentions 'successful transaction confirmation' and includes screenshots of the UI changes. Alice comments: 'This looks good, but how do we know this actually *works*? We need to define acceptance criteria before merging.' Which statement best reflects Alice's concern regarding Agile certification vocabulary within this scenario?
Alice's comment highlights the crucial role of 'acceptance criteria' in Agile development. This concept emphasizes that functionality doesn't just need to *look* right – it must also *work* as intended and be verifiable. The PMI-ACP certification focuses on validating these principles, ensuring teams deliver value through defined acceptance tests and a clear understanding of requirements, preventing issues arising from incomplete or ambiguous features. Options A, C, and D misinterpret the need for acceptance criteria beyond just UI changes.
9 / 45
During a Sprint Review, the team is showcasing their completed user authentication module. Liam, a newly certified Scrum Master, notices that the Product Owner isn't actively engaging with the demo and seems focused on pointing out minor UI inconsistencies. He wants to ensure the team is truly delivering value according to Agile principles. Which of the following phrases would be most appropriate for Liam to use when facilitating this discussion?
Liam: "Let's focus on whether this authentication module meets the core user needs as defined in the Product Backlog, and if it delivers a clear benefit to our users. Can we discuss how this aligns with the Sprint Goal?"Liam's question is crucial because it shifts the focus away from superficial critiques and back towards the core purpose of a Sprint: delivering valuable software. The incorrect options either ignore the fundamental principles of Agile (value delivery) or introduce unnecessary technical debates. By asking about alignment with the Product Backlog and Sprint Goal, Liam guides the discussion toward demonstrable value and ensures the team remains focused on what truly matters.
10 / 45
The team is struggling to define acceptance criteria for a new feature. Sarah, the Product Owner, states: 'We need to ensure this aligns with the Sprint Goal.' Liam, a newly certified Scrum Master, wants to guide the conversation towards value delivery. Which of the following responses would be most effective in facilitating that discussion?
Liam: "Let's revisit the user story and see how well this feature addresses it. Does it truly solve a problem for our users, and does it fit within the Sprint Goal's objectives? We can refine the acceptance criteria to ensure we're delivering tangible value."
This question tests understanding of Agile principles around value delivery and sprint goals. Option 3 directly addresses the core need – ensuring the feature provides tangible user benefits—and connects it back to the Sprint Goal, a key concept in Scrum. The other options miss this fundamental connection or introduce irrelevant considerations (technical debt, speed). It reflects how a certified Scrum Master should guide discussions towards delivering value.
11 / 45
Sarah: "Hey team, just pushed a new feature to the `develop` branch – it's supposed to improve user onboarding. I've added a detailed PR description explaining the changes and linking to the relevant Jira ticket.
Mark: "Sounds good, but could you add some acceptance criteria to the PR?"
Which of the following best describes Mark's request regarding acceptance criteria in this scenario?Mark's request highlights the importance of acceptance criteria within an Agile workflow. Acceptance criteria aren't just requirements from Jira—they are specific, measurable conditions that must be satisfied for a feature to be considered 'done.' Failing to include them can lead to misunderstandings and rework later on, demonstrating a key principle of iterative development and reducing ambiguity during code reviews. The options incorrectly imply acceptance criteria only relate to testing or scope; they're crucial for validating the completed work against the desired outcome.
12 / 45
David: 'I've just submitted a pull request for the new API endpoint. I've included screenshots and a brief description of the changes in the PR body, but I wasn't sure if we should be defining specific acceptance criteria at this stage – it feels a bit premature given the ongoing development. Maria: 'No worries, David, just get your code merged!'Maria's response reflects a potentially overly-focused approach to some Agile methodologies, prioritizing speed of delivery above all else. While rapid development is important, acceptance criteria aren't 'premature'; they're *crucial* for defining what constitutes a successful implementation and preventing misunderstandings later on. David's hesitation highlights the importance of balancing velocity with quality assurance – a core principle often misunderstood in some Agile interpretations. Acceptance criteria provide tangible validation points throughout the development lifecycle, ensuring alignment between the developer's understanding and the product owner's vision.
13 / 45
John is a developer reviewing a pull request for a new payment processing integration. The PR description mentions 'successful transaction confirmation' and includes screenshots of the UI changes. Alice comments: 'This looks good, but how do we know this actually *works*? We need to define acceptance criteria before merging.' Which statement best reflects Alice's concern regarding Agile certification vocabulary within this scenario?
Alice's comment highlights the crucial role of 'acceptance criteria' in Agile development. This concept emphasizes that functionality doesn't just need to *look* right – it must also *work* as intended and be verifiable. The PMI-ACP certification focuses on validating these principles, ensuring teams deliver value through defined acceptance tests and a clear understanding of requirements, preventing issues arising from incomplete or ambiguous features. Options A, C, and D misinterpret the need for acceptance criteria beyond just UI changes.
14 / 45
During a Sprint Review, the team is showcasing their completed user authentication module. Liam, a newly certified Scrum Master, notices that the Product Owner isn't actively engaging with the demo and seems focused on pointing out minor UI inconsistencies. He wants to ensure the team is truly delivering value according to Agile principles. Which of the following phrases would be most appropriate for Liam to use when facilitating this discussion?
Liam: "Let's focus on whether this authentication module meets the core user needs as defined in the Product Backlog, and if it delivers a clear benefit to our users. Can we discuss how this aligns with the Sprint Goal?"Liam's question is crucial because it shifts the focus away from superficial critiques and back towards the core purpose of a Sprint: delivering valuable software. The incorrect options either ignore the fundamental principles of Agile (value delivery) or introduce unnecessary technical debates. By asking about alignment with the Product Backlog and Sprint Goal, Liam guides the discussion toward demonstrable value and ensures the team remains focused on what truly matters.
15 / 45
The team is struggling to define acceptance criteria for a new feature. Sarah, the Product Owner, states: 'We need to ensure this aligns with the Sprint Goal.' Liam, a newly certified Scrum Master, wants to guide the conversation towards value delivery. Which of the following responses would be most effective in facilitating that discussion?
Liam: "Let's revisit the user story and see how well this feature addresses it. Does it truly solve a problem for our users, and does it fit within the Sprint Goal's objectives? We can refine the acceptance criteria to ensure we're delivering tangible value."
This question tests understanding of Agile principles around value delivery and sprint goals. Option 3 directly addresses the core need – ensuring the feature provides tangible user benefits—and connects it back to the Sprint Goal, a key concept in Scrum. The other options miss this fundamental connection or introduce irrelevant considerations (technical debt, speed). It reflects how a certified Scrum Master should guide discussions towards delivering value.
16 / 45
Sarah: "Hey team, just pushed a new feature to the `develop` branch – it's supposed to improve user onboarding. I've added a detailed PR description explaining the changes and linking to the relevant Jira ticket.
Mark: "Sounds good, but could you add some acceptance criteria to the PR?"
Which of the following best describes Mark's request regarding acceptance criteria in this scenario?Mark's request highlights the importance of acceptance criteria within an Agile workflow. Acceptance criteria aren't just requirements from Jira—they are specific, measurable conditions that must be satisfied for a feature to be considered 'done.' Failing to include them can lead to misunderstandings and rework later on, demonstrating a key principle of iterative development and reducing ambiguity during code reviews. The options incorrectly imply acceptance criteria only relate to testing or scope; they're crucial for validating the completed work against the desired outcome.
17 / 45
David: 'I've just submitted a pull request for the new API endpoint. I've included screenshots and a brief description of the changes in the PR body, but I wasn't sure if we should be defining specific acceptance criteria at this stage – it feels a bit premature given the ongoing development. Maria: 'No worries, David, just get your code merged!'Maria's response reflects a potentially overly-focused approach to some Agile methodologies, prioritizing speed of delivery above all else. While rapid development is important, acceptance criteria aren't 'premature'; they're *crucial* for defining what constitutes a successful implementation and preventing misunderstandings later on. David's hesitation highlights the importance of balancing velocity with quality assurance – a core principle often misunderstood in some Agile interpretations. Acceptance criteria provide tangible validation points throughout the development lifecycle, ensuring alignment between the developer's understanding and the product owner's vision.
18 / 45
John is a developer reviewing a pull request for a new payment processing integration. The PR description mentions 'successful transaction confirmation' and includes screenshots of the UI changes. Alice comments: 'This looks good, but how do we know this actually *works*? We need to define acceptance criteria before merging.' Which statement best reflects Alice's concern regarding Agile certification vocabulary within this scenario?
Alice's comment highlights the crucial role of 'acceptance criteria' in Agile development. This concept emphasizes that functionality doesn't just need to *look* right – it must also *work* as intended and be verifiable. The PMI-ACP certification focuses on validating these principles, ensuring teams deliver value through defined acceptance tests and a clear understanding of requirements, preventing issues arising from incomplete or ambiguous features. Options A, C, and D misinterpret the need for acceptance criteria beyond just UI changes.
19 / 45
During a Sprint Review, the team is showcasing their completed user authentication module. Liam, a newly certified Scrum Master, notices that the Product Owner isn't actively engaging with the demo and seems focused on pointing out minor UI inconsistencies. He wants to ensure the team is truly delivering value according to Agile principles. Which of the following phrases would be most appropriate for Liam to use when facilitating this discussion?
Liam: "Let's focus on whether this authentication module meets the core user needs as defined in the Product Backlog, and if it delivers a clear benefit to our users. Can we discuss how this aligns with the Sprint Goal?"Liam's question is crucial because it shifts the focus away from superficial critiques and back towards the core purpose of a Sprint: delivering valuable software. The incorrect options either ignore the fundamental principles of Agile (value delivery) or introduce unnecessary technical debates. By asking about alignment with the Product Backlog and Sprint Goal, Liam guides the discussion toward demonstrable value and ensures the team remains focused on what truly matters.
20 / 45
The team is struggling to define acceptance criteria for a new feature. Sarah, the Product Owner, states: 'We need to ensure this aligns with the Sprint Goal.' Liam, a newly certified Scrum Master, wants to guide the conversation towards value delivery. Which of the following responses would be most effective in facilitating that discussion?
Liam: "Let's revisit the user story and see how well this feature addresses it. Does it truly solve a problem for our users, and does it fit within the Sprint Goal's objectives? We can refine the acceptance criteria to ensure we're delivering tangible value."
This question tests understanding of Agile principles around value delivery and sprint goals. Option 3 directly addresses the core need – ensuring the feature provides tangible user benefits—and connects it back to the Sprint Goal, a key concept in Scrum. The other options miss this fundamental connection or introduce irrelevant considerations (technical debt, speed). It reflects how a certified Scrum Master should guide discussions towards delivering value.
21 / 45
Sarah: "Hey team, just pushed a new feature to the `develop` branch – it's supposed to improve user onboarding. I've added a detailed PR description explaining the changes and linking to the relevant Jira ticket.
Mark: "Sounds good, but could you add some acceptance criteria to the PR?"
Which of the following best describes Mark's request regarding acceptance criteria in this scenario?Mark's request highlights the importance of acceptance criteria within an Agile workflow. Acceptance criteria aren't just requirements from Jira—they are specific, measurable conditions that must be satisfied for a feature to be considered 'done.' Failing to include them can lead to misunderstandings and rework later on, demonstrating a key principle of iterative development and reducing ambiguity during code reviews. The options incorrectly imply acceptance criteria only relate to testing or scope; they're crucial for validating the completed work against the desired outcome.
22 / 45
David: 'I've just submitted a pull request for the new API endpoint. I've included screenshots and a brief description of the changes in the PR body, but I wasn't sure if we should be defining specific acceptance criteria at this stage – it feels a bit premature given the ongoing development. Maria: 'No worries, David, just get your code merged!'Maria's response reflects a potentially overly-focused approach to some Agile methodologies, prioritizing speed of delivery above all else. While rapid development is important, acceptance criteria aren't 'premature'; they're *crucial* for defining what constitutes a successful implementation and preventing misunderstandings later on. David's hesitation highlights the importance of balancing velocity with quality assurance – a core principle often misunderstood in some Agile interpretations. Acceptance criteria provide tangible validation points throughout the development lifecycle, ensuring alignment between the developer's understanding and the product owner's vision.
23 / 45
John is a developer reviewing a pull request for a new payment processing integration. The PR description mentions 'successful transaction confirmation' and includes screenshots of the UI changes. Alice comments: 'This looks good, but how do we know this actually *works*? We need to define acceptance criteria before merging.' Which statement best reflects Alice's concern regarding Agile certification vocabulary within this scenario?
Alice's comment highlights the crucial role of 'acceptance criteria' in Agile development. This concept emphasizes that functionality doesn't just need to *look* right – it must also *work* as intended and be verifiable. The PMI-ACP certification focuses on validating these principles, ensuring teams deliver value through defined acceptance tests and a clear understanding of requirements, preventing issues arising from incomplete or ambiguous features. Options A, C, and D misinterpret the need for acceptance criteria beyond just UI changes.
24 / 45
During a Sprint Review, the team is showcasing their completed user authentication module. Liam, a newly certified Scrum Master, notices that the Product Owner isn't actively engaging with the demo and seems focused on pointing out minor UI inconsistencies. He wants to ensure the team is truly delivering value according to Agile principles. Which of the following phrases would be most appropriate for Liam to use when facilitating this discussion?
Liam: "Let's focus on whether this authentication module meets the core user needs as defined in the Product Backlog, and if it delivers a clear benefit to our users. Can we discuss how this aligns with the Sprint Goal?"Liam's question is crucial because it shifts the focus away from superficial critiques and back towards the core purpose of a Sprint: delivering valuable software. The incorrect options either ignore the fundamental principles of Agile (value delivery) or introduce unnecessary technical debates. By asking about alignment with the Product Backlog and Sprint Goal, Liam guides the discussion toward demonstrable value and ensures the team remains focused on what truly matters.
25 / 45
The team is struggling to define acceptance criteria for a new feature. Sarah, the Product Owner, states: 'We need to ensure this aligns with the Sprint Goal.' Liam, a newly certified Scrum Master, wants to guide the conversation towards value delivery. Which of the following responses would be most effective in facilitating that discussion?
Liam: "Let's revisit the user story and see how well this feature addresses it. Does it truly solve a problem for our users, and does it fit within the Sprint Goal's objectives? We can refine the acceptance criteria to ensure we're delivering tangible value."
This question tests understanding of Agile principles around value delivery and sprint goals. Option 3 directly addresses the core need – ensuring the feature provides tangible user benefits—and connects it back to the Sprint Goal, a key concept in Scrum. The other options miss this fundamental connection or introduce irrelevant considerations (technical debt, speed). It reflects how a certified Scrum Master should guide discussions towards delivering value.
26 / 45
Sarah: "Hey team, just pushed a new feature to the `develop` branch – it's supposed to improve user onboarding. I've added a detailed PR description explaining the changes and linking to the relevant Jira ticket.
Mark: "Sounds good, but could you add some acceptance criteria to the PR?"
Which of the following best describes Mark's request regarding acceptance criteria in this scenario?Mark's request highlights the importance of acceptance criteria within an Agile workflow. Acceptance criteria aren't just requirements from Jira—they are specific, measurable conditions that must be satisfied for a feature to be considered 'done.' Failing to include them can lead to misunderstandings and rework later on, demonstrating a key principle of iterative development and reducing ambiguity during code reviews. The options incorrectly imply acceptance criteria only relate to testing or scope; they're crucial for validating the completed work against the desired outcome.
27 / 45
David: 'I've just submitted a pull request for the new API endpoint. I've included screenshots and a brief description of the changes in the PR body, but I wasn't sure if we should be defining specific acceptance criteria at this stage – it feels a bit premature given the ongoing development. Maria: 'No worries, David, just get your code merged!'Maria's response reflects a potentially overly-focused approach to some Agile methodologies, prioritizing speed of delivery above all else. While rapid development is important, acceptance criteria aren't 'premature'; they're *crucial* for defining what constitutes a successful implementation and preventing misunderstandings later on. David's hesitation highlights the importance of balancing velocity with quality assurance – a core principle often misunderstood in some Agile interpretations. Acceptance criteria provide tangible validation points throughout the development lifecycle, ensuring alignment between the developer's understanding and the product owner's vision.
28 / 45
John is a developer reviewing a pull request for a new payment processing integration. The PR description mentions 'successful transaction confirmation' and includes screenshots of the UI changes. Alice comments: 'This looks good, but how do we know this actually *works*? We need to define acceptance criteria before merging.' Which statement best reflects Alice's concern regarding Agile certification vocabulary within this scenario?
Alice's comment highlights the crucial role of 'acceptance criteria' in Agile development. This concept emphasizes that functionality doesn't just need to *look* right – it must also *work* as intended and be verifiable. The PMI-ACP certification focuses on validating these principles, ensuring teams deliver value through defined acceptance tests and a clear understanding of requirements, preventing issues arising from incomplete or ambiguous features. Options A, C, and D misinterpret the need for acceptance criteria beyond just UI changes.
29 / 45
During a Sprint Review, the team is showcasing their completed user authentication module. Liam, a newly certified Scrum Master, notices that the Product Owner isn't actively engaging with the demo and seems focused on pointing out minor UI inconsistencies. He wants to ensure the team is truly delivering value according to Agile principles. Which of the following phrases would be most appropriate for Liam to use when facilitating this discussion?
Liam: "Let's focus on whether this authentication module meets the core user needs as defined in the Product Backlog, and if it delivers a clear benefit to our users. Can we discuss how this aligns with the Sprint Goal?"Liam's question is crucial because it shifts the focus away from superficial critiques and back towards the core purpose of a Sprint: delivering valuable software. The incorrect options either ignore the fundamental principles of Agile (value delivery) or introduce unnecessary technical debates. By asking about alignment with the Product Backlog and Sprint Goal, Liam guides the discussion toward demonstrable value and ensures the team remains focused on what truly matters.
30 / 45
The team is struggling to define acceptance criteria for a new feature. Sarah, the Product Owner, states: 'We need to ensure this aligns with the Sprint Goal.' Liam, a newly certified Scrum Master, wants to guide the conversation towards value delivery. Which of the following responses would be most effective in facilitating that discussion?
Liam: "Let's revisit the user story and see how well this feature addresses it. Does it truly solve a problem for our users, and does it fit within the Sprint Goal's objectives? We can refine the acceptance criteria to ensure we're delivering tangible value."
This question tests understanding of Agile principles around value delivery and sprint goals. Option 3 directly addresses the core need – ensuring the feature provides tangible user benefits—and connects it back to the Sprint Goal, a key concept in Scrum. The other options miss this fundamental connection or introduce irrelevant considerations (technical debt, speed). It reflects how a certified Scrum Master should guide discussions towards delivering value.
31 / 45
Sarah: "Hey team, just pushed a new feature to the `develop` branch – it's supposed to improve user onboarding. I've added a detailed PR description explaining the changes and linking to the relevant Jira ticket.
Mark: "Sounds good, but could you add some acceptance criteria to the PR?"
Which of the following best describes Mark's request regarding acceptance criteria in this scenario?Mark's request highlights the importance of acceptance criteria within an Agile workflow. Acceptance criteria aren't just requirements from Jira—they are specific, measurable conditions that must be satisfied for a feature to be considered 'done.' Failing to include them can lead to misunderstandings and rework later on, demonstrating a key principle of iterative development and reducing ambiguity during code reviews. The options incorrectly imply acceptance criteria only relate to testing or scope; they're crucial for validating the completed work against the desired outcome.
32 / 45
David: 'I've just submitted a pull request for the new API endpoint. I've included screenshots and a brief description of the changes in the PR body, but I wasn't sure if we should be defining specific acceptance criteria at this stage – it feels a bit premature given the ongoing development. Maria: 'No worries, David, just get your code merged!'Maria's response reflects a potentially overly-focused approach to some Agile methodologies, prioritizing speed of delivery above all else. While rapid development is important, acceptance criteria aren't 'premature'; they're *crucial* for defining what constitutes a successful implementation and preventing misunderstandings later on. David's hesitation highlights the importance of balancing velocity with quality assurance – a core principle often misunderstood in some Agile interpretations. Acceptance criteria provide tangible validation points throughout the development lifecycle, ensuring alignment between the developer's understanding and the product owner's vision.
33 / 45
John is a developer reviewing a pull request for a new payment processing integration. The PR description mentions 'successful transaction confirmation' and includes screenshots of the UI changes. Alice comments: 'This looks good, but how do we know this actually *works*? We need to define acceptance criteria before merging.' Which statement best reflects Alice's concern regarding Agile certification vocabulary within this scenario?
Alice's comment highlights the crucial role of 'acceptance criteria' in Agile development. This concept emphasizes that functionality doesn't just need to *look* right – it must also *work* as intended and be verifiable. The PMI-ACP certification focuses on validating these principles, ensuring teams deliver value through defined acceptance tests and a clear understanding of requirements, preventing issues arising from incomplete or ambiguous features. Options A, C, and D misinterpret the need for acceptance criteria beyond just UI changes.
34 / 45
During a Sprint Review, the team is showcasing their completed user authentication module. Liam, a newly certified Scrum Master, notices that the Product Owner isn't actively engaging with the demo and seems focused on pointing out minor UI inconsistencies. He wants to ensure the team is truly delivering value according to Agile principles. Which of the following phrases would be most appropriate for Liam to use when facilitating this discussion?
Liam: "Let's focus on whether this authentication module meets the core user needs as defined in the Product Backlog, and if it delivers a clear benefit to our users. Can we discuss how this aligns with the Sprint Goal?"Liam's question is crucial because it shifts the focus away from superficial critiques and back towards the core purpose of a Sprint: delivering valuable software. The incorrect options either ignore the fundamental principles of Agile (value delivery) or introduce unnecessary technical debates. By asking about alignment with the Product Backlog and Sprint Goal, Liam guides the discussion toward demonstrable value and ensures the team remains focused on what truly matters.
35 / 45
The team is struggling to define acceptance criteria for a new feature. Sarah, the Product Owner, states: 'We need to ensure this aligns with the Sprint Goal.' Liam, a newly certified Scrum Master, wants to guide the conversation towards value delivery. Which of the following responses would be most effective in facilitating that discussion?
Liam: "Let's revisit the user story and see how well this feature addresses it. Does it truly solve a problem for our users, and does it fit within the Sprint Goal's objectives? We can refine the acceptance criteria to ensure we're delivering tangible value."
This question tests understanding of Agile principles around value delivery and sprint goals. Option 3 directly addresses the core need – ensuring the feature provides tangible user benefits—and connects it back to the Sprint Goal, a key concept in Scrum. The other options miss this fundamental connection or introduce irrelevant considerations (technical debt, speed). It reflects how a certified Scrum Master should guide discussions towards delivering value.
36 / 45
Sarah: "Hey team, just pushed a new feature to the `develop` branch – it's supposed to improve user onboarding. I've added a detailed PR description explaining the changes and linking to the relevant Jira ticket.
Mark: "Sounds good, but could you add some acceptance criteria to the PR?"
Which of the following best describes Mark's request regarding acceptance criteria in this scenario?Mark's request highlights the importance of acceptance criteria within an Agile workflow. Acceptance criteria aren't just requirements from Jira—they are specific, measurable conditions that must be satisfied for a feature to be considered 'done.' Failing to include them can lead to misunderstandings and rework later on, demonstrating a key principle of iterative development and reducing ambiguity during code reviews. The options incorrectly imply acceptance criteria only relate to testing or scope; they're crucial for validating the completed work against the desired outcome.
37 / 45
David: 'I've just submitted a pull request for the new API endpoint. I've included screenshots and a brief description of the changes in the PR body, but I wasn't sure if we should be defining specific acceptance criteria at this stage – it feels a bit premature given the ongoing development. Maria: 'No worries, David, just get your code merged!'Maria's response reflects a potentially overly-focused approach to some Agile methodologies, prioritizing speed of delivery above all else. While rapid development is important, acceptance criteria aren't 'premature'; they're *crucial* for defining what constitutes a successful implementation and preventing misunderstandings later on. David's hesitation highlights the importance of balancing velocity with quality assurance – a core principle often misunderstood in some Agile interpretations. Acceptance criteria provide tangible validation points throughout the development lifecycle, ensuring alignment between the developer's understanding and the product owner's vision.
38 / 45
John is a developer reviewing a pull request for a new payment processing integration. The PR description mentions 'successful transaction confirmation' and includes screenshots of the UI changes. Alice comments: 'This looks good, but how do we know this actually *works*? We need to define acceptance criteria before merging.' Which statement best reflects Alice's concern regarding Agile certification vocabulary within this scenario?
Alice's comment highlights the crucial role of 'acceptance criteria' in Agile development. This concept emphasizes that functionality doesn't just need to *look* right – it must also *work* as intended and be verifiable. The PMI-ACP certification focuses on validating these principles, ensuring teams deliver value through defined acceptance tests and a clear understanding of requirements, preventing issues arising from incomplete or ambiguous features. Options A, C, and D misinterpret the need for acceptance criteria beyond just UI changes.
39 / 45
During a Sprint Review, the team is showcasing their completed user authentication module. Liam, a newly certified Scrum Master, notices that the Product Owner isn't actively engaging with the demo and seems focused on pointing out minor UI inconsistencies. He wants to ensure the team is truly delivering value according to Agile principles. Which of the following phrases would be most appropriate for Liam to use when facilitating this discussion?
Liam: "Let's focus on whether this authentication module meets the core user needs as defined in the Product Backlog, and if it delivers a clear benefit to our users. Can we discuss how this aligns with the Sprint Goal?"Liam's question is crucial because it shifts the focus away from superficial critiques and back towards the core purpose of a Sprint: delivering valuable software. The incorrect options either ignore the fundamental principles of Agile (value delivery) or introduce unnecessary technical debates. By asking about alignment with the Product Backlog and Sprint Goal, Liam guides the discussion toward demonstrable value and ensures the team remains focused on what truly matters.
40 / 45
The team is struggling to define acceptance criteria for a new feature. Sarah, the Product Owner, states: 'We need to ensure this aligns with the Sprint Goal.' Liam, a newly certified Scrum Master, wants to guide the conversation towards value delivery. Which of the following responses would be most effective in facilitating that discussion?
Liam: "Let's revisit the user story and see how well this feature addresses it. Does it truly solve a problem for our users, and does it fit within the Sprint Goal's objectives? We can refine the acceptance criteria to ensure we're delivering tangible value."
This question tests understanding of Agile principles around value delivery and sprint goals. Option 3 directly addresses the core need – ensuring the feature provides tangible user benefits—and connects it back to the Sprint Goal, a key concept in Scrum. The other options miss this fundamental connection or introduce irrelevant considerations (technical debt, speed). It reflects how a certified Scrum Master should guide discussions towards delivering value.
41 / 45
Sarah: "Hey team, just pushed a new feature to the `develop` branch – it's supposed to improve user onboarding. I've added a detailed PR description explaining the changes and linking to the relevant Jira ticket.
Mark: "Sounds good, but could you add some acceptance criteria to the PR?"
Which of the following best describes Mark's request regarding acceptance criteria in this scenario?Mark's request highlights the importance of acceptance criteria within an Agile workflow. Acceptance criteria aren't just requirements from Jira—they are specific, measurable conditions that must be satisfied for a feature to be considered 'done.' Failing to include them can lead to misunderstandings and rework later on, demonstrating a key principle of iterative development and reducing ambiguity during code reviews. The options incorrectly imply acceptance criteria only relate to testing or scope; they're crucial for validating the completed work against the desired outcome.
42 / 45
David: 'I've just submitted a pull request for the new API endpoint. I've included screenshots and a brief description of the changes in the PR body, but I wasn't sure if we should be defining specific acceptance criteria at this stage – it feels a bit premature given the ongoing development. Maria: 'No worries, David, just get your code merged!'Maria's response reflects a potentially overly-focused approach to some Agile methodologies, prioritizing speed of delivery above all else. While rapid development is important, acceptance criteria aren't 'premature'; they're *crucial* for defining what constitutes a successful implementation and preventing misunderstandings later on. David's hesitation highlights the importance of balancing velocity with quality assurance – a core principle often misunderstood in some Agile interpretations. Acceptance criteria provide tangible validation points throughout the development lifecycle, ensuring alignment between the developer's understanding and the product owner's vision.
43 / 45
John is a developer reviewing a pull request for a new payment processing integration. The PR description mentions 'successful transaction confirmation' and includes screenshots of the UI changes. Alice comments: 'This looks good, but how do we know this actually *works*? We need to define acceptance criteria before merging.' Which statement best reflects Alice's concern regarding Agile certification vocabulary within this scenario?
Alice's comment highlights the crucial role of 'acceptance criteria' in Agile development. This concept emphasizes that functionality doesn't just need to *look* right – it must also *work* as intended and be verifiable. The PMI-ACP certification focuses on validating these principles, ensuring teams deliver value through defined acceptance tests and a clear understanding of requirements, preventing issues arising from incomplete or ambiguous features. Options A, C, and D misinterpret the need for acceptance criteria beyond just UI changes.
44 / 45
During a Sprint Review, the team is showcasing their completed user authentication module. Liam, a newly certified Scrum Master, notices that the Product Owner isn't actively engaging with the demo and seems focused on pointing out minor UI inconsistencies. He wants to ensure the team is truly delivering value according to Agile principles. Which of the following phrases would be most appropriate for Liam to use when facilitating this discussion?
Liam: "Let's focus on whether this authentication module meets the core user needs as defined in the Product Backlog, and if it delivers a clear benefit to our users. Can we discuss how this aligns with the Sprint Goal?"Liam's question is crucial because it shifts the focus away from superficial critiques and back towards the core purpose of a Sprint: delivering valuable software. The incorrect options either ignore the fundamental principles of Agile (value delivery) or introduce unnecessary technical debates. By asking about alignment with the Product Backlog and Sprint Goal, Liam guides the discussion toward demonstrable value and ensures the team remains focused on what truly matters.
45 / 45
The team is struggling to define acceptance criteria for a new feature. Sarah, the Product Owner, states: 'We need to ensure this aligns with the Sprint Goal.' Liam, a newly certified Scrum Master, wants to guide the conversation towards value delivery. Which of the following responses would be most effective in facilitating that discussion?
Liam: "Let's revisit the user story and see how well this feature addresses it. Does it truly solve a problem for our users, and does it fit within the Sprint Goal's objectives? We can refine the acceptance criteria to ensure we're delivering tangible value."
This question tests understanding of Agile principles around value delivery and sprint goals. Option 3 directly addresses the core need – ensuring the feature provides tangible user benefits—and connects it back to the Sprint Goal, a key concept in Scrum. The other options miss this fundamental connection or introduce irrelevant considerations (technical debt, speed). It reflects how a certified Scrum Master should guide discussions towards delivering value.
Frequently Asked Questions
What will I practice in "Agile Certification Vocabulary"?
This is a Certification Prep exercise set. It walks through 45 scenario-based multiple-choice questions built around real usage of Certification Prep terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 45 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the Certification Prep vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more Certification Prep exercises?
See the Certification Prep exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — Certification Prep vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.