Certbie

Free practice · No sign-up required

Scrum Developer Professional Certification Exam free practice test

30 questions with answer explanations. Choose an answer below to begin.

Question 1 of 30

Mr. Johnson\'s team has been struggling with productivity and team morale in recent sprints. To address this, he wants to introduce a new retrospective technique to foster team learning and improvement. Which of the following techniques is most suitable for achieving this goal?

0/30 answered · Bookmark questions to review later. Focus the practice area to use keys 1–9 and Enter.

Learn by doing

Put your answers into practice

Use official documentation and hands-on labs to work through topics you missed.

Explore all study resources →

All questions and explanations

Prefer to read at your own pace? Work through each question below, then open its answer to check your reasoning. You can link directly to a question or print this reference.

  1. Question 1

    Link to question

    Mr. Johnson\'s team has been struggling with productivity and team morale in recent sprints. To address this, he wants to introduce a new retrospective technique to foster team learning and improvement. Which of the following techniques is most suitable for achieving this goal?

    1. The Starfish Retrospective (Keep, Start, Stop, Less, More)

    2. The Timeline Retrospective (mapping events chronologically)

    3. The Four Ls Retrospective (Liked, Learned, Lacked, Longed for)

    4. The Sailboat Retrospective (anchors, sails, rocks, and land)

    Show answer and explanation

    Correct answer

    • The Four Ls Retrospective (Liked, Learned, Lacked, Longed for)

    The Four Ls Retrospective (Liked, Learned, Lacked, Longed for) is a comprehensive approach that encourages team members to reflect on various aspects of the sprint. It not only helps identify what went well and what didn\'t but also uncovers areas for future improvement. This technique promotes deep learning and continuous improvement, aligning with Agile principles of fostering a culture of introspection and adaptability. The other techniques are useful in their own right but may not cover the breadth of insights that the Four Ls can provide.

  2. Question 2

    Link to question

    John\'s Scrum team has grown significantly, and he is considering scaling Scrum to manage multiple teams effectively. Which framework is designed for scaling Scrum across multiple teams?

    1. Kanban

    2. Nexus

    3. Extreme Programming (XP)

    4. Lean Startup

    Show answer and explanation

    Correct answer

    • Nexus

    Nexus is a framework specifically designed to scale Scrum for large product and software development initiatives involving multiple Scrum teams. It extends Scrum\'s core principles and practices to facilitate coordination, integration, and alignment across multiple teams working towards a shared goal. Kanban, XP, and Lean Startup are other Agile methodologies but are not specifically focused on scaling Scrum. Nexus provides additional roles, artifacts, and events to manage dependencies and increase transparency in a scaled environment.

  3. Question 3

    Link to question

    Sarah is leading an Agile project in the finance department of her company. She faces resistance as her team believes Agile is only suitable for software development. Which of the following arguments best supports the application of Agile principles in non-technical domains?

    1. Agile allows for flexible budgeting and real-time financial reporting.

    2. Agile's iterative approach ensures better quality control in software.

    3. Agile emphasizes customer feedback, which is irrelevant to finance.

    4. Agile improves collaboration and transparency, which are crucial in finance.

    Show answer and explanation

    Correct answer

    • Agile improves collaboration and transparency, which are crucial in finance.

    Agile principles, such as improving collaboration and transparency, are universal and beneficial in any domain, including finance. These principles help teams respond to changes efficiently, enhance communication, and ensure all stakeholders are aligned. While options a), b), and c) contain some elements of Agile benefits, they either focus too narrowly on software development or miss the broader applicability of Agile principles. The correct answer highlights the fundamental Agile values that can drive success in non-technical fields.

  4. Question 4

    Link to question

    Mary is a Scrum Master working in a highly regulated industry. She needs to ensure her Agile team complies with industry standards and regulations while maintaining Agile principles. What is the best approach for Mary to achieve this?

    1. Implement a strict Waterfall methodology alongside Agile.

    2. Ignore industry standards to focus on Agile processes.

    3. Adapt the Definition of Done to include regulatory requirements.

    4. Conduct all work in short sprints without considering compliance.

    Show answer and explanation

    Correct answer

    • Adapt the Definition of Done to include regulatory requirements.

    Integrating regulatory requirements into the Definition of Done ensures that compliance is built into every increment of the product. This approach aligns with Agile principles by embedding compliance within the development process rather than treating it as an afterthought. Options a) and c) are not suitable as they either compromise Agile principles or ignore necessary regulations. Option d) overlooks the critical aspect of compliance, which could lead to significant risks and non-compliance issues.

  5. Question 5

    Link to question

    Alyssa\'s team is using Scrum in a marketing project. They are experiencing challenges due to the differences between software development and marketing work. Which adaptation could help them apply Scrum principles more effectively in their context?

    1. Use longer sprints to accommodate marketing campaign timelines.

    2. Focus solely on task completion rather than customer feedback.

    3. Incorporate marketing-specific roles within the Scrum framework.

    4. Eliminate the role of Scrum Master to simplify the process.

    Show answer and explanation

    Correct answer

    • Incorporate marketing-specific roles within the Scrum framework.

    Incorporating roles that understand the specific needs and dynamics of marketing can help bridge the gap between Scrum principles and marketing work. This adaptation allows the team to maintain the structure and discipline of Scrum while addressing the unique requirements of marketing projects. Options a), b), and d) either compromise Agile principles or ignore the specific challenges faced in marketing. The correct answer ensures that Scrum remains relevant and effective in a non-technical domain.

  6. Question 6

    Link to question

    Tom\'s company has successfully implemented Agile practices in their IT department and now wants to extend these practices to HR. Which case study approach would be most beneficial for Tom to present to his team?

    1. A case study on Agile in software development

    2. A case study on traditional HR practices

    3. A case study on Lean manufacturing

    4. A case study on Agile transformation in HR

    Show answer and explanation

    Correct answer

    • A case study on Agile transformation in HR

    A case study on Agile transformation in HR would provide the most relevant insights and examples for Tom\'s team, showing how Agile principles can be applied and adapted to HR processes. This type of case study would illustrate the benefits and challenges specific to HR, helping the team understand the practical implications and potential outcomes. Options a), b), and c) either focus on unrelated areas or do not provide the necessary context for HR transformation.

  7. Question 7

    Link to question

    Dr. Lewis is leading a Scrum team in a healthcare project that involves strict adherence to patient privacy regulations. Which of the following should be included in the Scrum process to ensure compliance with these regulations?

    1. Regular reviews by legal and compliance experts

    2. Prioritize speed over compliance to meet deadlines

    3. Conduct all work without documenting compliance efforts

    4. Implement compliance checks only at the end of the project

    Show answer and explanation

    Correct answer

    • Regular reviews by legal and compliance experts

    Regular reviews by legal and compliance experts ensure that the Scrum process adheres to patient privacy regulations throughout the project. This approach integrates compliance into the Agile process, aligning with the principle of delivering potentially shippable increments while maintaining high standards of quality and compliance. Options b), c), and d) either compromise compliance or introduce risks by deferring compliance checks until the end. The correct answer ensures ongoing adherence to regulations.

  8. Question 8

    Link to question

    Jessica is a Scrum Master who wants to implement Kaizen practices in her Agile team to foster continuous improvement. Which of the following actions is most aligned with Kaizen principles?

    1. Conducting a major process overhaul every year

    2. Encouraging small, incremental changes regularly

    3. Implementing changes without team involvement

    4. Focusing on short-term gains over long-term improvement

    Show answer and explanation

    Correct answer

    • Encouraging small, incremental changes regularly

    Kaizen emphasizes continuous improvement through small, incremental changes that involve the entire team. This approach aligns with Agile principles of iterative development and regular reflection, promoting a culture of ongoing enhancement. Options a), c), and d) contradict Kaizen principles by focusing on large-scale changes, excluding team involvement, or prioritizing short-term gains. The correct answer fosters a sustainable and collaborative improvement process.

  9. Question 9

    Link to question

    Alex is managing a Scrum team that frequently encounters the same issues sprint after sprint. To address this, Alex decides to use a specific Scrum pattern. Which pattern should Alex consider to identify and address these recurring issues?

    1. The Product Backlog Refinement pattern

    2. The Definition of Done pattern

    3. The Sprint Review pattern

    4. The Retrospective pattern

    Show answer and explanation

    Correct answer

    • The Retrospective pattern

    The Retrospective pattern is designed to identify and address recurring issues by reflecting on the previous sprint and discussing what went well, what didn\'t, and how processes can be improved. This pattern is crucial for continuous improvement and helps the team learn from past experiences to enhance future performance. Options a), b), and c) are important Scrum practices but do not specifically focus on identifying and resolving recurring issues. The correct answer ensures that the team systematically addresses and mitigates problems.

  10. Question 10

    Link to question

    Nancy is an Agile coach tasked with ensuring that her team\'s Agile practices comply with industry standards and regulations. What should Nancy prioritize to achieve this goal?

    1. Focus on delivering work quickly, regardless of compliance

    2. Integrate compliance checks into the Definition of Done

    3. Ignore compliance issues to maintain team velocity

    4. Conduct compliance audits only at project completion

    Show answer and explanation

    Correct answer

    • Integrate compliance checks into the Definition of Done

    Integrating compliance checks into the Definition of Done ensures that every increment of work meets industry standards and regulations. This approach aligns compliance with Agile principles of delivering high-quality, potentially shippable increments. Options a), c), and d) either compromise compliance or defer critical checks until the end of the project, which can introduce risks and non-compliance issues. The correct answer embeds compliance into the Agile process, ensuring ongoing adherence to standards and regulations.

  11. Question 11

    Link to question

    Sarah, a Scrum Developer, is working on a project that requires integrating AI capabilities into the existing product. The team is unsure about how to prioritize the AI-related tasks due to the ethical implications involved. What should Sarah consider when making decisions about task prioritization?

    1. Focus solely on technical feasibility.

    2. Prioritize tasks that align with the company's immediate business goals.

    3. Consider the potential ethical impact of each task alongside technical and business priorities.

    4. Defer all AI-related tasks until ethical guidelines are clearer.

    Show answer and explanation

    Correct answer

    • Consider the potential ethical impact of each task alongside technical and business priorities.

    In Agile, decision-making and prioritization should balance technical feasibility, business goals, and ethical implications. Prioritizing solely based on business or technical aspects can lead to unethical outcomes. Ethical decision-making ensures that the product does not harm users and aligns with societal values. This approach is supported by Agile principles which emphasize delivering value while maintaining integrity.

  12. Question 12

    Link to question

    John is part of a hybrid project management team where some parts of the project follow Agile methodologies while others use traditional Waterfall approaches. His task is to ensure smooth integration between these methodologies. What should John focus on to achieve this?

    1. Strictly adhere to Agile practices and disregard Waterfall methods.

    2. Use a unified project management tool that accommodates both Agile and Waterfall.

    3. Apply Agile practices to Waterfall tasks.

    4. Insist on converting all Waterfall tasks to Agile tasks.

    Show answer and explanation

    Correct answer

    • Use a unified project management tool that accommodates both Agile and Waterfall.

    In a hybrid project management environment, using a unified tool that supports both Agile and Waterfall methodologies helps in seamless integration. This ensures visibility, collaboration, and tracking across different methodologies, allowing the team to benefit from the strengths of both approaches. Adhering strictly to one methodology or forcing a conversion can disrupt project flow and reduce efficiency.

  13. Question 13

    Link to question

    Maria is leading a Scrum team and wants to prepare for future directions in Agile methodologies. She believes incorporating new trends will keep her team ahead. Which trend should Maria prioritize?

    1. Strictly adhering to traditional Scrum practices without modifications.

    2. Focusing only on current Agile practices without considering future trends.

    3. Avoiding changes until new methodologies are widely accepted.

    4. Exploring ways to integrate AI and machine learning into Agile practices.

    Show answer and explanation

    Correct answer

    • Exploring ways to integrate AI and machine learning into Agile practices.

    The future of Agile methodologies includes integrating AI and machine learning to enhance efficiency and decision-making. Exploring these trends allows teams to stay innovative and competitive. Traditional practices provide a foundation, but adapting to advancements ensures continuous improvement and relevance in a rapidly evolving field.

  14. Question 14

    Link to question

    Alex is a Scrum Developer tasked with writing user stories for a complex feature. He wants to ensure these stories are effective and meet the INVEST criteria. What should Alex do?

    1. Write high-level descriptions without focusing on details.

    2. Ensure each user story is independent, negotiable, valuable, estimable, small, and testable.

    3. Combine multiple features into a single user story to save time.

    4. Write stories that are dependent on each other to maintain flow.

    Show answer and explanation

    Correct answer

    • Ensure each user story is independent, negotiable, valuable, estimable, small, and testable.

    Effective user stories should meet the INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, and Testable. This ensures clarity, facilitates prioritization, and makes the stories manageable and deliverable within a sprint. High-level descriptions, combining features, or creating dependencies can lead to confusion and inefficiencies.

  15. Question 15

    Link to question

    Brian\'s team has identified several large epics that need to be broken down into smaller, actionable user stories. What approach should Brian take?

    1. Break down epics based on technical tasks only.

    2. Combine epics to create a single, large user story.

    3. Ignore the epics and focus on current tasks.

    4. Divide epics into smaller stories that each deliver specific, incremental value.

    Show answer and explanation

    Correct answer

    • Divide epics into smaller stories that each deliver specific, incremental value.

    Breaking down epics into smaller, actionable user stories that deliver specific, incremental value aligns with Agile principles of iterative development and continuous delivery. This approach ensures that each story is manageable, provides tangible progress, and can be completed within a sprint. Focusing solely on technical tasks or ignoring epics can hinder progress and value delivery.

  16. Question 16

    Link to question

    What is the primary purpose of using themes to organize and manage related user stories?

    1. To group unrelated tasks for convenience.

    2. To ensure user stories are delivered in a specific order.

    3. To create a logical structure that enhances understanding and management of related user stories.

    4. To avoid the need for epics and features.

    Show answer and explanation

    Correct answer

    • To create a logical structure that enhances understanding and management of related user stories.

    Themes provide a logical structure to organize and manage related user stories, making it easier to understand the context and purpose of each story. This approach enhances prioritization, tracking, and communication within the team. Grouping unrelated tasks or focusing solely on delivery order can create confusion and inefficiencies.

  17. Question 17

    Link to question

    Emma is working on ensuring that all user stories meet the Definition of Ready (DoR) before they enter a sprint. What should Emma include in the DoR criteria?

    1. High-level goals without specific details.

    2. Detailed acceptance criteria, clear requirements, and dependencies resolved.

    3. Vague descriptions that allow for flexibility.

    4. Only technical specifications.

    Show answer and explanation

    Correct answer

    • Detailed acceptance criteria, clear requirements, and dependencies resolved.

    The Definition of Ready (DoR) ensures that user stories are fully prepared for development. Including detailed acceptance criteria, clear requirements, and resolving dependencies ensures that stories are actionable and can be completed within a sprint. High-level goals, vague descriptions, or focusing solely on technical specifications can lead to misunderstandings and incomplete stories.

  18. Question 18

    Link to question

    What is the benefit of creating clear and testable acceptance criteria for user stories?

    1. It provides a flexible approach to development.

    2. It allows for interpretation and adjustment during development.

    3. It ensures that the team knows when a story is complete and meets the desired quality.

    4. It focuses on technical tasks only.

    Show answer and explanation

    Correct answer

    • It ensures that the team knows when a story is complete and meets the desired quality.

    Clear and testable acceptance criteria provide specific conditions that a user story must meet to be considered complete. This ensures that the story meets the desired quality and functionality, facilitating testing and validation. Flexible approaches, interpretation, or focusing solely on technical tasks can lead to incomplete or unsatisfactory deliverables.

  19. Question 19

    Link to question

    Tom is working on incorporating AI into Agile practices in his organization. What should Tom focus on to effectively integrate AI?

    1. Prioritizing AI development over all other tasks.

    2. Implementing AI without considering its impact on Agile processes.

    3. Avoiding AI until it's fully understood by the team.

    4. Using AI to enhance decision-making and automate repetitive tasks.

    Show answer and explanation

    Correct answer

    • Using AI to enhance decision-making and automate repetitive tasks.

    Integrating AI into Agile practices should enhance decision-making and automate repetitive tasks, thereby improving efficiency and effectiveness. Prioritizing AI over all other tasks, avoiding it, or implementing it without considering its impact can disrupt Agile processes and reduce overall productivity and value delivery.

  20. Question 20

    Link to question

    What should a Scrum Developer consider when ensuring user stories meet the Definition of Ready (DoR) before entering a sprint?

    1. That stories are independent, negotiable, valuable, estimable, small, and testable.

    2. That stories are detailed and fully defined without any room for discussion.

    3. That stories are vague to allow flexibility during the sprint.

    4. That stories are technically challenging to keep the team engaged.

    Show answer and explanation

    Correct answer

    • That stories are independent, negotiable, valuable, estimable, small, and testable.

    Ensuring user stories meet the Definition of Ready (DoR) involves confirming that stories are independent, negotiable, valuable, estimable, small, and testable (INVEST). This guarantees that the stories are ready for development, clear, and actionable. Fully defined stories without discussion, vague stories, or focusing solely on technical challenges can lead to misunderstandings and incomplete deliverables.

  21. Question 21

    Link to question

    Michael, a Scrum Developer, notices an increase in lead time for user stories in recent sprints. What action should Michael take to investigate and address this issue?

    1. Increase the size of the development team to handle more user stories simultaneously.

    2. Initiate a root cause analysis to identify factors contributing to the increased lead time.

    3. Implement stricter sprint review meetings to ensure timely completion of user stories.

    4. Adjust the Definition of Done (DoD) to include fewer criteria for user story completion.

    Show answer and explanation

    Correct answer

    • Initiate a root cause analysis to identify factors contributing to the increased lead time.

    Initiating a root cause analysis is essential to identify the underlying reasons behind increased lead time. This approach aligns with Agile principles of empirical process control, enabling the team to make informed decisions based on data and continuous feedback (Agile Alliance).

  22. Question 22

    Link to question

    Sarah, a Scrum Developer, notices that the team\'s velocity has significantly dropped over the past two sprints. She suspects it might be due to recent changes in the team composition. What should Sarah do first to address this issue?

    1. Conduct a retrospective meeting to discuss team dynamics and identify bottlenecks.

    2. Increase the sprint duration to allow more time for the team to adjust.

    3. Implement stricter sprint planning to enforce better time management.

    4. Request additional training for team members on Agile practices.

    Show answer and explanation

    Correct answer

    • Conduct a retrospective meeting to discuss team dynamics and identify bottlenecks.

    Conducting a retrospective meeting aligns with Agile principles of continuous improvement. It allows the team to reflect on recent changes and identify issues affecting velocity. This approach helps in addressing underlying problems collaboratively, which is crucial for maintaining and improving team performance (Agile Manifesto).

  23. Question 23

    Link to question

    Emily, a Scrum Developer, notices a significant amount of technical debt accumulating in the codebase. Which strategy should Emily adopt to manage technical debt effectively?

    1. Limit the number of sprint backlog items to minimize technical debt accumulation.

    2. Increase the number of acceptance criteria for user stories to reduce technical debt.

    3. Schedule regular refactoring sessions to address accumulated technical debt.

    4. Conduct additional user testing to mitigate the impact of technical debt.

    Show answer and explanation

    Correct answer

    • Schedule regular refactoring sessions to address accumulated technical debt.

    Regular refactoring sessions help in managing technical debt by improving code quality and reducing complexity over time. This practice aligns with Agile principles of sustainable development and continuous attention to technical excellence (Agile Manifesto).

  24. Question 24

    Link to question

    David, a Scrum Developer, is tasked with setting up a continuous delivery pipeline for the team\'s project. What should David prioritize when designing the pipeline?

    1. Increasing the frequency of production deployments to accelerate feedback cycles.

    2. Implementing manual checkpoints to ensure thorough validation before deployment.

    3. Minimizing the number of integration tests to speed up the deployment process.

    4. Automating build, test, and deployment processes to enable frequent releases.

    Show answer and explanation

    Correct answer

    • Automating build, test, and deployment processes to enable frequent releases.

    Prioritizing automation in the continuous delivery pipeline aligns with Agile practices of delivering working software frequently. Automated processes reduce human error, speed up deployment cycles, and enable rapid feedback, which is crucial for maintaining agility and responsiveness (Agile Alliance).

  25. Question 25

    Link to question

    Rachel, a Scrum Developer, is analyzing the team\'s cycle time and lead time metrics. What should Rachel consider when interpreting these metrics?

    1. Cycle time measures the total time taken to complete a user story, while lead time measures the time from request to delivery.

    2. Cycle time and lead time are interchangeable metrics that measure the same aspect of the development process.

    3. Cycle time measures the time taken to complete development tasks, while lead time measures team productivity.

    4. Cycle time and lead time are metrics used primarily for tracking project milestones and deadlines.

    Show answer and explanation

    Correct answer

    • Cycle time measures the total time taken to complete a user story, while lead time measures the time from request to delivery.

    Understanding the distinction between cycle time and lead time is crucial. Cycle time focuses on the time spent actively working on a task, while lead time includes waiting and process time. This knowledge helps teams accurately assess efficiency and optimize their workflow accordingly (Scrum Guide).

  26. Question 26

    Link to question

    John, a Scrum Developer, is tasked with assessing the team\'s Agile maturity. Which framework can John use to evaluate and improve Agile practices within the team?

    1. SAFe (Scaled Agile Framework)

    2. LeSS (Large-Scale Scrum)

    3. Kanban

    4. Scrum of Scrums

    Show answer and explanation

    Correct answer

    • LeSS (Large-Scale Scrum)

    LeSS is a framework specifically designed to scale Scrum across multiple teams, making it suitable for assessing and improving Agile maturity within larger organizations. It provides principles and practices to enhance collaboration, transparency, and value delivery, aligning with Agile values (LeSS Framework).

  27. Question 27

    Link to question

    Sophia, a Scrum Developer, notices that the team\'s Key Performance Indicators (KPIs) in Agile are not showing significant improvement over the last few sprints. What should Sophia prioritize to enhance the team\'s performance based on these metrics?

    1. Introduce additional reporting requirements to track individual team member contributions.

    2. Increase the frequency of daily stand-up meetings to improve communication.

    3. Review and adjust sprint goals to focus on achieving measurable outcomes.

    4. Implement stricter sprint planning to enforce adherence to timelines.

    Show answer and explanation

    Correct answer

    • Review and adjust sprint goals to focus on achieving measurable outcomes.

    Reviewing and adjusting sprint goals based on KPIs helps teams align their efforts with desired outcomes. It promotes transparency, adaptation, and continuous improvement, key principles of Agile methodologies (Agile Alliance).

  28. Question 28

    Link to question

    Mr. Thompson is a Scrum Developer in a software development team. During the sprint retrospective, the team identifies a recurring issue where the codebase becomes increasingly difficult to maintain due to accumulating technical debt. What action should Mr. Thompson prioritize?

    1. Increase the sprint duration to allow more time for refactoring

    2. Implement automated tests to prevent regression issues

    3. Conduct a root cause analysis to understand why technical debt accumulates

    4. Prioritize feature development over refactoring to meet sprint goals

    Show answer and explanation

    Correct answer

    • Conduct a root cause analysis to understand why technical debt accumulates

    Mr. Thompson should prioritize conducting a root cause analysis (Option C) to understand why technical debt accumulates. This approach aligns with Agile principles of continuous improvement and addresses the underlying issues causing technical debt. Agile practices emphasize identifying and addressing root causes to prevent recurring issues. Automated tests (Option B) are valuable but focus on preventing regression rather than addressing existing technical debt. Increasing sprint duration (Option A) contradicts Agile principles of timeboxing, and prioritizing feature development (Option D) without managing technical debt can lead to increased complexity and slower delivery in the long run.

  29. Question 29

    Link to question

    Ms. Roberts, a Scrum Developer, notices that the team\'s velocity has been fluctuating significantly over the past few sprints. What should she do to assess and stabilize the team\'s velocity?

    1. Increase the number of user stories in each sprint to normalize velocity

    2. Implement story point estimation for tasks to improve accuracy

    3. Analyze sprint retrospectives to identify factors impacting velocity

    4. Adjust the definition of done to reduce variability in task completion times

    Show answer and explanation

    Correct answer

    • Analyze sprint retrospectives to identify factors impacting velocity

    Ms. Roberts should analyze sprint retrospectives (Option C) to identify factors impacting velocity. Retrospectives provide insights into team dynamics, process bottlenecks, and external factors affecting performance, helping teams stabilize their velocity over time. Increasing user stories (Option A) can artificially inflate velocity without addressing underlying issues. Story point estimation (Option C) improves task estimation accuracy but does not directly stabilize velocity. Adjusting the definition of done (Option D) addresses task completion criteria but may not stabilize velocity unless underlying causes are identified and addressed.

  30. Question 30

    Link to question

    Mr. Garcia, a Scrum Developer, is part of a team that practices continuous delivery. He notices that the continuous integration pipeline occasionally fails due to conflicting code merges. What should Mr. Garcia suggest to improve the situation?

    1. Implement feature branching to isolate changes until ready for integration

    2. Increase the frequency of integration testing to catch conflicts earlier

    3. Use manual code reviews to identify and resolve merge conflicts

    4. Decrease the frequency of code merges to reduce pipeline failures

    Show answer and explanation

    Correct answer

    • Implement feature branching to isolate changes until ready for integration

    Mr. Garcia should suggest implementing feature branching (Option A) to isolate changes until they are ready for integration. Feature branching allows developers to work independently without disrupting the main codebase until changes are stable and ready for integration, reducing conflicts and pipeline failures. Increasing integration testing frequency (Option B) addresses detection but not prevention of conflicts. Manual code reviews (Option C) are valuable but may not prevent conflicts as effectively as feature branching. Decreasing merge frequency (Option D) conflicts with continuous delivery principles of frequent integration.

