30+ Capgemini Scrum Master Interview Questions and Answers

As a Scrum Master, I would handle the situation by following these steps:

• Assess the impact of the developer's absence on the critical user story

• Communicate with the team and stakeholders about the situation

• Identify if there are any other team members who can take over the work

• If no immediate replacement is available, prioritize the critical user story and adjust the sprint plan accordingly

• Work with the Product Owner to manage expectations and potentially reprioritize other us...read more

The three pillars of Scrum are transparency, inspection, and adaptation. They are interrelated and support the Scrum framework.

• Transparency ensures that all information is visible and accessible to the team, stakeholders, and customers.

• Inspection involves regularly reviewing the progress, artifacts, and processes to identify any deviations or issues.

• Adaptation refers to making necessary changes based on the inspection results to improve the product and the process.

• These pilla...read more

Velocity is the amount of work completed in a sprint, while capacity is the amount of work a team can handle in a sprint.

• Velocity is a measure of the team's productivity in completing user stories or tasks in a sprint.

• Capacity is the amount of work a team can handle in a sprint, taking into account factors such as team size, availability, and skill level.

• Velocity is calculated by dividing the total number of story points completed in a sprint by the length of the sprint in da...read more

Poker is an estimation technique used in Agile project management. Fibonacci series is used for story points to reflect uncertainty.

• Poker is a collaborative estimation technique where team members assign story points to user stories.

• It helps in determining the effort required to complete a user story.

• Fibonacci series (0, 1, 2, 3, 5, 8, 13, etc.) is used to reflect the uncertainty and complexity of the work.

• Larger numbers in the Fibonacci series indicate higher uncertainty and...read more

The pillars of Scrum are transparency, inspection, and adaptation.

• Transparency: All information about the project must be visible and understandable to everyone involved.

• Inspection: Regularly inspect the progress and the product to identify any deviations or issues.

• Adaptation: Based on the inspection, make necessary changes and adjustments to improve the product and the process.

To plan the capacity for a sprint, consider team velocity, individual availability, and any external factors.

• Calculate the team's velocity by reviewing past sprints and measuring the average number of story points completed.

• Consider individual team member availability, taking into account vacations, holidays, and other commitments.

• Factor in any external dependencies or constraints that may impact the team's capacity, such as shared resources or dependencies on other teams.

• Adj...read more

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

• Capacity is calculated by estimating the number of hours each team member can work in a sprint and multiplying it by the number of team members.

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

• Capacity and velocity can be adjusted based on factors such as team member availability, skill level, and external dependencie...read more

The principles of Agile are a set of values and beliefs that guide the Agile methodology.

• Customer satisfaction is the highest priority

• Welcome changing requirements, even late in development

• Deliver working software frequently

• Collaboration between business people and developers

• Build projects around motivated individuals

• Face-to-face conversation is the best form of communication

• Working software is the primary measure of progress

• Maintain a sustainable pace

• Continuous attention to ...read more

Methodology refers to a set of principles and guidelines for a specific process, while framework is a structure that provides a foundation for a process.

• Methodology is a set of rules and guidelines for a specific process, while framework is a structure that provides a foundation for a process.

• Methodology is more prescriptive, while framework is more flexible.

• Examples of methodologies include Waterfall, Agile, and Lean, while examples of frameworks include Scrum, Kanban, and S...read more

KPIs used to measure project health

• Velocity: Measure of work completed in each sprint

• Sprint Burndown Chart: Tracks progress of work remaining in a sprint

• Cycle Time: Time taken to complete a user story from start to finish

• Defect Density: Number of defects found per unit of work

• Customer Satisfaction: Feedback from stakeholders and end-users

Agile is a methodology and Scrum is a framework under Agile.

• Agile is a set of values and principles for software development.

• Scrum is a framework that follows Agile principles and provides a structure for implementing them.

• Agile is more flexible and adaptable to change than Scrum.

• Scrum has defined roles, events, and artifacts that provide a clear structure for the team.

• Agile can be applied to various industries, while Scrum is mainly used in software development.

• Example: Agil...read more

Scrum metrics include velocity, burn-down charts, sprint burndown, team happiness index, and cycle time.

• Velocity - measures the amount of work completed in a sprint

• Burn-down charts - track the remaining work in a sprint

• Sprint burndown - shows the progress of the sprint

• Team happiness index - measures the team's satisfaction and engagement

• Cycle time - measures the time it takes to complete a user story

The different columns in a Kanban Board are Backlog, To Do, In Progress, and Done.

• Backlog: Contains all the tasks that are yet to be started

• To Do: Contains the tasks that are ready to be worked on

• In Progress: Contains the tasks that are currently being worked on

• Done: Contains the tasks that have been completed

Scrum is a framework for agile project management.

• Scrum provides a set of guidelines and principles for managing and organizing work.

• It emphasizes iterative and incremental development.

• Scrum is flexible and allows teams to adapt and self-organize.

• It focuses on delivering value to the customer.

• Scrum includes specific roles, events, and artifacts.

• Examples of Scrum artifacts are product backlog, sprint backlog, and increment.

Story points are a unit of measure used in Agile project management to estimate the effort required to complete a user story.

• Story points are relative estimates of effort, not time.

• They are assigned to user stories during sprint planning.

• They take into account factors such as complexity, risk, and uncertainty.

