Basic to Advanced Scrum Master Interview Questions

1

How do you handle feedback from team members and stakeholders regarding your performance as a Scrum Master?

Reference answer

I encourage regular feedback sessions and maintain open communication channels to ensure I receive constructive criticism. I actively listen to the feedback, show appreciation, and implement necessary changes to continuously improve my performance.

2

What happens if the Sprint Goal becomes obsolete mid-Sprint?

Reference answer

As per the Scrum Guide, if the Sprint Goal becomes obsolete meaning business context changed so significantly that continuing makes no sense the Product Owner can cancel the Sprint. After cancellation: - Completed "Done" items are reviewed and accepted - Incomplete work returns to the Product Backlog - A new Sprint Planning is conducted immediately Cancellation is rare and should never be taken lightly but continuing a Sprint toward a goal that no longer matters is worse.

3

What are the five steps of Risk Management?

Reference answer

Identify Risks – Recognise potential risks that could impact the project. This includes technical failures, resource shortages, or market changes. Analyse Risks – Assess the likelihood and impact of each risk. Prioritize them based on severity and probability. Evaluate and Prioritise Risks – Determine which risks need immediate attention and which can be monitored. High-impact risks require proactive mitigation. Treat Risks – Develop strategies to reduce, transfer, or eliminate risks. Implement preventive measures. Monitor and Review – Continuously track risks and update plans as needed. Regular reviews ensure risks remain manageable.

4

What are some common Scrum Master interview questions?

Reference answer

Common interview questions often include inquiries about your understanding of the Scrum process, handling team conflicts, facilitating meetings, and your experiences with Agile methodologies. Prepare for situational and behavioural questions that assess your problem-solving and leadership skills.

5

How do you foster a culture of continuous improvement within your team?

Reference answer

I foster a culture of continuous improvement by encouraging regular retrospectives where the team can openly discuss what went well and what needs improvement. I also promote a learning environment by providing training and development opportunities, ensuring that the team is always evolving.

6

Can you describe a situation where you had to facilitate a team meeting that led to a significant decision? How did you ensure everyone's voices were heard?

Reference answer

You're looking for candidates who can demonstrate their ability to guide discussions and meetings constructively. They should showcase their skills in encouraging balanced participation, handling dominant personalities, and managing conflicts. Candidates who provide specific examples of how they've applied these skills in past situations give an insight into their capabilities as a Scrum Master.

7

What is an ideal way, according to you, to train a newly established Scrum team?

Reference answer

Training a scrum team consists of a structured process where you set the foundation for the principles you will share with your newly set-up team. Although team members will already be familiar with the Scrum methodology, roles, and responsibilities, as a mentor, you should guide them through the fundamentals of Scrum and Agile principles, while defining their goals and the roadmap they should follow. Brief everyone on the core concepts, theories, and practices, and ensure that everyone is well-aligned with the status of projects and products to be delivered, so that there is no confusion or chaos in the process.

8

A manager wants to assign tasks. What do you tell them?

Reference answer

Clarify that the team self-manages and explain the benefits of autonomy.

9

Explain the user story structure with an example.

Reference answer

A typical user story follows this format: As a [type of user], I want [a goal] so that [benefit]. - Example: As a customer, I want to reset my password so that I can regain access to my account if I forget it.

10

How Does Agile and Scrum Differ If They Do?

Reference answer

If the person is unaware that scrum falls under the larger umbrella of agile that's a problem. There are four main values and 12 principles of agile, while scrum has its own set of values and principles. Scrum is a framework to help teams become agile. This question will reveal whether the candidate is in fact a scrum master.

11

Q #4) What are the scrum events?

Reference answer

There are five events in a scrum: - Sprint Planning: This event happens at the start of the sprint where the scrum team discusses the items in the product backlog and decides which ones will form part of the current sprint. The deliverable of the sprint planning meeting is the sprint backlog. - Daily Scrum: Daily scrum is timeboxed to 15 minutes and is held usually at the start of the day. In the daily scrum, the scrum team discusses the sprint backlog items to understand their progress or any issues/blockers that need to be resolved. - Sprint: The sprint itself is the duration in which all the sprint backlog items are delivered. This is usually 2 weeks but can be a month. - Sprint Review: Sprint review is held at the end of the sprint where the team reviews the product with the stakeholders. The sprint review is a maximum of 4 hours. - Sprint Retrospective: This meeting reviews the last sprint to answer questions: What went well and what could be improved and then develops a plan to improve. The sprint retrospective is 1 hour to 3 hours.

12

How do you estimate user stories in points vs. man-hours?

Reference answer

Estimating User Stories in Points vs. Man-Hours: [not explicitly listed in the text, but implied from context]

13

What are the three pillars of Scrum?

Reference answer

Following are the three pillars of Scrum: - Transparency: Those accountable for the outcome must be able to see important components of the process. Transparency necessitates that those elements be defined by a uniform standard so that viewers may comprehend what they are seeing. For example, all participants must speak the same language when referring to the process, and those performing the job and those inspecting the resulting increment must have the same concept of "done." - Inspection: To spot undesired deviations, Scrum users must examine Scrum artifacts and progress toward a Sprint Goal on a regular basis. Their inspections should not be so frequent that they become a hindrance to their work. Inspections are most effective when performed diligently at the point of work by skilled inspectors. - Adaption: If an inspector concludes that one or more parts of a process deviate beyond acceptable boundaries, the method or the material being processed must be modified. To avoid future deviation, an adjustment must be performed as soon as feasible.

14

How do you debrief a Sprint Retrospective with leadership?

Reference answer

Share systemic learnings without blaming and highlight team improvement goals.

15

How do you handle incomplete items in a Sprint Review?

Reference answer

Situation: Once, our team had incomplete items during a Sprint Review. Task & Action: I ensured these items were transparently presented, explaining the reasons for incompletion and the plan for addressing them. Result: This approach maintained stakeholder trust and provided clear expectations for the next Sprint.

16

What does INVEST stand for in User Stories?

Reference answer

INVEST stands for Independent, Negotiable, Valuable, Estimable, Small, and Testable. It's a guide to writing good user stories in Agile projects.

17

What is the Definition of Done (DoD)?

Reference answer

The Definition of Done (DoD) is a shared checklist of quality standards and criteria the entire Scrum Team agrees on. It creates a consistent baseline for "done" work that prevents partial features from being shipped and ensures quality and predictability.

18

What is Agile?

Reference answer

Agile is a mindset and set of principles that promote iterative development, customer collaboration, and adaptability to change. Agile is defined in the Agile Manifesto and is implemented using frameworks like Scrum, Kanban, and SAFe.

19

What is your approach to estimating the release date for a product in Agile?

Reference answer

By tracking the team's Velocity and considering the Product Backlog size, I estimate a realistic release date. This is regularly reviewed and adjusted based on the team's progress and any changes in scope.

20

How do you ensure effective communication in Scaled Agile environments?

Reference answer

Besides regular Scrum of Scrums, I encourage the use of collaborative tools and cross-team meetings. It's crucial to maintain transparency and a shared understanding of goals and progress.

21

What is an ideal team size for Scrum and why?

Reference answer

The optimal Scrum team size is usually between 3 and 9 members. This number is thought to be best since it's big enough to possess a variety of skills but small enough to stay agile and communicate well.

22

How do you promote self-organization within the Scrum team while ensuring alignment with overall project goals?

Reference answer

Fostering self-organization within the Scrum team involves creating an environment where team members can take ownership and make decisions collaboratively. I provide guidance on Scrum principles, encourage open communication, and emphasize the importance of shared responsibility. During sprint planning, I facilitate discussions that allow the team to self-organize and commit to achievable goals. To ensure alignment with project goals, I maintain a clear vision and communicate the overarching objectives to the team. By empowering the team to make decisions collectively and providing a framework for alignment, we strike a balance between autonomy and project cohesion.

23

Define the three pillars of Scrum.

Reference answer

The three Scrum pillars include Transparency, Inspection and Adaptation, where transparency refers to the openness and clarity of concepts among the team members, ensuring informed decision making. Inspection is all about keeping a check on the progress made by the team in the direction of the established goals. This assessment is carried out by clients, team members and stakeholders, and lastly, adaptation is about the team's way of integrating suggestions and improvements into the development process to release an ideal output.

24

Explain your approach to continuous improvement

Reference answer

Keeping a focus on continuous improvement is important in the scrum framework. The scrum team uses regular feedback meetings, like sprint retrospectives, to talk about problems and think of ways to solve them. When you work in a place that values trying new things, the team can test out new practices and learn new technologies. This can lead to better work and more interest in what they do. When the team has ownership of their work, they feel more able to spot what needs to change and improve. Sharing useful facts, updates, and checking team velocity can show how the team grows and what steps to take next. This helps guide later sprints. In the end, it raises business value and helps the team follow agile principles. This way, the scrum team works well and the scrum environment gets better.

25

What is a User Story?

Reference answer

User stories are a fundamental tool in Agile development, particularly in Scrum, for capturing requirements and prioritizing work. They focus on the user's needs and goals, helping teams to better understand and deliver value to their users. User stories are often written on index cards or in digital tools and are used to facilitate discussions, planning, and estimation during Agile ceremonies like Sprint Planning. It serves as a communication tool, emphasizing the customer's perspective and providing context to the development team. Unlike technical specifications, user stories focus on why a feature is needed, who it is for, and how it will deliver value.

26

How do you ensure that every team member contributes effectively during the daily stand-up meetings?

Reference answer

To ensure effective contribution, I encourage a round-robin format where each member answers the three key questions: what they did yesterday, what they will do today, and any blockers. I also foster a safe environment by emphasizing that the meeting is for the team, not for status reporting to management.

27

What are the artifacts of the Scrum process?

Reference answer

