Scrum Scrum Master Certified SMC New Questions

Primary objectives of the meeting are to identify three specific things:

Things the team needs to keep doing: best practices

Things the team needs to begin doing: process improvements

Things the team needs to stop doing: process problems and bottlenecks

These areas are discussed and a list of Agreed Actionable Improvements is created.

Although the Stakeholder(s) and the Product Owner have the final say on Prioritized Product Backlog Items

and whether to accept or reject any Change Requests presented during Demonstrate and Validate Sprint, it is

the Scrum Master’s responsibility to ensure that the requirements and Acceptance Criteria are not altered

during the Sprint Review Meeting for the User Stories completed in the current Sprint. This prevents the

rejection of completed User Stories based on the fact that they do not meet newly changed requirements. If

any requirements need to be changed, any corresponding PBI needs to be revised to accommodate the

modified requirements in a future Sprint.

The Skills Requirement Matrix, also known as a competency framework, is used to assess skill gaps and

training requirements for team members. A skills matrix maps the skills, capabilities, and interest level of team

members in using those skills and capabilities on a project. Using this matrix, the organization can assess any

skill gaps in team members and identify the employees who will need further training in a particular area or

competency. Team members may not always possess the required knowledge or skills to work in the Scrum

environment. The Product Owner should evaluate the training needs of potential team members and facilitate

training to bridge any knowledge gaps in the team.