Intermediate Agile & Scrum test (Intermediate)

Sample questions

5 sample questions from the Intermediate Agile & Scrum test, with the answers. Samples are taken out of the live test, so you will not meet these when you sit it.

1. Which of the following statements best describes the difference between cycle time and lead time in the context of Kanban, and when each is more relevant to measure?

   1. Cycle time is the time from when a request is made to when it is delivered, while lead time is the time from when work starts to when it is done. Cycle time is more relevant for measuring the efficiency of the team's workflow, while lead time is more relevant for measuring the time it takes to deliver value to the customer.
   2. Cycle time is the time from when work starts to when it is done, while lead time is the time from when a request is made to when it is delivered. Both cycle time and lead time are equally relevant for measuring the efficiency of the team's workflow.
   3. Cycle time is the time from when work starts to when it is done, while lead time is the time from when a request is made to when it is delivered. Cycle time is more relevant for measuring the efficiency of the team's workflow, while lead time is more relevant for measuring the time it takes to deliver value to the customer.
   4. Cycle time is the time from when work starts to when it is done, while lead time is the time from when a request is made to when it is delivered. Cycle time is more relevant for measuring the time it takes to deliver value to the customer, while lead time is more relevant for measuring the efficiency of the team's workflow.

   Answer: C. Cycle time is the time from when work starts to when it is done, while lead time is the time from when a request is made to when it is delivered. Cycle time is more relevant for measuring the efficiency of the team's workflow, while lead time is more relevant for measuring the time it takes to deliver value to the customer.

   Cycle time measures the time an item spends in progress, which is useful for understanding workflow efficiency. Lead time measures the total time from request to delivery, which is more relevant for customer satisfaction. The distinction helps in choosing the right metric based on the goal of the team.

2. Which of the following best describes the difference in how Agile and Waterfall models handle changes in requirements during a project?

   1. Agile is more suitable for projects with stable requirements, while Waterfall is better for projects with evolving requirements.
   2. Agile and Waterfall have the same approach to handling changes in requirements during a project.
   3. Waterfall allows for changes in requirements during the project, while Agile requires all requirements to be fixed upfront.
   4. Agile allows for changes in requirements during the project, while Waterfall requires all requirements to be fixed upfront.

   Answer: D. Agile allows for changes in requirements during the project, while Waterfall requires all requirements to be fixed upfront.

   Agile methodologies, such as Scrum and Kanban, emphasize flexibility and adaptability, allowing for changes in requirements throughout the project. In contrast, the Waterfall model is a linear, sequential approach where all requirements are defined and fixed before development begins. This makes Agile more suitable for projects with evolving requirements, while Waterfall is better suited for projects with stable, well-understood requirements.

3. What is the difference between the Definition of Done for performance testing and the Definition of Done for code quality, and in what scenarios would each be used?

   1. The Definition of Done for performance testing is the same as the Definition of Done for code quality.
   2. The Definition of Done for performance testing is less rigorous than the Definition of Done for code quality.
   3. The Definition of Done for performance testing is not required in agile projects.
   4. The Definition of Done for performance testing ensures that all performance criteria are met before an item is considered done, while the Definition of Done for code quality ensures that the code meets quality standards. The former is used when performance is a critical requirement, while the latter is used when code quality is the primary focus.

   Answer: D. The Definition of Done for performance testing ensures that all performance criteria are met before an item is considered done, while the Definition of Done for code quality ensures that the code meets quality standards. The former is used when performance is a critical requirement, while the latter is used when code quality is the primary focus.

   The Definition of Done for performance testing is specifically focused on ensuring that performance-related requirements are met, such as response times, scalability, and system stability. This is crucial in scenarios where performance is a key success factor, such as in high-traffic applications or mission-critical systems. On the other hand, the Definition of Done for code quality ensures that the code adheres to best practices, is well-documented, and passes all relevant code reviews and static analysis tools. The choice between the two depends on the context and priorities of the project, with performance being prioritized when it directly impacts user experience or system reliability.

4. Which of the following best represents the Definition of Done for user acceptance, including performance and complexity aspects?

   1. The user story has been decomposed into smaller tasks.
   2. The feature is integrated into the main branch and passes CI checks.
   3. Code is reviewed and passes unit tests.
   4. User acceptance criteria are met, including performance and usability requirements.

   Answer: D. User acceptance criteria are met, including performance and usability requirements.

   The Definition of Done (DoD) includes user acceptance criteria, ensuring that the product meets performance, usability, and other functional requirements. This is a critical part of the DoD, as it guarantees that the work is complete and acceptable to the user. Other options focus on internal aspects like code quality or testing, which are also part of the DoD but not the specific angle of user acceptance.

5. Which of the following statements correctly describes how the Sprint Goal is set in Scrum?

   1. The Sprint Goal is set during the Sprint Review and is used to evaluate the sprint's success.
   2. The Sprint Goal is set during the Daily Scrum and is based on the team's current workload.
   3. The Sprint Goal is determined by the Product Owner and is not visible to the Scrum Team.
   4. The Sprint Goal is set during Sprint Planning and is a commitment for the Sprint Backlog.

   Answer: D. The Sprint Goal is set during Sprint Planning and is a commitment for the Sprint Backlog.

   The Sprint Goal is established during Sprint Planning and serves as the commitment for the Sprint Backlog. It provides a unifying purpose for the Scrum Team and helps guide their work during the sprint. The other options are incorrect because they either misrepresent the timing or the purpose of the Sprint Goal.