- Product Backlog – A prioritized list of features and requirements. - Sprint Backlog – A selection of backlog items for a sprint. - Increment – The working product delivered at the end of a sprint. - Definition of Done (DoD) – Criteria defining when a task is complete.

28

How do you balance delivering new features with reducing technical debt?

Reference answer

I work with the Product Owner to ensure technical debt and quality work are visible in the backlog. I advocate for allocating capacity for refactoring and improvement tasks every sprint. I also help stakeholders understand that sustained delivery speed depends on long-term code health, not just short-term feature output.

29

A member of the scrum team does not want to participate in the sprint planning meetings and considers meetings as a waste of time. How do you deal with that kind of attitude?

Reference answer

For a Scrum Master, it is important to understand the pulse of the team. If there's a member in your team who takes the meetings as useless, it's time to know why he/she is adopting such a behavior. The focus should be on the behavior rather than the individual, the Scrum Master should try to talk to the team member individually by asking open-ended questions to find out the reason for not attending the meeting. Certainly, there is a need to understand the cause of this behavior and try to explain the importance of the planning meeting (Scrum ceremonies). In Scrum, each individual is important, it is like the wheels of a truck, any wheel gets dealigned or malfunctioned, the complete vehicle suffers. Hence, the need to explain the impact of not having his presence in the planning meeting and its impact on the entire team arises. Even the team can start to feel this imbalance. If it is still not resolved, the Scrum Master can set up a meeting with his reporting manager to talk about the concern and look out for ways to help the team member and the team.

30

What is your understanding of the Scrum Framework?

Reference answer

The scrum framework comprises a Scrum team that has a product owner, a scrum master and developers, each of whom works on a different set of responsibilities. The Scrum framework is mainly used by the software development team and engineers who are required to act promptly and adapt to dynamic scenarios, keeping in mind the financial scope of the projects. The Scrum framework involves a set of values, principles, ceremonies, and practices that the Scrum team members take care of to deliver an output.

31

How do you ensure effective communication and collaboration between the Scrum team and stakeholders?

Reference answer

I ensure effective communication and collaboration by facilitating regular meetings and updates with stakeholders, using clear and concise communication channels. Additionally, I encourage stakeholder involvement in key Scrum events to maintain alignment and transparency.

32

What is the Agile Manifesto?

Reference answer

Four values and principles behind the Agile philosophy are - Individuals and interactions over processes and tools - Working software over comprehensive documentation - Customer collaboration over contract negotiation - Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.

33

What is a release candidate?

Reference answer

A release candidate is a build or version of the software that can be released to production. Further, testing such as UAT may be performed on this version of the product.

34

How does a Scrum Master track Sprint progress?

Reference answer

- Daily Standups: Monitor blockers and progress. - Burndown Charts: Track work remaining. - Sprint Backlog Updates: Check completed vs. pending tasks.

35

How do you coach without authority?

Reference answer

Use influence, trust, facilitation skills, and coaching stances.

36

How long should an Agile sprint be?

Reference answer

Typically 1-4 weeks, depending on project needs.

37

Describe how you build psychological safety in a team.

Reference answer

Encourage vulnerability, acknowledge failure as learning, and create a blame-free space.

38

What anti-patterns do you know of that can happen during a Sprint Retrospective?

Reference answer

Typical Scrum Sprint Retrospective anti-patterns are: - Waste of time: The team does not collectively value the Sprint Retrospective. If some team members consider the Sprint Retrospective to be of little or no value, it is most often the Sprint Retrospective itself that sucks. Is it the same procedure every time, ritualized and boring? Have a meta-Sprint Retrospective on the Sprint Retrospective itself. Change the venue. Have a beer- or wine-driven Sprint Retrospective. There are so many things a Scrum Master can do to make Sprint Retrospectives interesting and valuable again, reducing the absence rate. Furthermore, it is good to remember that (in my experience) introverts like to take part in Sprint Retrospectives also. - Prisoners: Some team members only participate because they are forced to team up. Don't pressure anyone to take part in a Sprint Retrospective. Instead, make it worth their time. The drive to continuously improve as a team needs to be fueled by intrinsic motivation, neither by fear nor by order. Tip: Retromat's “Why are you here?” exercise is a good opener for a Sprint Retrospective from time to time. - Groundhog day: The Sprint Retrospective never changes in composition, venue, or length. In this case, the is that the team will revisit the same issues over and over again — it's like Groundhog Day without the happy ending. - Let's have it next Sprint: The team postpones the Sprint Retrospective into the next Sprint. Beyond the “inspect & adapt” task, the Sprint Retrospective serves as a moment of closure, helping reset everybody's mind so that the team can focus on the new Sprint goal. That is the reason why we have the Sprint Retrospective before the planning of the follow-up Sprint. Postponing it into the next Sprint may also interrupt the flow of the team, and delay tackling possible improvements by up to a Sprint. This is why it is important to have the Sprint Retrospective before the planning of the follow-up Sprint. - #NoDocumentation: No one is taking minutes for later use. A Sprint Retrospective is a substantial investment for many reasons and should be taken seriously. Taking notes and photos supports the process. - No psychological safety: The Sprint Retrospective is an endless cycle of blame and finger-pointing. The team wins together, the team loses together. Unfortunately, the blame game documents both the failure of the Scrum Master as the facilitator of the Sprint Retrospective as well as the team's lack of maturity and communication skills. - Bullying: One or two team members are dominating the Sprint Retrospective. This communication behavior is often a sign of either a weak or uninterested Scrum Master. The Sprint Retrospective needs to be a safe place where everyone–introverts included–can address issues and provide their feedback free from team members who are dominating the conversation, bullying or intimidating other teammates. The failure to provide a safe place will result in participants dropping out of the Sprint Retrospective and render the results obsolete. It is the main responsibility of the Scrum Master to ensure that everyone can be heard and has an opportunity to voice their thoughts. According to Google, equally distributed speaking time fosters and signifies a high-performing team. - Stakeholder alert: Stakeholders participate in the Sprint Retrospective. There are plenty of Scrum events that address the communication needs of stakeholders: the Sprint Review, the Product Backlog refinement, the Daily Scrum events — not to mention opportunities of having a conversation at water coolers, over coffee, or during lunchtime. If that spectrum of possibilities is still not sufficient, feel free to have additional meetings. However, the Sprint Retrospective is off-limits to stakeholders. - Passivity: The team members are present but are not participating. There are plenty of reasons for such a behavior: they regard the Sprint Retrospective as a waste of time, it is an unsafe place, or the participants are bored to death by its predictiveness. The team members may also fear negative repercussions should they be absent, or maybe a homogenous group of introverts was unwittingly hired. Whatever the reason, there is likely no quick fix. The Scrum Master needs to determine what style of Sprint Retrospective will work best in their organization's context.

39

What is the Definition of Done (DoD)?

Reference answer

The Definition of Done (DoD) is a clear set of criteria that must be met for a product backlog item or increment to be considered complete. It ensures that all team members share a common understanding of what it means for work to be finished. To achieve the DoD, the team should collaboratively define specific criteria, including coding standards, testing requirements, and documentation. Regular reviews during Sprint Retrospectives allow adaptation based on lessons learned and project changes. Incorporating quality metrics, such as passing tests and code reviews, ensures high standards are met. Accessible documentation of the DoD promotes adherence, enhancing collaboration and product quality.

40

Describe the biggest challenge you have faced as a Scrum Master. How did you overcome it? How did it make you better at your job?

Reference answer

The candidate should describe a significant challenge (e.g., resistance to Scrum, team conflict), how they overcame it (e.g., through coaching, facilitation), and how the experience improved their skills.

41

What is User Story Mapping?

Reference answer

User Story Mapping is a technique used in product ideation, like discovering a new product or new feature in an existing product. It can be used to identify MVP (minimum viable product).

42

How do you define Agile Success?

Reference answer

There is no standard definition for” Agile Success”. Every organization must develop its own criteria to evaluate whether the adoption of agile was a success or not. Here are a few things to consider: - (Content not explicitly listed in the provided text beyond the introductory statement).

43

Differentiate Between Agile and Scrum.

Reference answer

The difference between Agile and Scrum is a very fundamental and common Scrum Master interview question asked in an interview.

44

How do you handle conflicts within the Scrum team?

Reference answer

Handling conflicts within the Scrum team to promote a productive work atmosphere is crucial. We resolve conflicts by starting conversations among team members to grasp different viewpoints. Our method includes identifying the main reason for conflicts and cooperating to discover solutions everyone can agree on. Promoting a transparent culture and ongoing improvement motivates team members to communicate issues and work together to solve problems efficiently.

45

What development practices complement Scrum well?

Reference answer

While Scrum focuses on the process framework, technical practices are essential for long-term agility. Continuous Integration/Continuous Delivery (CI/CD) enables the frequent delivery that Scrum promotes. Test-Driven Development (TDD) and Behavior-Driven Development (BDD) help ensure quality is built in from the start rather than tacked on at the end. Pair Programming and Mob Programming support knowledge sharing across the team, reducing silos and bottlenecks that can derail Sprint commitments. Refactoring prevents technical debt from accumulating, which is essential for maintaining the sustainable pace that Scrum advocates. DevOps practices like infrastructure as code and automated monitoring help bridge the gap between development and operations. As a Scrum Master, I don't dictate these practices to the team, but I do help them understand how technical practices impact their agility.

46

In Agile, how do you address the challenges of metric-driven pressure on teams?

Reference answer

I focus on the qualitative aspects and team well-being alongside metrics. It's crucial to balance data-driven insights with team morale and ensure that metrics are used to support, not stress, the team.

47

How would you deal with a team member who considers sprint planning meetings a waste of time and refuses to participate?

Reference answer