Read all flashcards

Recall the answer before opening each card.

What is the primary benefit of the Four Ls retrospective?

The Four Ls (Liked, Learned, Lacked, Longed for) provides a comprehensive view of the sprint, covering both positive and negative aspects and future desires, promoting deep learning and continuous improvement.

Which framework is designed to scale Scrum across multiple teams?

Nexus is the framework for scaling Scrum. It adds roles, events, and artifacts to coordinate multiple teams working on a single product increment.

How can Agile be justified for non-technical departments like finance?

Agile improves collaboration and transparency, which are universal needs. Its principles help teams respond to changes efficiently and align stakeholders, making it suitable for any domain.

What should be included in the Definition of Done in a regulated industry?

Regulatory compliance requirements should be embedded in the Definition of Done, ensuring every increment meets standards and regulations, not treated as an afterthought.

How can a marketing team adapt Scrum effectively?

Incorporate marketing-specific roles within the Scrum framework to address unique needs while maintaining Scrum structure. This bridges the gap between principles and domain work.

What is the most relevant case study for extending Agile to HR?

A case study on Agile transformation in HR provides context-specific insights into applying principles to HR processes, illustrating benefits and challenges.

How should patient privacy regulations be handled in healthcare Scrum projects?

Regular reviews by legal and compliance experts throughout the project ensure ongoing adherence to regulations, integrated into the Agile process.

