Every Tuesday we'll give you three challenging Scrum Mastery questions. The following Monday I 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!
Are you ready?
Which of the following do not contribute to the Scrum value of focus. Pick all that apply.
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.
At the end of the Sprint there are incomplete Product Backlog items still on the Sprint Backlog. What should be done with this them? Choose the two best answers.
Any incomplete Product Backlog items are worked on first in the next Sprint, before the Development Team works on any new Product Backlog items in the current Sprint.
Incomplete Product Backlog items at the end of a Sprint go back on the Product Backlog. The Product Owner will decide if they still have value and where they should be ordered in the Product Backlog.
Any incomplete Product Backlog items should be discussed at the Sprint Review, making transparent what was "Done" and not "Done" during the Sprint.
The Scrum Master should move the incomplete Product Backlog items and any associated work into the next Sprint, placing the undone items at the top f the Sprint Backlog.
The Sprint should be extended so the Development Team can finish what they committed to.
Scrum is best suited for simple, repeatable efforts where requirements are fully known, documented and discussed upfront and before a Sprint begins.