The Scrum master should focus on the behavior rather than on the individual. Firstly, you should talk to the team member privately and ask open-ended questions to figure out their reasoning. After that, make a case for the importance of sprint planning meetings and why all team members should participate. Moreover, you could encourage other team members to voice their concerns during a retrospective regarding the non-participation of the team member in question. Ask them to talk about how that affects the working environment and the team's performance. Lastly, if all else fails, you should set up a meeting with the team member's reporting manager to discuss solutions and if possible consider a transfer to a team that is not using Scrum.

48

What does the term Minimum Viable Product (MVP) mean to you?

Reference answer

A Minimum Viable Product has only the critical (minimum) features required, ready to be presented to stakeholders and to be shipped for production. This is one of the simplest terms to understand, so be sure you know it — and why it's important in development — ahead of your interview.

49

What strategies do you use to stay updated with Agile methodologies and practices?

Reference answer

I regularly attend Agile conferences, participate in community discussions, and engage in continuous learning through courses and certifications. Staying connected with the Agile community is crucial for staying updated.

50

How do you ensure user stories meet requirements?

Reference answer

I ensure user stories meet requirements by making expectations explicit early and validating them collaboratively before development starts.

51

What are the objectives of Scrum Master Certification?

Reference answer

To sustain and develop the Scrum Developer Program To gain certifications based on assessments To assist our business to grow To escalate to the demands of a progressively intricate world of Scrum. To simplify increasingly complex technologies and products. Spread the materials and techniques in a concise way To move to a collective, inventive methodology to form and facilitate the software.

52

Define the key roles in Scrum (Scrum Master, Product Owner, Development Team).

Reference answer

a)Scrum Master: The Scrum Master acts as a facilitator, ensuring that the Scrum process is followed. b) Product Owner: The Product Owner is responsible for defining and prioritising the work that needs to be done, usually by managing the Product Backlog. c) Development Team: The Development Team is made up of professionals who do the actual work of delivering the product.

53

What do you mean by timeboxing in Scrum? When can a Sprint be cancelled and by whom?

Reference answer

Timeboxing refers to allocating a specific amount of time to a specific activity. A timebox is a time measurement unit. A timebox should be no more than 15 minutes long. Before the Sprint timebox limit expires, a Sprint can be canceled. The sprint can only be canceled by the Product Owner.

54

What Should Be the Ideal Size of a Scrum Team?

Reference answer

Ideally, a scrum team involves 10 or fewer people, where the product owner, scrum master, and developer are the core members. The main purpose of setting up the scrum team is to ensure that there is deliberate skill management of the employees, and there is quality output at the end of the session. If you are someone who is just starting and planning to establish a scrum team, starting small is the key to success. As with smaller teams, there is better collaboration, but as the team members grow beyond a certain count, managing the work done becomes difficult.

55

How do you ensure consistency in Story Point estimation across the team?

Reference answer

By facilitating regular refinement meetings and estimation sessions, I help the team calibrate their understanding of what each point value represents, leading to more consistent estimations over time.

56

Describe a coaching stance.

Reference answer

Neutral, curious, non-judgmental posture encouraging others' self-discovery.

57

Can you describe the difference between a product backlog item and a user story?

Reference answer

A product backlog item (PBI) is a broad term for any item in the backlog, which could be a feature, bug, technical debt, or knowledge acquisition. A user story is a specific type of PBI that describes a feature from an end-user perspective, typically following the format: "As a [user], I want [goal] so that [reason]."

58

How do you ensure that the Scrum team maintains a focus on quality and avoids shortcuts that might compromise the final product?

Reference answer

Upholding a focus on quality requires a combination of clear expectations, continuous monitoring, and a commitment to best practices. I establish coding standards, conduct regular code reviews, and promote pair programming to ensure that quality is built into the development process. During sprint planning, I emphasize the importance of delivering a potentially shippable product increment, which reinforces the team's commitment to quality. If there are time constraints or pressure to take shortcuts, I engage in discussions with the team to assess the potential impact on the final product and collaborate on alternative solutions. By prioritizing quality and maintaining a culture of accountability, we avoid compromising the final product for short-term gains.

59

Does the Scrum Master enforce rules strictly?

Reference answer

Although Scrum does require the Scrum Master to ensure processes are followed, it is crucial to define the extent and limitations of this enforcement. Enforcing rules does not mean forcing the team to follow the process strictly. Instead, it requires including the core principles of Scrum to facilitate the team's achievements. It is important to highlight that encouragement should not be confused with coercion. The Scrum Master does not give orders like a project manager but instead works with the team to solve problems. Although the Scrum Master can emphasize the advantages of implementing specific processes and help the team grasp Scrum practices, the final decision to adopt these practices lies with the team. Moreover, the Scrum Master is a mentor, leading the team on their Agile path and nurturing their achievements. Their goal is to enable the team to succeed in the Agile framework.

60

What are the three pillars of Scrum?

Reference answer

The three pillars of Scrum are Transparency, Inspection, and Adaptation. They help teams stay aligned, regularly review progress, and make improvements as needed.

61

Do You Know Other Agile Frameworks?

Reference answer

Scrum isn't the only framework for teams to become agile. There is also kanban (which uses kanban boards), test-driven development and feature-driven development, to name a few. See what frameworks outside of scrum the person has worked with and how that played out in the project. You want to know how expansive their knowledge is.

62

How do you ensure that the team is following Scrum values and principles?

Reference answer

I model the Scrum values (Commitment, Courage, Focus, Openness, Respect) in my own behavior. I remind the team of these values during events, especially when conflicts arise. I facilitate retrospectives to discuss how well the team is adhering to these values and principles.

63

What is the difference between Epic, User Stories, and Tasks?

Reference answer

- An Epic is a group of related user stories. - User Stories define the actual business requirements. They are generally created by the business owner. - Task: To accomplish the business requirements, the development team creates tasks.

64

Why do Agile transformations fail?

Reference answer

Agile transformations fail due to: - Treating Agile as a process, not a mindset - Lack of leadership alignment - Ignoring cultural change - Over-focusing on tools - Poor coaching support True Agile success requires behavioral change, not just ceremony adoption.

65

How do you ensure that the Scrum team remains focused on delivering value to the customer?

Reference answer

Ensuring the Scrum team remains focused on delivering value to the customer involves continuous alignment with the product vision and priorities. To ensure the Scrum team remains focused on delivering value to the customer, the product owners actively prioritize user stories based on their business value, considering the number of features that contribute to the overall product vision, adhering to Scrum methodology. Therefore, I work closely with the Product Owner to understand customer needs and priorities, translating them into actionable user stories. During sprint planning, I emphasize the importance of delivering increments that align with customer expectations. Additionally, I regularly engage the team in discussions about the impact of their work on end-users, fostering a sense of purpose and commitment to delivering tangible value. By maintaining a customer-centric mindset throughout the development process, we ensure that the team's efforts contribute directly to customer satisfaction.

66

Share an example of when you failed as a Scrum Master

Reference answer

Early in my time as a Scrum Master, I did not stop scope changes for my team. A stakeholder asked for a change during the sprint, saying it was “small.” I thought it would not cause big problems. But it made us switch focus, which slowed everyone down. We did not reach our sprint goal. During the sprint retrospective, I said I made a mistake. I talked about how this change hurt our team's capacity and morale. It was tough, but I learned the importance of saying no and protecting the sprint. After that, we made a simple process for handling change requests. I now use what I learned from this to help Product Owners and stakeholders. Because of this, I am a better Scrum Master.

67

What Is Timeboxing in Scrum?

Reference answer

Timeboxing in Scrum is the maximum time taken by any event, project or activity to sustain the efficiency, priority and productivity of the deliverables. This is achieved by maintaining the scope of the project and sticking to a timeline. In Scrum, the timeboxes work like: - Sprint: Extends for up to one month (maximum) or less. - Sprint Planning: Approximately 8 hours devoted to a one-month sprint session - Daily Scrum: Daily meeting lasting up to 15 minutes - Sprint Review: Approximately 4 hours devoted to a one-month sprint session - Sprint Retrospective: Roughly 3 hours for a one-month sprint session

68

What would you do if the team completes work early?

Reference answer

Options include: - Pulling the highest priority backlog items - Refining future backlog - Reducing technical debt - Improving test automation

69

What is your experience in writing reports for your scrum projects?

Reference answer

The candidate should describe their experience in creating and sharing reports such as sprint reviews, project status updates, velocity tracking, impediment logs, and metrics dashboards. They should explain how they tailor reports for different stakeholders (e.g., team, product owner, management) and use data to support decision-making.

70

What are the key features of a good user story?

Reference answer

A good user story is essential for clear communication and effective Agile development. Here are the key features: - (Content not explicitly listed in the provided text beyond the introductory statement).

71

Q #3) Do you know any other agile methodologies apart from Scrum?

Reference answer

Other Agile methodologies include Kanban, XP, Lean, and SAFe.

72

How do you approach risk management within a Scrum team?

Reference answer

I approach risk management by identifying potential risks early through regular team discussions and implementing mitigation strategies. I continuously monitor these risks and adjust our plans as needed to ensure minimal impact on the project.

73

How do you coach a team to be self-managing?

Reference answer

Gradually reduce dependencies, promote ownership, and facilitate decision-making.

74

Have You Managed More Than One Scrum Team at a Time?

Reference answer

Of course, scrum guidelines say that only one scrum master per team. The key to the question is the use of the word “managed” rather than “led,” as scrum masters don't manage, they lead. So, ask this scrum master interview question as stated above, and see if the candidate is really listening.

75

What is Empirical Process Control in Scrum?

Reference answer

Empiricism refers to work that's based on facts, experiences, evidence, observations, and experimentation. It is established and followed in Scrum to ensure project progress and interpretation is based on facts of observations. It relies on transparency, inspection, and adaption. The mindset of the team and the shift in thought process and culture are essential to achieve the agility required by the organization.