What action aligns with Kaizen principles?

Encouraging small, incremental changes regularly that involve the entire team. Kaizen is about continuous improvement through frequent, minor adjustments.

Which Scrum pattern helps identify recurring issues?

The Retrospective pattern. It is designed to reflect on past sprints to identify and address recurring problems, fostering continuous improvement.

How should AI ethics be prioritized in task prioritization?

Consider the potential ethical impact of each task alongside technical and business priorities. Agile decision-making must balance ethical implications to avoid harm.

What tool helps integrate Agile and Waterfall in a hybrid project?

A unified project management tool that accommodates both methodologies provides visibility, collaboration, and tracking across different approaches.

What is the primary purpose of using themes in user story management?

Themes create a logical structure to organize and manage related user stories, enhancing understanding, prioritization, and communication.

What must user stories satisfy to be considered ready for a sprint?

The Definition of Ready requires detailed acceptance criteria, clear requirements, and resolved dependencies, ensuring stories are actionable and can be completed in a sprint.

What is the benefit of clear and testable acceptance criteria?

They provide specific conditions that must be met for a story to be complete, ensuring quality and facilitating testing. The team knows exactly when the story is done.

How should AI be integrated into Agile practices?

Use AI to enhance decision-making and automate repetitive tasks, improving efficiency without disrupting Agile processes.

