10+ Infosys Scrum Master Interview Questions and Answers

Scrum principles can be implemented through daily stand-ups, sprint planning, retrospectives, and backlog grooming.

• Daily stand-ups ensure team communication and progress tracking.

• Sprint planning involves setting goals and prioritizing tasks for the upcoming sprint.

• Retrospectives allow for reflection and continuous improvement.

• Backlog grooming ensures the backlog is up-to-date and prioritized.

• Using visual aids such as burndown charts and task boards can aid in transparency and...read more

Scrum fundamentals are the basic principles and values that guide the Scrum framework.

• Empirical process control

• Self-organizing teams

• Iterative and incremental development

• Time-boxed events

• Product backlog

• Sprint backlog

• Incremental delivery

• Continuous improvement

• Transparency

• Inspection and adaptation

Cost of estimation can be calculated by considering the time and effort put in by the team.

• Calculate the total time spent by the team on estimation

• Multiply the total time by the hourly rate of the team

• Add any additional costs such as tools or software used for estimation

• Divide the total cost by the number of items estimated to get the cost per item

• Use the cost per item to make informed decisions about future estimation efforts

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 by collaboratively coming up with action items to address ...read more

Scrum Master responsibilities include facilitating sprint planning, coaching the team, and leading scrum ceremonies.

• Facilitating sprint planning meetings to help the team set goals and plan work for the upcoming sprint

• Coaching the team on agile principles and practices, helping them improve their processes and collaboration

• Leading daily stand-up meetings to keep the team aligned and focused on their goals

• Organizing and facilitating sprint review and retrospective meetings to ...read more

Capacity can be evaluated by analyzing team's historical data, considering individual skills and availability, and factoring in external factors.

• Analyze team's historical data to determine their average velocity or throughput

• Consider individual team member's skills and availability to estimate their contribution

• Factor in external factors such as holidays, vacations, and other commitments

• Use tools like burn-up or burn-down charts to track progress and adjust capacity according...read more

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 capacity based on any known risks or uncertainties

Estimation techniques are used to predict the effort required to complete a task or project.

• Planning Poker - team members estimate the effort required for a task by assigning story points

• T-Shirt Sizing - team members estimate the size of a task using t-shirt sizes (XS, S, M, L, XL)

• Relative Sizing - team members compare the size of a task to a reference task

• Bottom-Up Estimation - breaking down a task into smaller sub-tasks and estimating each sub-task

• Expert Judgment - using th...read more

Vertical slicing is breaking down a feature into smaller, vertical slices that deliver value to the customer.

• Vertical slicing is a technique used in Agile development.

• It involves breaking down a feature into smaller, vertical slices that deliver value to the customer.

• Each slice should be independent and deliver a complete piece of functionality.

• This allows for faster feedback and iteration.

• Example: Breaking down a login feature into slices such as user authentication, passwor...read more

Velocity is a measure of the amount of work a team can complete in a sprint.

• Velocity is calculated by adding up the number of story points completed in a sprint.

• It is used to help the team plan and forecast how much work they can complete in future sprints.

• Velocity can vary from sprint to sprint depending on factors such as team capacity and complexity of work.

• For example, if a team completes 20 story points in a sprint, their velocity is 20.

There are 5 Scrum ceremonies: Sprint Planning, Daily Standup, Sprint Review, Sprint Retrospective, and Backlog Refinement.

• Sprint Planning - Plan the work to be done in the upcoming sprint

• Daily Standup - Daily check-in to discuss progress and any obstacles

• Sprint Review - Demo the work completed in the sprint to stakeholders

• Sprint Retrospective - Reflect on the sprint and identify areas for improvement

• Backlog Refinement - Review and prioritize the product backlog

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 and continuously improve

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 available

Sprint Zero is a preparatory phase before the start of the first official sprint in Scrum.

• Sprint Zero focuses on setting up the project, team, and environment.

• Activities in Sprint Zero may include creating the project backlog, setting up development tools, and defining team roles.

• Sprint Zero helps in laying the foundation for a successful project by addressing any initial setup or preparation tasks.

• It is not a mandatory part of Scrum but can be beneficial for teams new to the...read more

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 of backlog items include user stories, bug fixes, technical...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 review can influence the next sprint planning

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 track progress and ensure that the sprint goal is achieved.

Scrum is a framework for agile project management that emphasizes collaboration, flexibility, and continuous improvement.

• Scrum involves breaking down projects into small, manageable tasks called user stories.

• It includes regular meetings such as daily stand-ups, sprint planning, sprint review, and sprint retrospective.

• Scrum roles include Product Owner, Scrum Master, and Development Team.

• Key artifacts in Scrum include the Product Backlog, Sprint Backlog, and Increment.

• Scrum pro...read more