76

What is Sprint 0 and what is a Spike?

Reference answer

Sprint 0 is the preliminary phase used to set up the groundwork for the project. It involves outlining an initial version of the product backlog and providing preliminary estimates for product releases. Its purposes include: - (Content not explicitly listed in the provided text beyond the introductory statement). On the other hand, a spike refers to a dedicated period, often used in Extreme Programming (XP), focused on research, design exploration, investigations, and developing Proof of Concepts (POCs). The primary purpose of a spike is: - (Content not explicitly listed in the provided text beyond the introductory statement).

77

Is the Scrum Master responsible for delivery?

Reference answer

No; the Developers are responsible for delivering a Done increment.

78

What are the key roles of the Scrum Master?

Reference answer

The following are the key roles of the Scrum Master: Scrum master has the main role of managing the Agile projects along with other key responsibilities.

79

What is the role of the Product Owner?

Reference answer

The Product Owner insists on the business's success, thereby maintaining its market worth. Their primary responsibility is identifying and optimizing the Commodity Backlog products. The Product Owner is the client's voice to the team and also represents the consumer. The PO keeps the inventory backlog up-to-date and directs the staff on when to produce what portion of the backlog. The Product Owner plays a crucial role in Scrum, acting as the bridge between the team and stakeholders. Here are the key responsibilities: - (Content not explicitly listed in the provided text beyond the introductory statement).

80

How do you help a team stay Agile while also meeting compliance rules or audit needs?

Reference answer

Talk about helping teams document the right things (like Definition of Done) and work closely with compliance teams without slowing down their delivery. Share how you found balance between following rules and staying Agile.

81

Have you ever worked with stakeholders closely? How do you manage stakeholders who seem incompatible?

Reference answer

During our journey as a scrum master, we come across different people, and stakeholders are the ones that we work closely with. So, a significant share of our vision and work process gets influenced by their ideas, insights and suggestions. The most important aspect of client meetings and stakeholder management is that you get to know them only when you start working with them. Whenever I encounter a stakeholder who is not easy to work with, I give them time and also reflect upon how I can improve this dynamic. For this, I focus on clear communication, understanding their point of view, defining mutual business objectives to work towards them with a similar mindset, taking part in each other's problems to resolve them completely, and following a professional approach to resolve internal conflicts.

82

What are the elements that constitute a good user story?

Reference answer

The elements that constitute a good user story are-

83

What is your experience with Agile transformation?

Reference answer

Candidate's tailored response should include coaching, training, and stakeholder work.

84

Explain Empirical Process Control in Scrum.

Reference answer

Empirical Process Control in Scrum is based on the idea of learning through experience. Scrum uses transparency (visibility of processes), inspection (regular checks on progress), and adaptation (making improvements based on feedback) to continuously evolve and improve the product and process.

85

How do your values align with our company values?

Reference answer

Ideally your candidate would have done their research on your company values. But depending on your interview stage, your candidate may not be super familiar with this information just yet. Be sure to share a proper introduction to your company, including your values and what they mean to you as a team before you ask this question. Their answer will help you figure out if your values are aligned. Listen for: Someone who is particularly interested in the company's future. People who are already thinking of ways to help your company are valuable assets.

86

How would you handle a situation where the Product Owner is unavailable and the team has questions about story details mid-sprint?

Reference answer

First, I wouldn't answer the questions for them—that undermines the PO's authority and makes us dependent on me. But I also wouldn't let them sit blocked. I'd probably say, ‘What's your best judgment on what this should do?' and let them move forward with that assumption. We'd flag it in the sprint review with the PO so she can confirm or adjust. Long-term, I'd work with the PO on a few things: Can we do better backlog refinement so these questions get answered before the sprint? Can the team be more autonomous in deciding trade-offs? I might also propose a brief check-in with the PO mid-sprint on key stories if she's not fully available. The goal is for the team to be unblocked without me becoming a pseudo-PO.

87

A team's velocity has been declining for three sprints. Walk me through how you'd investigate and address this.

Reference answer

I'd start by looking at the actual sprint data. Is the team committing to less work, or are they not finishing what they commit to? That tells you different stories. Then I'd have a conversation in retrospective format: ‘We've noticed velocity declining. What's going on?' Often it's not laziness—it's usually one of a few things: they're getting pulled into unplanned work, story sizes got bigger, or they're dealing with quality issues slowing them down. In one case, we discovered the team was spending 15 hours per sprint debugging production issues that weren't part of our planned work. We worked with the PO to dedicate someone to production support and suddenly velocity went back up. The issue wasn't the team; it was the system.

88

What does a self-structured, self-reliant agile team look like?

Reference answer

Any self-organising, self-reliant agile team is highly driven by principles. They know what their next action would be and how it will impact the dependences associated. They are highly decisive and take full accountability for their work. Additionally, any agile team is open to collaboration, knows the right way to manage and delegate tasks and is highly adaptive to new changes and developments. This makes each of them work decently towards the final, common goal.

89

How do you support continuous learning and improvement in your team?

Reference answer

I promote a culture of feedback and retrospection. Encouraging participation in workshops, seminars, and cross-training within the team fosters a continuous learning environment.

90

What is the difference between MVP and MMP?

Reference answer

The Minimum Viable Product (MVP) is the simplest version of the product that is released to gather customer feedback. The Minimum Marketable Product (MMP) is a version of the product that contains all the essential features necessary for launch. As a Scrum Master, I ensure that the team focuses on delivering the MVP first to validate ideas before adding more features.

91

What are the ceremonies performed in a Scrum framework?

Reference answer

In the Scrum framework, there are several key ceremonies that help the team stay on track and ensure smooth collaboration: a) Sprint Planning: Plan tasks for the sprint. b) Daily Standup: Share progress and blockers. c) Sprint Review: Demo work to stakeholders. d) Retrospective: Reflect and improve. e) Backlog Refinement: Groom the backlog (informal but essential).

92

What is systems thinking in your role?

Reference answer

Understanding how organizational elements interact and addressing root-level issues.

93

How do you ensure that a Sprint Goal is effectively set and understood?

Reference answer

In Sprint Planning, I facilitate a collaborative session where the Product Owner presents the goal, and the team discusses how it aligns with the product vision. I encourage questions and clarifications to ensure everyone is on the same page.

94

What is a good Scrum user story structure?

Reference answer

A good Scrum user story follows a simple and user-focused structure: "As a [user role], I want [goal] so that [reason]." This format clearly captures the Who, What, and Why of the requirement. A well-written story includes a clear title, a meaningful description, and specific acceptance criteria.

95

What is velocity?

Reference answer

The amount of work a team completes in a Sprint, measured by story points or work items.

96

How do you balance the need for documentation with the agile principle of prioritizing working software?

Reference answer

Balancing the need for documentation with the agile principle of prioritizing working software is essential for maintaining agility and efficiency. I advocate for a pragmatic approach, where documentation serves the purpose of enhancing understanding and collaboration without becoming a bottleneck. Critical documentation, such as user stories and acceptance criteria, is prioritized to ensure alignment within the team. I also encourage the use of collaborative tools and real-time communication to reduce the reliance on extensive documentation. By focusing on delivering valuable increments while maintaining sufficient documentation for clarity, we strike a balance that aligns with agile principles.

97

What is your experience with continuous delivery and deployment in Agile environments?

Reference answer

I have extensive experience with continuous delivery and deployment, facilitating frequent and incremental changes to the product. This approach enhances flexibility, reduces risk, and improves product quality through regular feedback and faster issue resolution.

98

What do you understand by the term Sprint? What is its duration?

Reference answer

A Sprint is heart of Scrum. Sprint is a time boxed container which has all 4 mandatory events Sprint Planning, Daily Scrum, Sprint Review & Retrospective. It's a repeatable event of maximum 1 month or less during which Team delivers a potentially releasable software or solution. During the Sprint: - No changes are made that would endanger the Sprint Goal - Quality goals do not decrease - Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned Each Sprint may be considered a project with no more than a one-month horizon. Like projects, Sprints are used to accomplish something. Each Sprint has a goal of what is to be built, a design and flexible plan that will guide building it, the work, and the resultant product increment. Sprints are limited to one calendar month. When a Sprint's horizon is too long the definition of what is being built may change, complexity may rise, and risk may increase. Sprints enable predictability by ensuring inspection and adaptation of progress toward a Sprint Goal at least every calendar month. Sprints also limit risk to one calendar month of cost. The Product Owner focuses on the success of the product, ensuring the business value of it. Their main responsibility is to identify and refine the Product Backlog items. Product Owner is the voice of customer for Team and represents customer often. PO keeps product Backlog up to date and guides team on when to deliver what part of Product Backlog.

99

How do you identify potential risks and obstacles during the project?

Reference answer

I identify risks through daily stand-ups, retrospectives, and regular risk assessment sessions with the team. I encourage the team to flag any impediments early. I also look for patterns in historical data that might indicate recurring obstacles.

100

What is the purpose of the Daily Standup?

Reference answer

The Daily Standup is a short, focused meeting where the team discusses what they accomplished yesterday, what they plan to do today, and any obstacles they are facing. It helps the team stay aligned and ensures transparency about progress. Interview questions for Scrum Master usually dive into your experience with agile practices, how you handle roadblocks, and how you ensure the team's progress stays on track throughout the sprint.

101

How do you deal with a Product Owner who assigns user stories/tasks to the individual team members?

Reference answer