What is a key step when lead time increases?

Initiate a root cause analysis to identify factors contributing to the increase. This aligns with empirical process control and continuous feedback.

What is the first action when team velocity drops?

Conduct a retrospective meeting to discuss team dynamics and identify bottlenecks. This aligns with continuous improvement and collaborative problem-solving.

How do you manage accumulating technical debt?

Schedule regular refactoring sessions to address technical debt. This improves code quality and aligns with sustainable development and technical excellence.

What should be prioritized when designing a continuous delivery pipeline?

Automating build, test, and deployment processes to enable frequent releases. Automation reduces errors and speeds up feedback.

How do cycle time and lead time differ?

Cycle time is the time actively spent working on a task from start to finish. Lead time includes waiting and process time from request to delivery. Both help assess efficiency.

Active recall deck

Practice Scrum Developer Professional Certification Exam with real flashcards

Read the prompt, commit to an answer, then flip the card. Move through the deck at your own pace and repeat any topic that does not come back quickly.

20 free cards

Card 1 of 20

1 reviewed this session

Connect the concepts

Your Scrum Developer Professional Certification Exam study mind map

Open a branch to connect a topic with its practice questions and explanations. Use the map to choose your next review topic.

Scrum Developer Professional Certification Exam30 questions in this practice set
Practice focus 1(1)
Practice focus 2(1)
Practice focus 3(1)
Practice focus 4(1)
Practice focus 5(1)
Practice focus 6(1)
Practice focus 7(1)
Practice focus 8(1)
Practice focus 9(1)
Practice focus 10(1)
Practice focus 11(1)
Practice focus 12(1)
More practice connections(18)
Exam-focused analysis

