Scrum Artifacts Simulation

Correct Answer: Explain that in the revised Scrum Guide, every member contributing to the Sprint goal is considered a Developer, emphasizing collaboration over individual roles.

The Scrum Guide's update simplifies roles within the Scrum Team to encourage flexibility and cross-functionality, referring to all members working towards the Sprint goal as 'Developers', regardless of their specific tasks. This is meant to enhance collaboration and efficiency. The wrong answers propose steps that either contradict Scrum principles by reinforcing rigid roles and hierarchies or misinterpret the intention behind the terminology change, moving away from the Scrum Guide's emphasis on flexibility and cross-functionality.

Correct Answer: Explain that in Scrum, delivery dates are based on the team's progress and past velocity, making it a forecast rather than a fixed date.

In Scrum, delivery dates are not fixed but are forecasts based on the team's velocity and progress. The Scrum Master should educate stakeholders about the empirical nature of Scrum, where decisions are made based on what is known, which includes past performance (velocity). Other methods such as committing to work in a Sprint Planning for a fixed date, basing assumptions on the product backlog, or adjusting the definition of 'Done' can mislead or put undue pressure on the team, leading to a decrease in quality or unfinished work.

Correct Answer: Coach the team member on the purpose and structure of the Daily Scrum and remind them to stick to it.

The correct course of action for a Scrum Master when a team member consistently exceeds the time box during the Daily Scrum is to coach them on the purpose and structure of the Daily Scrum, emphasizing the importance of sticking to its time box to maintain its effectiveness. The wrong answers, while related to managing time and communication within a team, either introduce unnecessary complexity (assigning a rotating 'timekeeper' role), misinterpret the purpose of the Daily Scrum (organizing separate technical meetings), or suggest a solution that could bypass the value of face-to-face communication (using a digital tool for progress reporting).