As part of a Scrum Master role, one of the responsibilities entails helping and coaching the Product Owner. It is really critical for the Scrum roles to understand their role and function accordingly. If the product owner is assigning the user stories/tasks, it is the job of a scrum master to make the product owner realize the meaning of self-organization. In the Scrum Guide, a partial definition of self-organizing is given as Scrum Teams are self-organizing. Self-organizing teams choose how to accomplish their work, rather than being directed by others outside the team.” Self-governance is one of the utmost motivators there is for people doing creative and problem-solving types of work. Assigning tasks to people is an implicit claim that the product owner knows better than the team, this not only passes on the wrong notion but it also lowers the morale of the team and at the same time defies the scrum values and Agile principle – “Point 5. Give them the environment and support they need, and trust them to get the job done.” And “Point 11. The best architectures, requirements, and designs emerge from self-organizing teams.” Hence, the product owner is assigning work, the Scrum Master should intervene and help the Product Owner in understanding the true sense of working in a Scrum framework and refrain him/her to continue this practice.

102

What is a Daily Scrum?

Reference answer

The Daily Scrum is a 15-minute event where developers synchronize work and plan for the next 24 hours. It improves: - Transparency - Alignment - Early risk identification

103

Can you describe a time when you had to deal with a team member who was struggling to meet their targets, and how you supported them to improve their performance?

Reference answer

In one case, a developer was struggling due to unclear requirements. I paired them with the Product Owner to clarify the story. I also arranged for them to work with a senior developer on a pair programming session. This provided both clarity and skill-building, improving their performance.

104

How can QA add value to an agile team?

Reference answer

QA can provide value addition by thinking differently about the various scenarios to test a story. They can provide quick feedback to the developers whether new functionality is working fine or not.QA is not a separate silo but is part of a cross-functional agile team. It is included in the project from the beginning, and the whole team works together on user stories using the same tracking tools. The Director of the QA team works closely with the executive management team to identify technology and staffing needs in relation to project pipelines. Quality Assurance is empowered to support projects and add value in whatever way the situation requires. Examples include design reviews, requirements assessments, browser and device support, process, tools, risk assessments, and helping to determine “Definition of Ready” and “Definition of Done.” QA sits with the project team whenever possible, allowing for increased conversation and problem-solving in real time. The QA team attends and contributes to all relevant planning meetings and sprint ceremonies and also work directly with clients on quality and testing processes. Members of QA teams always learn as individuals, as project team members, and as representatives of a skilled discipline within the organization. Our process and approach to testing evolve to keep up with advances in technology and the changing needs of clients. What works for one client or project might differ radically from another. Flexibility is the key.

105

How do you keep your team encouraged?

Reference answer

Besides performing daily tasks and managerial responsibilities, a scrum master is also accountable for maintaining peace and harmony within the team. Being an instructor and guide, you must know how you can help your team members resolve issues, establish strong relationships with one another, recognise each other's efforts and help each other grow. Remember, a good manager or supervisor is the one who identifies flaws to address them with clear communication and practical strategies. Additionally, to keep your team motivated, try to step into their shoes whenever you think there is an overwhelming situation and the team members need help. Try to consider their perspectives as well before you give out an opinion. Celebrate good times and achievements together, so that the team members also feel recognised and valued. Ensure a healthy, happy environment is maintained in your team always.

106

What Is Discussed During the Sprint Planning Meeting?

Reference answer

In a sprint planning meeting, any discussion mostly revolves around the work to be done in the future sprint and the process that will be followed to achieve that. This gathers the focus of the team to look into the ultimate objective of the project first, followed by the backlog that is to be cleared.

107

What techniques do you use to coach team members on Agile principles and practices?

Reference answer

I coach team members on Agile principles through hands-on workshops and interactive training sessions, ensuring they grasp the concepts effectively. Additionally, I provide one-on-one mentoring and use real-world examples to make the learning process more relatable and impactful.

108

How would you deal with last‑minute requirement changes?

Reference answer

I would assess the impact of the change and work with the Product Owner to prioritise it in the Product Backlog. If the change is urgent, I would adjust the Sprint Backlog to accommodate the new requirement, ensuring the team understands the impact on timelines and goals.

109

Can you give an example of how you helped a Product Owner refine their backlog?

Reference answer

Situation: A Product Owner struggled with an overloaded and disorganized backlog. Task: My goal was to help them streamline and prioritize the backlog effectively. Action: I coached them on techniques like user story mapping and MoSCoW prioritization. Result: This led to a more structured backlog, making it easier for the team to understand and implement the work.

110

What is a Definition of Done (DoD)?

Reference answer

The Definition of Done is a clear checklist that shows when a task or feature is fully complete. It ensures quality and sets shared expectations for delivery.

111

What are the five Scrum values?

Reference answer

The five Scrum values are commitment, focus, openness, respect, and courage. These values drive Scrum's success by making it more than just a series of processes, setting it apart from traditional project management approaches like Waterfall. They are important in a Scrum team as they foster trust, collaboration, and accountability, directly impacting team performance.

112

What are some common challenges that teams face when conducting demos?

Reference answer

Common challenges include incomplete or unstable features, lack of preparation, managing stakeholder expectations, technical difficulties, and difficulty keeping the demo focused on the product increment rather than the process.

113

How do you handle situations where the team faces resistance or reluctance to adopt new agile practices or methodologies?

Reference answer

Addressing resistance to new agile practices involves a combination of education, communication, and collaboration. I initiate discussions with the team to understand their concerns and perspectives, providing clear explanations of the benefits associated with the proposed changes. I organize training sessions or workshops to facilitate the learning and adoption of new practices, ensuring that team members feel confident in their application. Additionally, I leverage retrospective meetings to gather feedback on the effectiveness of new practices and make adjustments as needed. By fostering a culture of continuous improvement and involving the team in the evolution of their practices, we overcome resistance and promote successful adoption.

114

What does the Scrum Methodology consist of?

Reference answer

The Scrum Methodology consists of-

115

How do you manage conflict within the team?

Reference answer

Not all conflict is harmful. Healthy disagreement can lead to better decisions. Destructive personal conflict needs direct intervention. My approach involves addressing issues early, facilitating open communication, and mediating when necessary. What I avoid is ignoring conflict and hoping it disappears. Unaddressed conflict damages psychological safety and eventually affects the whole team.

116

What do you understand by DoD?

Reference answer

The DoD is commonly a brief record in the form of an agenda, that defines when a product backlog item (i.e. user story) is contemplated “done” before the team can start applying in the next sprint. It is a checklist of what needs to be done to a product backlog item which has many bases and countless ways to understand it: You need a general explanation of what “done” (“this user story is finished”) means. Else it will mean unique for every person on the team. - All your non-functional necessities reside in the DoD. - A usual list of acceptance criteria to be enhanced to every story's explicit acceptance criteria. - Many amendments you will find in your retrospectives end up in the DoD.

117

What branching strategies do you recommend for Agile teams?

Reference answer

I usually recommend simple branching strategies like Feature Branching or Trunk-Based Development, depending on the team size and project complexity. The focus is on maintaining a clean and manageable codebase with frequent merges.

118

Does the Scrum Master enforce the Scrum process?

Reference answer

The Agile methodology prioritizes 'People over Processes,' emphasizing individuals and interactions over rigid procedures. However, the Scrum Master's role involves facilitating the Scrum process to help teams achieve their goals effectively. Rather than enforcing the process, the Scrum Master motivates the team to embrace Scrum practices voluntarily. It's crucial to note that the Scrum Master's role is more about guidance and support than authoritarian enforcement. They assist the team in understanding the benefits of Scrum practices and encourage adoption through collaboration. The Scrum Master helps navigate obstacles and facilitates discussions, empowering the team to make informed decisions about following the Scrum framework.

119

What is the timebox for a Sprint?

Reference answer

One month or less.

120

What does a Scrum Master do on a daily basis?

Reference answer

My activities as a Scrum Master encompass three major areas: serving the Development Team, Product Owner, and serving the organization. In regard to the Development Team, I conduct the Daily Scrum, but that is just the beginning of my work. There is also a lot of effort that is required on my end in finding obstacles that are bound to slow my team down, whether they are process-related, technical, or even human relations issues. In cooperation with the Product Owner, I make sure that the Product Backlog is updated and that items coming up in the list are adequately prepared. This requires conducting and guiding Backlog Refinement sessions as well as assisting the Product Owner in writing clear and valuable user stories. For the organization, I am helping leaders grasp the effects of their decision-making on the agile ways of working. This may mean disseminating some metrics relating to team performance, teaching other stakeholders, or being a proponent of change in areas that would make more support for agility.

121

What do you understand by DoD?

Reference answer

The DoD is commonly a brief record in the form of an agenda, that defines when a product backlog item (i.e. user story) is contemplated "done" before the team can start applying in the next sprint. It is a checklist of what needs to be done to a product backlog item which has many bases and countless ways to understand it: You need a general explanation of what "done" ("this user story is finished") means. Else it will mean unique for every person on the team. - All your non-functional necessities reside in the DoD. - A usual list of acceptance criteria to be enhanced to every story's explicit acceptance criteria. - Many amendments you will find in your retrospectives end up in the DoD.

122

What is a Scrum of Scrums?

Reference answer

A scrum of scrums is a scaled agile technique that helps organizations connect their multiple teams to develop and deliver complex solutions. To get something done efficiently, we need integrated teamwork and a way to do that is through transparency, inspection, and adaptation combined with agile techniques because if you focus on delivering value instead of working in silos you can scale your projects much more effectively.

123

Are You Certified?

Reference answer

There are certifications for scrum masters, and that might be a prerequisite for your hiring decision. But it might not be, either. Some believe in certification, others less so, but either way, it's helpful to know a candidate's background. This is a way to open that door.

124

What are the key responsibilities of the Development Team (Developers)?

Reference answer

Designs, develops, tests, and delivers product increments, self-organizes work, ensures quality standards, collaborates with Product Owner, commits to Sprint goals.

125

How do you handle situations where team members resist adopting Scrum practices?

Reference answer