What this Scrum Developer Professional Certification Exam practice set measures

This is an analysis of the practice bank, not a claim about the vendor's live exam blueprint. Use it to identify the knowledge, judgment, and recall patterns exercised here, then verify your coverage against the current official exam guide.

Scrum Ceremonies and Continuous Improvement

Effective retrospectives are the engine for team learning and improvement. The practice bank highlights the Four Ls (Liked, Learned, Lacked, Longed for) as a comprehensive technique that surfaces insights beyond simple start-stop-continue. It also emphasizes Kaizen principles—small, incremental changes involving the whole team—and the Retrospective pattern for addressing recurring issues. When velocity drops or technical debt accumulates, a retrospective is the first step to root cause analysis and collaborative problem-solving. These ceremonies are timeboxed and must yield actionable improvements.

  • Use the Four Ls retrospective to uncover deep insights and drive adaptation.
  • Apply Kaizen through regular, small improvements rather than large overhauls.
  • Always investigate root causes when performance metrics decline; retrospectives are the primary forum.

Adapting Scrum to Different Contexts

Scrum is not limited to software development. The practice bank shows how to apply Agile principles in finance, marketing, HR, and healthcare. Key adaptations include incorporating domain-specific roles, integrating regulatory compliance into the Definition of Done, and using case studies from similar domains to guide transformation. In hybrid environments, a unified project management tool bridges Agile and Waterfall. Scaling across multiple teams is addressed by the Nexus framework, which adds roles and events for coordination. When incorporating AI, prioritize ethical impact alongside technical and business value.

  • In regulated industries, embed compliance checks into the Definition of Done.
  • For non-IT teams, tailor roles (e.g., marketing roles) while preserving Scrum cadences.
  • Use Nexus to scale Scrum; use LeSS for assessing Agile maturity in larger organizations.

