Basic Scrum Concepts

A high variance in the sizes of tasks can cause a significant fluctuation on the burn-down chart. Bigger tasks will make the progress slowed down when they are being worked on, while smaller tasks will make the progress seem faster when they are being completed. The other responses in the answers are not necessarily correct: - 'The Scrum Master does not accurately report the team's progress.': A Scrum Master is a facilitator and has the responsibility to ensure that the team's progress is accurately reflected in the burn-down chart. But this does not explain the fluctuations in the chart - 'Product Owner is changing requirements daily.': While changes in requirements can cause fluctuations in a burn-down chart, in Scrum, the Product Owner should not change the requirements during a sprint. The sprint backlog is supposed to be fixed during a sprint - 'Team members are not focusing on the sprint goal.': If team members were not focusing on the sprint goal, the burn-down chart would likely be flat or trending upwards, not fluctuating Therefore, the most likely cause of a fluctuating burn-down chart is that the size of the tasks varies a lot.

In a Scrum Team, the person who typically leads Sprint Reviews and presentations is the Scrum Master. The Scrum Master is a servant-leader for the Scrum Team, and they facilitate Scrum events as requested or needed. They ensure that everyone follows Scrum theory, practices, and rules. As a result, Scrum Master is the best answer.

The Product Owner is primarily responsible for maximizing the value of the product resulting from the work of the Development Team. They manage the product backlog, but they do not generally lead the Sprint Reviews. Thus, 'Product Owner' is not a fitting role for John in this case.

Stakeholders do not play an active role in running the sprint or hosting the sprint reviews. Instead, they are usually invited by Scrum Team to provide their inputs during the Sprint Reviews. Therefore, 'Stakeholder' is not correct.

Lastly, the developers in a scrum team develop and delivers potentially releasable increments of 'Done' product at the end of each Sprint. They indeed take part in the presentation of the created increment during the Sprint Reviews, but they do not lead these events. So, 'Developer' is not the correct role for John either.

The Development Team, according to Scrum framework, will have the most intimate understanding of the technical requirements and capabilities for executing a user story. They are best suited to opine on the technical feasibility of a particular user story due to their hands-on experience with the codebase, tools, and technologies being used. While the ScrumMaster helps remove obstacles and optimizes the workings of the team, they may not necessarily be the technical expert to advise on technical feasibility. The Stakeholders and the End Users, although very important for providing business and user requirements respectively, may not possess the requisite technical expertise to advise on technical feasibility of a user story.