Addressing resistance to Scrum practices involves a combination of education, collaboration, and empathy. First, I seek to understand the reasons behind the resistance by engaging in open and honest conversations with team members. I then provide education on the benefits of Scrum, emphasizing how it can enhance collaboration, transparency, and overall project success. Collaboratively, we identify specific concerns and work towards solutions that address those concerns while staying true to Scrum principles. By fostering a culture of trust and demonstrating the value of Scrum through tangible outcomes, I've found that teams become more open to embracing agile practices.

126

Define the roles in Scrum?

Reference answer

Developers: The Scrum team includes developers to create a usable Increment each Sprint is done by developers. The Product Owner: The Scrum Team works on a product and then comes the role of the product owner. The product owner has the objective of maximizing the value of the product to the fullest. Scrum Master: The Scrum Master is responsible for the Scrum Team's effectiveness. Constant motivation and guidance to the Scrum Team to be proficient in its practices within the Scrum framework with explaining them the Scrum theory and general practices. So Scrum Master is a leader to leads the Scrum team effectively. A scrum master will combine and unite a project for the benefit of a common goal.

127

Can you give an example of successful Pair Programming implementation?

Reference answer

Situation: A project had complex features that needed high-quality code. Task: My goal was to implement Pair Programming to improve code quality. Action: I facilitated pairing of developers with complementary skills and organized workshops on effective pair programming techniques. Result: This led to improved code quality, reduced bugs, and enhanced knowledge sharing within the team.

128

How do you resolve conflicts within a Scrum team?

Reference answer

Here are some simple steps to be followed to resolve the conflicts within scrum team: - (Content not explicitly listed in the provided text beyond the introductory statement).

129

How do you coach a Product Owner?

Reference answer

Guide them in value-based prioritization, stakeholder engagement, and backlog clarity.

130

Describe a situation where you had to mediate a conflict within your team. How did you handle it?

Reference answer

The responses to these questions will provide insights into the candidate's ability to communicate effectively. Ideally, they'll demonstrate their active listening skills, ability to provide clear and concise information, and tact in giving feedback and handling conflict. Their ability to manage expectations and explain complex concepts well is crucial for successful Scrum implementation.

131

How would you handle a situation where your team is resisting a new technology or process?

Reference answer

I would first seek to understand their concerns and resistance. Then, I would provide training and resources to ease the transition, along with highlighting the benefits of the new technology or process.

132

What agile frameworks are you familiar with? What are your favorite features? Do they have any limitations?

Reference answer