User Stories, Backlog Management, and Definition of Ready

High-quality user stories follow the INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable). Epics are broken into smaller stories that each deliver incremental value. Themes organize related stories to provide context. The Definition of Ready (DoR) ensures stories have detailed acceptance criteria, clear requirements, and resolved dependencies before entering a sprint. Clear and testable acceptance criteria confirm completeness and quality. Proper backlog management prevents misunderstandings and enables smooth sprint planning.

  • Always validate stories against INVEST before acceptance into a sprint.
  • Break epics into small, value-delivering stories; use themes for grouping.
  • Define DoR with explicit acceptance criteria and dependency resolution.

Metrics, Technical Debt, and Process Improvement

Metrics like velocity, cycle time, and lead time reveal team performance. Cycle time measures active work; lead time includes waiting. Fluctuating velocity or increasing lead time requires root cause analysis via retrospectives. Technical debt is managed through regular refactoring and fixing root causes, not by ignoring it. Continuous delivery pipelines should automate build, test, and deployment. When conflicts cause pipeline failures, feature branching isolates changes until stable. KPIs improve by adjusting sprint goals to focus on measurable outcomes. LeSS helps evaluate Agile maturity.

  • Differentiate cycle time (work time) from lead time (total time); both inform efficiency.
  • Schedule regular refactoring sessions to reduce technical debt sustainably.
  • Use feature branching to prevent integration conflicts; automate CI/CD for frequent releases.

