The Scrum Mastery Challenge - Quiz #3
Updated: Aug 6, 2019
Every Tuesday we'll give you three challenging Scrum Mastery questions. The following week I will share the answers with you in a new blog post, or you can get the answers by adding your email to my mailing list in the Contacts section at the bottom of the page.
If you are feeling courageous, add your answers in the comment section of this blog.
My advice is to read each question thoroughly, and time-box each question to four minutes. To challenge yourself, keep the Scrum Guide and other browser windows closed. Have fun with the quiz, I hope this helps you learn and to be a better Scrum Master!
This week our questions are slightly easier than last week's. Anyone have a perfect score so far?
The #no-estimates movement has taken off in your IT department, with four other Scrum Teams having done away with estimating Product Backlog items recently. Your Development Team brings this up in the Sprint Retrospective as a way to save time and make Product Backlog refinement go smoother. What may be the most likely outcomes for a Scrum Team not estimating Product Backlog items (pick two)?
The Product Owner may have difficulty forecasting likely target and delivery dates, and some transparency will be lost.
Management of the organization requires Scrum Teams to report velocity each Sprint, which may result in a loss of transparency and the inability to understand how much customer value is being delivered each Sprint.
During Sprint Planning, the Development Team may have difficulty forecasting what can be developed during the Sprint. Due to the loss of transparency, it may be challenging to understand if some Product Backlog items may be too large to complete within a Sprint.
The Scrum Team can get started with delivering value much earlier, rather than spending several weeks of upfront effort to estimate the entire Product Backlog.
When may a Scrum Team release a product Increment to production? Select the best answer(s).
As often as the Scrum Team has a done increment that the Product Owner wants to release. Released Increments must meet the Definition of "Done".
Only at the end of the Sprint, once the stakeholders provide the Product Owner with approval at the Sprint Review.
Releases usually happen in between Sprints, after the Sprint Review but before Sprint Planning.
As soon as the testing team finishes and signs off on testing, the Scrum Master works with the Product Owner to set a production release date.
How are non-functional requirements (NFRs) such as security, performance and availability handled in Scrum? Choose the one best answer.
NFRs may be described in the Product Backlog.
NFRs may be described as Acceptance Criteria
NFRs may be described as part of the definition of "Done"
All of the above