• They help the team to plan and track progress more effectively.

• Examples of story point values include 1, 2, 3, 5, 8, 13, 20, 40, and 100.

My favourite Scrum ceremony is the Sprint Review.

• I enjoy the opportunity to showcase the team's work to stakeholders.

• It's a chance to receive feedback and make improvements for the next sprint.

• I also appreciate the collaborative nature of the ceremony, as it involves the entire team.

• Other ceremonies are important too, but the Sprint Review stands out to me.

• For example, the Daily Scrum helps keep the team aligned and focused.

• The Sprint Retrospective allows for continuous impro...read more

Yes, release plan is a high-level view of the product roadmap, release planning is the process of creating a detailed plan for a specific release, and release management is the ongoing process of managing and monitoring the release.

• Release plan is a strategic plan that outlines the product roadmap and high-level features to be delivered in each release.

• Release planning is a detailed planning process that involves breaking down the high-level features into smaller tasks, estim...read more

I use various tools to facilitate Scrum processes and communication.

• Jira for backlog management and sprint planning

• Slack for team communication and updates

• Zoom for remote daily stand-ups and sprint reviews

• Google Drive for document sharing and collaboration

• Trello for visualizing workflow and progress

• Miro for virtual whiteboarding and brainstorming

Designing a Jira board involves creating columns, swimlanes, and filters to organize tasks effectively.

• Start by identifying the workflow stages for your project

• Create columns representing each stage (e.g. To Do, In Progress, Done)

• Set up swimlanes to group tasks by team, priority, or other criteria

• Use filters to customize the view and track progress efficiently

Scrum master is responsible for facilitating the Scrum process, ensuring the team follows Agile principles, and removing any obstacles that may hinder the team's progress.

• Facilitates Scrum events such as daily stand-ups, sprint planning, sprint review, and sprint retrospective

• Helps the team understand and implement Agile principles and practices

• Removes impediments that are blocking the team's progress

• Acts as a coach and mentor to the team members

• Ensures the team is self-organ...read more

Burndown charts show remaining work over time, while burn up charts show completed work over time.

• Burndown charts track remaining work to reach the project goal by the end of the sprint.

• Burn up charts track completed work over time, showing progress towards the project goal.

• Burndown charts typically have a downward trend, while burn up charts have an upward trend.

• Both charts help teams visualize progress and make informed decisions during the sprint.

Scrum day to day activities involve daily stand-up meetings, sprint planning, backlog grooming, sprint reviews, and retrospectives.

• Daily stand-up meetings to discuss progress and plan for the day

• Sprint planning to determine tasks for the upcoming sprint

• Backlog grooming to prioritize and refine the product backlog

• Sprint reviews to demonstrate completed work to stakeholders

• Retrospectives to reflect on the sprint and identify areas for improvement

Agile Manifesto is a set of values and principles for software development emphasizing flexibility, collaboration, and customer satisfaction.

• Agile Manifesto values individuals and interactions over processes and tools.

• It values working software over comprehensive documentation.

• It values customer collaboration over contract negotiation.

• It values responding to change over following a plan.

Prioritizing backlogs involves understanding business value, dependencies, risks, and stakeholder needs.

• Understand the business value of each item in the backlog

• Consider dependencies between backlog items

• Assess risks associated with each item

• Take into account stakeholder needs and feedback

• Use techniques like MoSCoW prioritization or Value vs Effort matrix

The 4 principles of Scrum are commitment, focus, openness, and respect.

• Commitment: Team members commit to achieving the goals of the sprint.

• Focus: Everyone focuses on the work of the sprint and the goals of the team.

• Openness: Team members and stakeholders are open about the work and challenges.

• Respect: Team members respect each other's opinions, skills, and expertise.

Scrum ceremonies are structured meetings that facilitate collaboration and progress in Agile project management.

• Sprint Planning: Teams define the work to be done in the upcoming sprint. Example: Prioritizing user stories from the backlog.

• Daily Stand-up: A short daily meeting where team members share updates and obstacles. Example: Each member answers what they did yesterday, what they'll do today, and any blockers.

• Sprint Review: At the end of a sprint, the team demonstrates w...read more

The daily activities of a Scrum Master involve facilitating daily stand-up meetings, removing impediments, coaching the team, and ensuring adherence to Scrum practices.

• Facilitating daily stand-up meetings to keep the team aligned and focused

• Removing impediments that are blocking the team's progress

• Coaching the team on Scrum principles and practices

• Ensuring adherence to Scrum processes and ceremonies

• Collaborating with the Product Owner to prioritize the backlog

• Helping the team...read more

Kanban is a visual management tool for workflow optimization, while Lean is a methodology focused on eliminating waste and improving efficiency.

• Kanban is based on visualizing work on a board with columns representing different stages of the process.

• Lean focuses on continuous improvement, reducing waste, and delivering value to customers.

• Kanban limits work in progress to improve flow and identify bottlenecks.

• Lean principles include value stream mapping, just-in-time production...read more

Sprint planning duration should typically be 8 hours for a 1-month sprint

• Sprint planning duration is usually 8 hours for a 1-month sprint

• For shorter sprints, the duration should be proportionally shorter

• Ensure all team members are present and engaged during sprint planning

• Use tools like planning poker to estimate user stories accurately