Study workflow

Turn one Scrum Developer Professional Certification Exam attempt into a study plan

  1. 1

    Run an Effective Retrospective

    Use the Four Ls format. Ask each team member to list what they Liked, Learned, Lacked, and Longed for. Group similar items, vote on the most impactful, and create one or two actionable improvement experiments for the next sprint. Ensure the discussion is blameless and focuses on processes.

  2. 2

    Integrate Regulatory Compliance into Agile

    Collaborate with legal and compliance experts to add regulatory requirements to your Definition of Done. Include acceptance criteria that validate compliance. Schedule regular reviews with experts to check adherence, and treat compliance as a non-functional requirement that must be met each sprint.

  3. 3

    Decompose Epics into Actionable Stories

    Start with the epic's high-level goal. Brainstorm user journeys, then slice into small stories that each deliver specific, incremental business value. Ensure each story meets INVEST criteria. Use vertical slicing (end-to-end functionality) rather than horizontal (technical layers) to enable early feedback.

  4. 4

    Manage Technical Debt Proactively

    In each sprint, allocate a fixed percentage of capacity (e.g., 20%) to refactoring. When a team member identifies technical debt, capture it as a technical story in the backlog. Use root cause analysis in retrospectives to address systemic causes, and prioritize debt based on impact on future velocity.

  5. 5

    Stabilize Fluctuating Velocity

    First, gather data from the past three sprints: velocity, team composition, scope changes, and external interruptions. Present these in the retrospective. Facilitate a discussion to identify patterns (e.g., inexperienced members, unclear requirements). Create experiments like pair programming, reducing WIP, or refining estimation practices.