The candidate should list agile frameworks they know (e.g., Scrum, Kanban, SAFe), highlight favorite features (e.g., Scrum's sprints, Kanban's flow), and discuss limitations (e.g., Scrum's rigidity for certain teams).

133

Can you give an example of a situation where you had to balance the needs of the team with the expectations of stakeholders or management?

Reference answer

Once, management wanted a feature delivered quickly, but the team was at capacity. I facilitated a meeting where the team presented the impact of adding the work, such as reduced quality or lower velocity. We negotiated a compromise by delivering a smaller scope first, balancing stakeholder needs with team sustainability.

134

Can you discuss how you handle conflicts or disagreements among stakeholders regarding the backlog?

Reference answer

I facilitate a discussion to understand each stakeholder's perspective and priorities. I help the Product Owner make the final decision based on the product vision and overall business value. If needed, I use data or user research to guide the conversation towards a data-driven decision.

135

Have you managed more than one team at a time?

Reference answer

The candidate should answer yes or no, and if yes, describe how they balanced responsibilities across multiple teams, managed competing priorities, facilitated cross-team coordination, and ensured each team received adequate support. If no, they can discuss their readiness to take on such a challenge.

136

What do you mean by Scrum of Scrums?

Reference answer

Scrum of Scrums is a scalable agile technique for connecting several teams that must collaborate to produce complicated solutions. It enables teams to design and deliver complicated products at scale by facilitating transparency, inspection, and adaption. It's especially effective when all members of a high-performing Scrum team work toward a single purpose, have complete trust and respect for one another and are completely aligned. It is a virtual team made up of delegates who are connected to the original delivery teams via embedded linkages. These interconnected team architectures simplify communication paths when compared to traditional organizational hierarchies or project-based teams. The goal is to coordinate smaller, self-contained groups.

137

What is technical debt?

Reference answer

Technical debt refers to shortcuts in development that may speed up delivery initially but create future maintenance costs.

138

How do you handle situations where external stakeholders request changes outside the scope of the current sprint?

Reference answer

When external stakeholders request changes outside the scope of the current sprint, I follow a transparent and collaborative approach. First, I communicate with the stakeholders to understand the urgency and impact of the requested changes. If the changes align with the overall project goals and won't compromise the current sprint's objectives, I work with the Product Owner to evaluate the feasibility of incorporating the changes. However, if the changes pose a risk to the sprint goal or would require a significant adjustment of priorities, I guide the stakeholders to prioritize the requests for consideration in the upcoming sprints. It's essential to balance flexibility with maintaining the team's focus on delivering a cohesive increment during each sprint.

139

What are the key responsibilities of a Scrum Master?

Reference answer

This is a crucial question to display how well the candidate understands the responsibilities of the role they're interviewing for. It will also provide insight as to how experienced they are in the industry. Listen for: An understanding of and respect for Scrum's rules, values and principles. You'll want to learn how they remove distractions from their work environment and ensure their team delivers real value. They should also put a focus on leading their team, not managing. They understand their role is to manage roadblocks to make sure their team stays productive.

140

What is a Product Backlog?

Reference answer

The Product Backlog is a prioritized list of features, enhancements, and fixes required to build the product. It is owned and managed by the Product Owner and continuously refined.

141

Is Scrum and Agile the same? If not so, differentiate between them.

Reference answer

No, Scrum and Agile are not the same. Following are the differences between them: | Agile | Scrum | |---|---| | Agile is a development methodology that takes an incremental and iterative strategy. | Scrum is one of the agile methodology's implementations. In this scenario, the customer receives incremental builds every two to three weeks. | | Agile software development has long been seen to be best suited to situations with a small but highly skilled project development team. | Scrum is best suited for projects with quickly changing requirements. | | It is a more rigid method when compared to Scrum. As a result, there isn't a lot of room for regular modifications. | Scrum's greatest benefit is its adaptability. | | Agile entails cross-functional collaborations and face-to-face interactions between team members. | Collaboration is achieved in Scrum by holding daily stand-up meetings in which the scrum master, product owner, and team members each have a specific role to play. | | Agile development can necessitate a significant amount of up-front process and organizational change. | When implementing the scrum process, there aren't many adjustments that need to be made. | | The design and implementation should be kept as simple as possible. | Innovative and experimental design and execution are possible. | | The most basic indicator of progress is working software. | Working software is not a basic criterion. |

142

Product Owner doesn't have any experience in Agile methodologies. He used to manage Waterfall projects. He doesn't want to participate actively in Scrum events like Sprint Planning, and Sprint Review and be available for Dev Team during Sprints. What would you do to make sure the Scrum process is being applied?

Reference answer

The candidate should describe coaching the Product Owner on Agile values, explaining the importance of their role in Scrum events, facilitating initial sessions to demonstrate value, setting clear expectations for collaboration, and escalating if necessary to ensure the Product Owner understands their responsibilities in supporting the team.

143

Benefits of Agile:

Reference answer

The perspective for Customer: When the customer takes a lookout in the market as for going with which technique for Software Development process, Agile Methodology stands perfectly for the need and outreach for the Customers. The Agile Methodology is more responsive to the customer's request. Not only it gives the customer high valued features but also delivers more quickly with short cycles. The Benefit for the development team: Agile has a great role in making a good working environment. It makes the work process very smooth and makes the team enjoy development work. This helps to generate more good output. With Agile Methodology, their work is valued and more quality product is delivered. It also helps in reducing non-productive work. The Benefits for Scrum Master: As a Scrum Master, one needs to have good knowledge of Agile Methodology and how to implement the method into Scrum Framework. Agile gives a process for Scrum Master by virtue of which they can easily plan and track task in daily meetings. Agile gives the Scrum Master a good sense of approach and awareness towards the project state and status. The Agile Method also helps the Scrum Master to react to blockages quickly and address them. The Benefits for Product Owner: As a product owner, one predicts to have a good sense of approach for the work process so as to get a product of high values. The Agile development method the product owner to develop work aligns with customer needs. As it gives a product of high quality and highest possible values, it gives a good scope to them for a good approach. The Perspective for Vendor: As a vendor, with the help of Agile Methodology, one gets focused development on high-value features with increased efficiency It also helps them to reduce wastage and decreases the overhead.

144

What is a Scrum Sprint, and what is its ideal duration?

Reference answer

A Scrum Sprint is a fixed period of time during which a specific set of work is completed and made ready for review. It's essentially a mini-project within the larger project, where the team focuses on delivering a specific set of features or improvements. The ideal duration of a Scrum Sprint is 1 to 4 weeks, with 2 weeks being the most common.

145

Explain the pillar of Transparency in Scrum.

Reference answer

Transparency - Transparency is essential when implementing a process in any sort of business. This prevents any miscommunication from occurring that could result in the product not meeting its intended criteria. It's important for all participants working on the end goal to refer to their actions in the same terms.

146

What is the difference between a sprint goal and user stories?

Reference answer

A sprint goal is the single objective that ties the entire sprint together—it's the why behind the work. For example, ‘Improve checkout experience for mobile users' is a sprint goal. User stories are the individual pieces of work that contribute to that goal. You might have three or four user stories like ‘As a mobile user, I want to see my saved payment methods' or ‘As a mobile user, I want one-click checkout.' The sprint goal keeps the team aligned on purpose, whereas user stories break down how we're going to achieve it. During sprint planning, I make sure the team can articulate the goal first, and then we pull in stories that support it. If a story doesn't support the sprint goal, we question whether it belongs in the sprint.

147

What are the three daily Scrum questions, and should they be asked in the daily Scrum?

Reference answer

The standard three daily Scrum questions are as follows: - What did you do yesterday? - What do you plan to do today? - Are there any impediments that block your progress? The three daily Scrum questions were removed in the 2020 Scrum Guide -- not because they are bad or ineffective, but because teams shouldn't feel obligated to ask and answer them every day. Developers on the team should determine the format and structure of the daily Scrum. The goal of the daily Scrum is to inspect progress and, if necessary, adapt the Scrum plan to ensure the sprint goal remains in focus. If those three daily Scrum questions help developers achieve that end, then they are well within their rights to ask them. However, if the team has other effective strategies to keep the sprint plan on track, they shouldn't feel that asking the three daily Scrum questions is a requirement.

148

What is the Scrum Master's role in the Sprint Retrospective?

Reference answer

In the Sprint Retrospective, the Scrum Master plays a crucial role in facilitating open and constructive discussions, ensuring that the team reflects on the sprint and identifies ways to improve. They create a safe, supportive environment where team members feel comfortable sharing insights about what went well, what didn't, and potential improvements. The Scrum Master guides the conversation to help the team focus on actionable items, encourages collaborative problem-solving, and helps prioritize changes for the next sprint. The Scrum Master ensures that any agreed-upon improvements are documented and followed up on, fostering a culture of continuous improvement within the team.

149

How do you implement a Kanban system in an Agile environment?

Reference answer

Implementation involves setting up a Kanban board that mirrors the team's workflow, establishing WIP limits for each stage, and continuously monitoring the flow of work to identify and address bottlenecks.

150

What is the role of a Scrum Master?

Reference answer

For Scrum, we need a Scrum Master. To improve the profession of software delivery, the role of SCRUM Master comes into the picture. They are: - For a complex issue, a product owner orders the work into a Product Backlog. - Design of the framework with added value is done by the Scrum team. - The outcome is measured by the Scrum team and its stakeholders. - Repeat

151

How is estimation in a Scrum project done? What are the techniques used for estimation?

Reference answer

Estimation can be done using any available estimation techniques such as Function Points, Wideband Delphi etc. and Scrum has no recommendation for this. However a relative estimation technique like Planning Poker estimation has been widely used across multiple companies and is very popular.

152

How do you handle conflicts within the Scrum team?

Reference answer

Resolving conflicts within the Scrum team is vital for maintaining a healthy working environment. I approach conflicts by first facilitating an open dialogue among team members to understand perspectives. Then, I identify the root cause of the conflict and work collaboratively to find a mutually agreeable solution. It's crucial to foster a culture of transparency and continuous improvement, encouraging team members to express concerns and collaborate on finding resolutions.

153

How do you handle disagreements within the Agile team?

Reference answer

I encourage open communication and a collaborative approach to conflict resolution. Understanding each team member's perspective and finding a middle ground that aligns with project goals is my strategy.

154

What is a cross-functional team?

Reference answer

A cross-functional team has all skills required to deliver a product increment without external dependencies.

155

What is your approach to Sprint planning?

Reference answer

My approach involves ensuring the Product Backlog is well-defined and prioritized. During Sprint Planning, I facilitate discussions to determine the Sprint Goal and select Backlog items that align with this goal, ensuring the team understands the scope and is committed to the Sprint objectives.

156

Can you tell me about a time when you had to mediate a conflict within your team? How did you approach it, and what was the result?

Reference answer

Look for responses that demonstrate a systematic approach to problem-solving. These include identifying the issue, analyzing it, devising a plan, implementing it, and reviewing the results. The candidate should also show an ability to deal with ambiguity and make decisions with limited information.

157

Can you discuss your experience with remote or distributed Scrum teams and the challenges you faced?

Reference answer

In my experience with remote Scrum teams, I utilized tools like Slack and Zoom to maintain constant communication and foster collaboration. One challenge we faced was time zone differences, which we overcame by implementing flexible meeting schedules and asynchronous updates.

158

What are the primary tools utilized in a Scrum project?

Reference answer

There are many primary tools utilized in a Scrum project, including: [not explicitly listed in the text, but implied from context]

159

What is a WIP limit?

Reference answer

Work-in-Progress (WIP) limit restricts the number of tasks in progress to improve flow and reduce bottlenecks.

160

What do you know about Scrumban?

Reference answer

Scrumban is a hybrid of Scrum and Kanban. It combines: - Scrum's structure (Sprints, roles, planning) - Kanban's flow-based approach (visual boards, limiting work in progress) - Scrumban is useful for teams transitioning from Scrum to a more flexible workflow.

161

Can you walk me through the process of preparing for a demo?

Reference answer

Preparation involves the team identifying which completed items to demonstrate, rehearsing the presentation, setting up the environment to ensure a smooth demo, and inviting the right stakeholders. The Scrum Master helps coordinate this preparation and ensures the team is ready.

162

What is the difference between MVP and MMP?

Reference answer

The Minimum Viable Product (MVP) is a concept rooted in the Lean Startup methodology. It emphasizes learning during product development by introducing an initial version to target customers and users. This approach aims to gather direct feedback and data from its users. The primary objective of an MVP is to release a basic version of the product, gauge user reactions, and gather insights about their preferences and needs. The Minimal Marketable Product (MMP), on the other hand, is a version of the product with the fewest features but still meets user needs and requirements. MMP aims to expedite the product's launch in the market while ensuring it remains valuable to its target audience.

163

What do you understand by product backlog in Scrum?

Reference answer

A Scrum product backlog can be explained as a list or menu that includes all the activities that need to be done in the project. The items on this list can be technical or user-centric.

164

What is the difference between Sprint Review and Sprint Retrospective?

Reference answer

Sprint Review focuses on the product, while Sprint Retrospective focuses on the process. Sprint Review is concerned primarily with optimizing and maximizing product value, whereas Sprint Retrospective is involved with people, processes, and tools.

165

How do you ensure that team members have the resources and tools they need to do their jobs effectively?

Reference answer

I regularly check in with the team about their tooling and resource needs. I proactively identify potential bottlenecks, such as slow build servers or missing licenses, and work with management to acquire what is needed. I also encourage the team to raise issues early.

166

What kind of metrics do you use to track the progress of a sprint?

Reference answer

Common metrics include velocity (story points completed per sprint), burndown charts (remaining work over time), cumulative flow diagrams, lead time and cycle time, sprint goal success rate, and defect density. The candidate should explain how these metrics help the team inspect and adapt their process.

167

What would you do if the Product Owner is unavailable during a Sprint?

Reference answer

If the Product Owner is unavailable, I work with the team to ensure that they can continue making progress. I ensure the team has enough information to move forward and, if necessary, I facilitate communication with other stakeholders to keep the work moving. Be ready to answer scrum master questions on how you handle conflicts, support continuous improvement, and drive the team towards the sprint goals.

168

Recall a time when you had to manage a project with limited resources.

Reference answer

Situation: Assigned to a project with constrained resources. Action: Prioritized the project deliverables, optimized team workload, and negotiated additional resources. Result: Successfully completed the project by maximizing the efficiency of available resources.

169

How do you handle scope creep during a sprint?

Reference answer

Scope creep happens when urgent requests come in during the sprint. My approach is to never say no outright, but to help the team understand trade-offs. When someone asks to add work mid-sprint, I ask: ‘If we do this, what should we pull out to stay at our committed velocity?' Usually, that question alone makes people reconsider whether the urgent thing is truly urgent. If it really is, we decide together what doesn't make the sprint. I also make sure the Product Owner is the gatekeeper—they're making the call on priorities, not me or the team on our own. In one case, an executive asked us to jump on a production bug mid-sprint. Instead of just pulling the team off their work, I said, ‘Let's talk through the impact.' We realized it could wait until the sprint ended, and it freed up the team to finish their sprint goal. That's better for everyone.

170

What is the difference between Agile and Scrum?

Reference answer

Agile is a set of values and principles for iterative, customer-focused delivery. Scrum is one specific framework that implements Agile principles in practice.

171

Your team keeps missing commitments, and its performance velocity is unpredictable. What could be the reasons? How would you tackle this issue?

Reference answer

Possible Reasons: - Overcommitting. - Poor backlog refinement. - Technical debt. Solutions: - Improve backlog refinement. - Use realistic estimates. - Encourage better collaboration.

172

How do you facilitate the communication and collaboration among the team members during Sprint planning?

Reference answer

I encourage open dialogue by asking clarifying questions and ensuring everyone has a chance to speak. I use facilitation techniques like brainstorming, estimation games, and visual aids to keep the session interactive. I also manage the discussion to prevent it from devolving into unproductive arguments.

173

How do you support team members who may be struggling with work-life balance or other personal challenges?

Reference answer

I have an open-door policy and encourage team members to speak with me confidentially. I advocate for flexible working arrangements when possible and remind them of company resources like EAP (Employee Assistance Programs). I prioritize their well-being over short-term productivity.

174

How do you estimate user stories – hours, days, or story points? Why?

Reference answer

User stories are usually estimated using story points, which measure effort, complexity, and uncertainty. Story points provide a relative estimate, allowing the team to compare stories more easily. It also focuses on effort rather than time, promoting better planning and tracking across sprints.

175

How do you prioritize your workload and stay organized?

Reference answer

This is a big question to answer but nonetheless an important one to ask! Your Scrum Master candidate should display prioritization and smart multi-tasking skills. Additionally, they should be able to identify tools and techniques to maintain organization. Listen for: Their ability to prioritize their workload, manage their time well, delegate to their team and communicate to stakeholders.

176

What are the three C's in an User Story?

Reference answer

Following are the three C's in a User Story: - Card: It is a written account of the story that is utilized to plan and estimate. To keep user stories succinct, they are manually written on index "cards." - Conversation: The Conversation is required to learn more about the Card. The conversation encourages the agile team to work together in small steps to develop a shared understanding of the problem and potential solutions. - Confirmation: Confirmation is an acceptance criteria that contains the fundamental requirements and turns them into test criteria so that we can determine when the user story has been properly provided.

177

Can you give an example of a situation where you helped resolve a misunderstanding between the team and the Product Owner?

Reference answer

Look for answers indicating a candidate's understanding of what causes conflicts and the strategies they should use to manage disagreements effectively. Candidates should provide real-life examples demonstrating their ability to mediate disagreements, clarify misunderstandings, and create a harmonious working environment. They should show how they've used their skills to maintain team productivity and project momentum in the face of conflicts.

178

The manager of the team is anxious about how the team is doing and asks you to invite him into your retrospective from now on so that he knows what problems there are. How do you respond?

Reference answer

Firstly, why is the manager anxious? There must be a reason for him to be stressed about the team's performance or something else. So the first thing for me to do is to discuss with the manager in more detail what information exactly is he trying to get from the retrospective. There might be other ways to get that information in a more appropriate manner. I would also explain that the retrospective is the Scrum Team internal meeting where no external people are invited. It has to be a safe environment where people feel free to speak up and raise concerns. Having a manager in the room may have a negative impact on it. So the team members may refrain from bringing the real issues to the table and hence make the retrospective much less productive. I would also check with the team if they are willing to share their retrospective notes with the manager. However, if they don't feel comfortable doing so, then I must respect their decision.

179

What techniques do you use to track progress and identify potential roadblocks during the daily stand-up meetings?

Reference answer

I use visual management tools like task boards (physical or digital) to track progress. During the stand-up, I listen for inconsistencies between reported progress and board status, and I ask clarifying questions to uncover hidden roadblocks or dependencies.

180

What do you understand by the term "protecting the team" in Scrum?

Reference answer

Protecting the team means shielding them from external interruptions, distractions, and pressures that could disrupt their focus and productivity during the Sprint. It also involves ensuring they have a safe and supportive environment to work in.

181

Q #13) What are the roles of the Scrum Master and Product Owner?

Reference answer

Scrum Master acts as a Servant Leader for the Scrum team. He presides over all scrum ceremonies and coaches the team to understand and implement scrum values and principles. The scrum master helps facilitate the scrum process and removes any impediments that will impact the delivery of the scrum team. Scrum Master also helps the team and the overall organization understand the Scrum process and helps in its adoption. Product Owner is the point of contact for the Scrum Team. He/she is the one who works closest to the business. The main responsibility of a product owner is to identify and refine the product's backlog items. The product owner will own, develop, and maintain the product backlog.

182

How do you facilitate effective feedback and discussion during retrospectives?

Reference answer

I use a structured format to guide the discussion, such as 'Start, Stop, Continue.' I encourage everyone to speak by using silent writing or small groups. I ask probing questions to dig deeper into issues and ensure the feedback is specific and actionable.

183

What is Sprint Backlog?

Reference answer

A sprint is a restricted period, generally 2–4 weeks, during which a team of developers works to finish a specific set of tasks. At the end of the sprint, the objective is to have a functional increment of software. A Sprint Backlog is a list of work that a team of developers intends to perform over a specified period is known as a Sprint. A Sprint usually lasts two to four weeks, during which time the team works to finish a certain set of tasks. The Sprint Backlog in Agile methodology is produced during the Sprint Planning meeting, where the team picks the items from the Product Backlog that they will work on during the Sprint. The Product Backlog is a prioritized list of features, enhancements, and bug fixes that the team must achieve within the project's duration. The Sprint Backlog is a dynamic document that is updated throughout the Sprint. It is used by the team to track their progress, make modifications, and ensure that they are on pace to finish the task inside the Sprint. Each item on the Sprint Backlog should be split down into smaller tasks so that the team may work on them in a more manageable manner. These tasks should be short enough to be done in a day or two and assigned to individual team members.

184

Describe a problem/risk you identified early on. What steps did you take to resolve the problem?

Reference answer

The candidate should describe a specific problem or risk they identified early, the steps they took to resolve it, and the outcome.

185

How much time should a person expect to spend on Scrum Master activities?

Reference answer

A Scrum Master should make this role their top priority to focus on the benefits of the overall Scrum team. Their load will vary from sprint to sprint depending on what impediments and issues the team is dealing with. Newly formed teams typically take more Scrum Master time, 50–100 percent; while experienced Scrum Masters with established well-functioning teams might spend 50 percent or less time on the Scrum Master role.

186

How do you facilitate the integration of new team members into an existing Scrum team?

Reference answer

Integrating new team members into an existing Scrum team is a crucial aspect of fostering collaboration and maintaining productivity. I start by providing comprehensive onboarding materials, including documentation on team processes, coding standards, and project specifics. Additionally, I encourage pair programming and mentorship to facilitate knowledge transfer. During sprint ceremonies, I ensure that new team members feel comfortable expressing their perspectives and contributing to discussions. By creating a welcoming environment and promoting a culture of shared responsibility, we enable a smooth integration process that minimizes disruptions to team dynamics and productivity.

187

What is Sprint 0 in Scrum?

Reference answer

Sprint 0 is not officially a part of Scrum. Teams sometimes use it to prepare for the actual sprints. It may involve initial project setup, gathering requirements, creating the initial backlog, setting up development environments, and planning. However, in pure Scrum, the focus is typically on delivering potentially shippable increments of the product starting from Sprint 1.

188

Q #32) How do you calculate a story point?

Reference answer

A story point is calculated by taking into consideration the development effort + testing effort + resolving dependencies and other factors that would be required to complete a story.

189

What is servant leadership in the Scrum context?

Reference answer

Leading by serving others, removing blockers, and enabling team growth.

190

Who is a Scrum Master? And what does he/she do?

Reference answer

A Scrum Master is someone who promotes and supports the usage of Scrum within the team. • He/She understands the theory, practices, rules and, values of Scrum • He/She ensures that the team follows the values, principles and, practices of Scrum • They remove any distractions and impediments that hamper the progress of the project • The Scrum Master ensures that the team delivers value during the sprint

191

How do you handle fatigue in Retrospectives?

Reference answer

To prevent fatigue in retrospectives, I keep them short and engaging by changing the format, including interactive activities, and encouraging everyone's participation. It's important to maintain energy levels and make the retrospectives something the team looks forward to rather than a chore.

192

What is the similarity between Agile and Scrum?

Reference answer

Scrum is a framework within Agile. Both share core principles such as: - Iterative development - Customer collaboration - Adaptability - Continuous improvement

193

Can you name the Scrum process's three key artifacts?

Reference answer

Scrum's three key artifacts are: - Sprint Backlog - Product Backlog - Product Increment.

194

How do you ensure that the Scrum team maintains a balance between individual autonomy and collaborative decision-making?

Reference answer

Maintaining a balance between individual autonomy and collaborative decision-making involves recognizing the strengths of both approaches and adapting to the needs of the team. I encourage team members to take ownership of their tasks and make individual decisions within their areas of expertise. During collaborative decision-making situations, such as sprint planning or refinement meetings, I facilitate discussions that allow the team to collectively make decisions and share insights. I emphasize the importance of clear communication and alignment with overall project goals. By fostering a culture that values both individual autonomy and collaboration, we create a dynamic environment that leverages the strengths of each team member.

195

Explain velocity in Agile.

Reference answer

Velocity is a metric that is calculated by the addition of all effort estimates associated with user stories completed in one iteration. It predicts how much work Agile can complete in a sprint and how much time it will require to complete a project.

196

What is the major advantage of using Scrum?

Reference answer

- Early & continuous feedback which fosters inspect & adapt - Early delivery to markets - Increases communication between business and implementer reducing the scope for defects - Technology and business are aligned and hence cost reduction

197

What are the key responsibilities of a Scrum Master?

Reference answer

Ensures Scrum framework is followed, facilitates Scrum ceremonies, removes impediments, coaches the team on Agile practices, protects the team from external distractions.

198

Tell me about a time you made a mistake in your role and how you handled it.

Reference answer

The goal of this question is to learn how a Scrum candidate handles mistakes in their role. The truth is, mistakes are inevitable — communication may break down, team members may run into issues or details may be missed. What you're looking for in a candidate is how they deal with those roadblocks to come out on top. Listen for: A real-world scenario. You want to hear that they displayed sound judgment, applied logic to the situation, and collaborated with their team to resolve the problem.

199

What are traits of a good scrum master?

Reference answer

- A servant leader - Who puts teams needs ahead of his/her - Who fosters leadership in team - A good impediment resolver - Patient listener - Coach to individuals and team - A protector for team - An effective facilitator

200

How do you handle differing opinions among team members on addressing a problem?

Reference answer

When team members have differing opinions on addressing a problem, applying Scrum principles can be instrumental in finding a solution. Fostering productive communication during key meetings such as sprint planning or daily stand-ups is essential. Furthermore, organizing time-boxed workshops and brainstorming sessions can facilitate collaboration and consensus-building among team members.

DON'T WANT TO MISS A THING?

Latest Cisco, PMP, AWS, CompTIA, Microsoft Materials on SALE
Get Now

Basic to Advanced Scrum Master Interview Questions | SPOTO

Earn a certification to make your resume stand out.

DON'T WANT TO MISS A THING?

Latest Cisco, PMP, AWS, CompTIA, Microsoft Materials on SALE Get Now

Basic to Advanced Scrum Master Interview Questions | SPOTO

Earn a certification to make your resume stand out.

Latest Cisco, PMP, AWS, CompTIA, Microsoft Materials on SALE
Get Now