Infosys Scrum Master Interview Questions, Process, and Tips

The product backlog is a prioritized list of user stories, features, and enhancements that need to be developed.

• It is a dynamic document that evolves throughout the project.

• Items in the backlog are ordered based on their value and priority.

• The backlog is constantly refined and updated by the product owner and development team.

• It serves as a communication tool between the stakeholders and the development team.

• Examples o...read more

Sprint review is a Scrum event where the development team presents the completed work to stakeholders.

• Sprint review is held at the end of each sprint

• It is an opportunity for the development team to showcase the completed work to stakeholders

• Stakeholders provide feedback and suggest changes

• The product owner determines what to do with the feedback and updates the product backlog accordingly

• The outcome of the sprint revie

The sprint backlog is a list of tasks that the development team plans to complete during a sprint.

• It is created during the sprint planning meeting.

• It contains the user stories or product backlog items that will be worked on during the sprint.

• Each task in the sprint backlog is estimated and assigned to a team member.

• The sprint backlog is a dynamic document that can be updated throughout the sprint.

• It helps the team to t...read more

Scrum Master activities include facilitating Scrum events, removing impediments, coaching the team, and ensuring adherence to Scrum principles.

• Facilitating Scrum events such as Daily Standups, Sprint Planning, Sprint Review, and Retrospective

• Removing impediments that hinder the team's progress

• Coaching the team on Agile and Scrum practices

• Ensuring adherence to Scrum principles and values

• Helping the team self-organize an

Capacity planning for a sprint involves estimating team's capacity and considering factors like team size, individual availability, skill levels, and historical velocity.

• Estimate team's capacity based on team size and individual availability

• Consider team members' skill levels and experience

• Take into account any planned time off or other commitments

• Review historical velocity to understand team's past performance

• Adjust c...read more

Organize retrospective by setting the stage, gathering data, generating insights, deciding what to do, and closing the retrospective.

• Set the stage by creating a safe environment for team members to share their thoughts and feelings.

• Gather data by reviewing what went well, what didn't go well, and what could be improved.

• Generate insights by discussing the root causes of issues and identifying patterns.

• Decide what to do ...read more

Estimation of user story and defect management involves breaking down tasks, assigning story points, and tracking progress.

• Break down user stories into smaller tasks for better estimation

• Assign story points based on complexity, effort, and risk

• Track progress using burndown charts or velocity metrics

• Prioritize defects based on severity and impact on users

• Regularly review and update estimates as more information becomes