FAQ

Questions about this exam practice page

Clear boundaries on what the bank covers, how to use it, and where official vendor information still matters.

What is the difference between cycle time and lead time in Scrum?+

Cycle time measures the time spent actively working on a user story from start to finish. Lead time measures the total time from when the story is requested until it is delivered, including waiting periods. Both metrics help identify bottlenecks and improve workflow efficiency.

How does Nexus help scale Scrum across multiple teams?+

Nexus extends Scrum for multi-team development by adding a Nexus Sprint Goal, a Nexus Integration Team, and the Nexus Daily Scrum. It emphasizes cross-team coordination, dependency management, and continuous integration to ensure all teams collaborate toward a single product increment.

What does the INVEST criteria stand for in user stories?+

INVEST stands for Independent, Negotiable, Valuable, Estimable, Small, and Testable. These criteria ensure user stories are well-formed, clear, and ready for development. Independent stories reduce dependencies, Negotiable allows collaboration, Valuable delivers business value, Estimable enables planning, Small fits in a sprint, and Testable confirms completion.

How should a Scrum team incorporate Kaizen principles?+

Kaizen, or continuous improvement, is implemented by encouraging small, incremental changes regularly. The entire team participates in identifying improvements, often through retrospectives. Each improvement is tested in the next sprint, and successful changes become part of the standard process.

What is the difference between cycle time and lead time? (FAQ redundancy avoided – adjusted) Can you define the Definition of Ready?+

Definition of Ready (DoR) is a set of criteria that a user story must meet before it can be accepted into a sprint. Typical DoR includes detailed acceptance criteria, clear requirements, dependencies resolved, and the story is INVEST-compliant. It ensures the team can begin work with minimal ambiguity.

Keep studying

Build the next review session

Browse another free bank or use the study strategy guide to turn your misses into spaced review.

All free testsStudy strategy