Eight Scrum habits that cost points on a Scrum Master assessment
Experience can work against you on a Scrum Master assessment. Your team runs Scrum a certain way, and the questions are written against the 2020 Scrum Guide, which is shorter and stricter than most teams. I wrote 200 practice questions using nothing but that guide, and these are the habits that cost points over and over. Every quote below is from The 2020 Scrum Guide by Ken Schwaber and Jeff…
The Scrum Master assessment can cost you valuable points due to certain habits that are not aligned with the 2020 Scrum Guide. This guide, authored by Ken Schwaber and Jeff Sutherland, outlines specific practices that are crucial for passing the assessment. According to the guide, the Daily Scrum, a 15-minute event for the Developers of the Scrum Team, is exclusively for Developers.
Product Owners and Scrum Masters should only participate when they are actively working on Sprint Backlog items. The use of the term "Development Team" in the 2020 guide has been replaced with "Scrum Team," which consists of a Scrum Master, a Product Owner, and Developers without any sub-teams or hierarchies. Furthermore, the guide introduces commitments as a new addition, with each artifact - Product Backlog, Sprint Backlog, and Increment - having its own commitment: Product Goal, Sprint Goal, and Definition of Done, respectively.
It's important to note that the guide does not mention velocity, story points, or user stories, so answers suggesting their necessity are incorrect. The 2020 guide also emphasizes that Refinement is an ongoing activity, not an event, and the Sprint Review is not a gate to releasing value. The timeboxes for each event vary based on the Sprint length, and only the Product Owner has the authority to cancel a Sprint.
By reviewing the 2020 Scrum Guide thoroughly, you can avoid falling into these traps and improve your chances of success on the Scrum Master assessment.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
