SWE Sprint Review Mock Quiz -1

A digital illustration of a diverse group of Scrum team members collaborating in a modern office environment, with Scrum boards and sticky notes in the background, emphasizing teamwork and agility.

SWE Sprint Review Mock Quiz

Test your knowledge of Scrum principles and practices with our engaging SWE Sprint Review Mock Quiz! This quiz is designed for Scrum Masters, Product Owners, and Development Teams looking to deepen their understanding of the Scrum framework.

Key features:

  • Multiple choice and checkbox questions
  • Real-life scenarios for practical learning
  • Instant feedback on your answers
  • Learn and improve your Scrum game!
13 Questions3 MinutesCreated by EngagingScrumMaster12
The Product Owner wants to create estimations and ask the Scrum Master for guidance about it. What is the most proper guideline that the Scrum Master should give?
Product Owner should use ideal days to get estimations.
There is no estimation in Scrum.
Development Team must create estimations.
Product Owner should use story points to get estimations.
In order to start the first Sprint, Scrum only requires a Product Owner with enough ideas, a Development Team to execute on those ideas, and a Scrum Master to guide the process
True
False
Which are three reasons why to include tests in the Definition of “Done” is a good practice?
Because adds transparency to final increments.
Because the results are likely to be releasable.
Because it can simplify requirement definitions
Because progress will be easier to show in burndown charts
At the end of the eighth Sprint, the internal sponsors are upset and angry with the progress of the product being built. The current state of the product is not as expected and will require additional Sprints and more budget than originally anticipated at the start of the project. What factors may have led to this? (Choose three.)
The Product Owner has not been engaging with sponsors frequently enough and has not been kept aware of the overall progress of the project.
The sponsors haven’t been using the Sprint Reviews to actively engage, and inspect and evaluate progress
The scope changes have not been tracked adequately and the change request process has not been followed properly
The stakeholders have not been using the Daily Scrum effectively to track the Development Team’s progress
The Scrum Master has not ensured transparency.
The project plan proposed to the sponsors at the start of the project followed stringently.
A Development Team has a total of six members, 4 members who work full time in the office and 2 members who work part time at home. The Development Team is complaining that it is too difficult to synchronize every day and has suggested having the Daily Scrum every other day instead. What would be three key concerns if the Daily Scrum is held less frequently? (Choose three.)
The Product Owner cannot accurately inspect utilization of the individual team members.
The Scrum Master loses the ability to update the burndown chart adequately.
Impediments are raised and resolved more slowly.
Less information about the progress will be shared causing the Sprint plan to become inaccurate and reducing transparency over progress toward the Sprint Goal.
Opportunities to inspect and adapt the Sprint Backlog are reduced.
Steven, who is a Scrum Master, on one of the Scrum Teams has approached you asking for advice. Their Daily Scrum requires more than 15 minutes and the team has suggested dividing themselves into two separate teams in order to stay within the time box. As another Scrum Master, what would be the best response?
Agree - this is an appropriate solution to the problem.
Unsure - dividing a team into two cannot be decided based on this information. You offer to observe.
Disagree - as the root cause may not be that the team is too big.
Agree - You agree that dividing the team into two is a good strategy to allow the teams to learn how to run Daily Scrums quickly and effectively. Once they’ve learned to limit the Daily Scrum to 15 minutes, you can merge the teams again.
During the Sprint Retrospective, the team is discussing the quality issues that prevented the team from delivering a releasable Increment at the end of the Sprint. The Development Team does, however, mention that they were able to achieve a high velocity. What are the best two responses for Steven, their Scrum Master, to take? (Choose two.)
Stress the value of working software over measured velocity.
Agree and acknowledge the Development Team’s hard work, so they will be motivated to do even more in the next Sprint
Facilitate a discussion on how to improve the quality to a level high enough for the Increment to be releasable, even if the measured velocity drops in the next Sprint.
Acknowledge the hard work but remind the Development Team that they need to improve in order to do even more in the next Sprint.
You have a Scrum Team that has been working together for over a year. The Development Team consists of eleven members who rarely collaborate and work within their functional boundaries. There are no Sprint Goals and most of the items in the Sprint Backlog are unrelated. The Scrum Team has concluded that it is not possible to create Sprint Goals based on the items in the Product Backlog. What might explain why the Scrum Team is finding it difficult to craft Sprint Goals? (Choose all that apply.)
The Sprints are too long.
The Development Team is too big.
Scrum might not be the best framework for this team
The Product Owner is not empowered to make decisions about items in the Product Backlog nor how they are ordered.
The Product Owner doesn’t set objectives that he/she wants to achieve with upcoming Sprints
Which are two good approaches for the Development Team to make non-functional requirements visible?
Add them to the acceptance criteria as part of the definition of "Done".
QA must run integration and regression tests before the end of the Sprint.
Create and special Product Backlog only for these requirements.
Add them to the Product Backlog and keep the Product Owner informed of the estimated effort.
During the Sprint Review of a scaled development effort, each Scrum Team should demonstrate its individual Increment in a separate branch of the code
True
False
Steven is a Scrum Master for three Scrum Teams building the same product and working from the same Product Backlog. Management wants to standardize how velocity is calculated across all three teams in order to identify which teams are high performing and which teams need more support. What would be the best two responses Steven could provide to management? (Choose two.)
Providing incentives based on velocity can increase the Scrum Team’s motivation to produce more value
There is no direct relationship between velocity and value
Velocity is the amount of business functionality that a Scrum Team creates in a Sprint. It is unique to that team and used as an input to Sprint Planning.
Standardizing velocity across teams is a good way to understand which teams are producing the most value
Development Team asks their Product Owner to re-order the Product Backlog. The team is waiting for an external supplier to deliver a specific software component. Without that component there won’t be enough work in the next Sprint to occupy the full team. The Product Owner asks the Scrum Master for help. What would be good advice to give the Product Owner?
Remind the Product Owner that his primary concern is the flow of value reflected in the ordering of the Product Backlog.
Tell the Product Owner to re-order the Product Backlog so the work involving the external component can be planned in a separate sprint
Tell the Product Owner that the Product Backlog should be ordered to maximize utilization of the Development Team
At the fifth Sprint Retrospective, the Product Owner mentions that he is surprised about the amount of technical debt that has built up in the system and that the product is not able to support an adequate number of users. Peter, the Product Owner, is upset that the product will need several more Sprints to address the scalability issues in order to meet his expectations. What factors may have led to this?
The Scrum Team has not used the past Sprint Retrospectives effectively to inspect and adapt
The Development Team has not been paying enough attention to technical quality
The Development Team and the Product Owner are not having conversations around technical debt
The Scrum Master has not ensured that the Scrum Team is transparent.
All of the above.
None of the above.
{"name":"SWE Sprint Review Mock Quiz -1", "url":"https://www.quiz-maker.com/QPREVIEW","txt":"Test your knowledge of Scrum principles and practices with our engaging SWE Sprint Review Mock Quiz! This quiz is designed for Scrum Masters, Product Owners, and Development Teams looking to deepen their understanding of the Scrum framework.Key features:Multiple choice and checkbox questionsReal-life scenarios for practical learningInstant feedback on your answersLearn and improve your Scrum game!","img":"https:/images/course2.png"}
Powered by: Quiz Maker