Scrum Mastery Quiz Part 1
Scrum Mastery Quiz Part 1
Test your knowledge and skills as a Scrum Master with this comprehensive quiz! This quiz covers essential aspects of Scrum methodology and practices, challenging you on real-world scenarios and concepts.
Key Features:
- 10 carefully crafted questions
- Multiple choice and checkbox formats
- Designed for aspiring and current Scrum Masters
You are the Scrum Master for a Scrum Team that has been together for 3 months. Several of the Development Team members approach you after the Daily Scrum and mention that they are frustrated with one developer and ask you to act. They complain that they are having a hard time getting timely updates from her, because she either fails to show up to the Daily Scrum several days a week, and when she does is writing software on her laptop. As Scrum Master, what is the next best action to take?
Take over facilitation of the Daily Scrum, require everyone to close their computers for 15 minutes, and call on her for a status. Advise anyone who is not going to be in attendance that it is mandatory to email updates to the Scrum Master right by the start of the Daily Scrum.
Meet with the developer before the next Daily Scrum and respectfully yet firmly ask for her participation. Try to find out why she isn't participating and teach her why it is important for the Development Team to get timely updates on progress towards and impediments blocking the Sprint Goal.
Coach the Development Team members to resolve this situation directly with their teammate. Remind them about Scrum values, and to use courage, openness and respect when discussing the situation with her. In the near future facilitate team building exercises to build up trust within the team.
Schedule a meeting with the developer and her manager to escalate the situation, because the lack of communication and collaboration has turned into an impediment. If the situation does not improve in the next Sprint, ask her manager to have her removed from the Scrum Team.
Who creates the Sprint Goal, and when is the Sprint Goal created?
The Product Owner creates the Sprint Goals ahead of Sprint Planning and shares it with the Development Team in Sprint Planning.
The Product Owner determines and creates the Sprint Goal in Sprint Planning and shares it with the Scrum Team in Sprint Planning.
The Scrum Team collaboratively works together to create the Sprint Goal in Sprint Planning.
The Product Owner collaborates with the Development Team to create the Sprint Goal in Product Backlog refinement.
Choose the one best answer which describes velocity.
Velocity is an indication of the number of story points completed during the Sprint by the Development Team, on average, and tracked by the Scrum Master, generally for use in Sprint Planning to determine how many points the Development Team should commit to.
Velocity measures the productivity and the amount of value delivered by the Scrum Team, on average, every Sprint.
Velocity is an an optional, but often used, indication of the average amount of Product Backlog turned into an Increment of product during a Sprint by a Scrum Team, tracked by the Development Team for use within the Scrum Team.
Velocity is an indication of the average number of task hours completed during the Sprint by the Development Team for use within the Scrum Team.
Your Scrum Team has taken over the ongoing support and enhancements of a software product developed by a third-party company, which was turned over to your Scrum Team 6 weeks ago. After three Sprints of working on new enhancements, the Development Team has discovered a large amount of technical debt, which is making it a challenge to complete a “Done” Increment each Sprint. What is the best option going forward?
Since Product Owners have no accountability for technical debt, the Development Team should keep a list of all technical debt in their own special Development Backlog, and every Sprint they should work to clean up the technical debt and make that work transparent in the Sprint Backlog.
The Development Team should collaborate with the Product Owner to make all the technical debt transparent on the Product Backlog. The Scrum Team should also form a working agreement to focus a small amount of their capacity each Sprint to remove and repay technical debt, until the Scrum Team agrees it is under control.
The Product Owner should stop all new product enhancements immediately after the current Sprint. The lead developer should work with the Product Owner to quantify and set priority on the technical debt. The Development Team should then remove all the technical debt in hardening Sprints, before proceeding with any new enhancements.
The Scrum Master should break the Development Team into two teams. The Scrum Master should then assign one Development Team to focus on technical debt and have the other Development Team focus on working with the Product Owner to build new enhancements.
Which of the following may be inputs into Sprint Planning? Select all vapid answers that apply.
Product Backlog
Past performance of Development Team (e.g. velocity, throughput)
Product Increment
Projected Capacity of Development Team
Sprint Goal
Definition of "Done"
Definition of "Ready"
The Scrum Team has had a challenging Sprint and will not be able to meet their Sprint Goal. Two members were unexpectedly out sick, the Product Owner was in training for the last 3 days of the Sprint and has not been able to provide feedback, and test environments were down for a good portion of the Sprint, hence the Development Team could not finish a lot of testing. The day before the Sprint Review and Sprint Retrospective, the Development Team pushes hard to cancel these two events. As Scrum Master what do you do?
1. Since only a Product Owner may cancel a Sprint Review, work with her to cancel the Sprint to avoid wasting the stakeholders time.
2. Suggest the Sprint be extended by two or three days to give the Development Team time to finish testing and to get feedback from the Product Owner,
3. Cancel the Sprint Review because there isn't anything to demo but keep the Sprint Retrospective because there are some important topics to discuss and improve upon next Sprint.
4. Uphold Scrum by not cancelling these events and help the Development Team understand the benefits of being transparent and for the need to collaborate with stakeholders on the upcoming Sprint. Help the developers understand that the Sprint Retrospective is needed to inspect what happened and to improve next Sprint
Which of the following are Scrum values? Pick all that apply.
Commitment
Working software over comprehensive documentation
Respect
Focus
Responding to change over following a plan
Simplicity
Courage
Which of the following are not part of Scrum?
Sprint 0
User Stories
Story Points
Acceptance Criteria
UAT
None of the Above
If 5 Scrum Teams are working on the same product Increment, which of the following would be true
There will be 5 Sprint Backlogs. In other words, each Development Team will create, update and be responsible for their own Sprint Backlog.
There will be one Product Owner and one Product Backlog for all 5 teams.
Not every Team has to have the same Sprint length. One Team may choose 1-week Sprints, another 3-week Sprints.
All 5 Development teams will use one common definition of "Done", although some of these teams may extend their definition of "Done" to be more rigorous.
All of the Above
Which of the following do not contribute to the Scrum value of focus?
The Development Team decides to implement work-in-progress (WIP) limits on their Sprint's Kanban board (sometimes referred to as a Story Board or Task Board).
Scrum event time-boxes.
The Scrum Master assigns just enough work to the Development Team so that they can work at a sustainable pace.
The Sprint Goal.
Assigning Development Team members to more than one team or project at a time.
{"name":"Scrum Mastery Quiz Part 1", "url":"https://www.quiz-maker.com/QPREVIEW","txt":"Test your knowledge and skills as a Scrum Master with this comprehensive quiz! This quiz covers essential aspects of Scrum methodology and practices, challenging you on real-world scenarios and concepts.Key Features:10 carefully crafted questionsMultiple choice and checkbox formatsDesigned for aspiring and current Scrum Masters","img":"https:/images/course4.png"}