1

Resposta de referência

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.

2

Resposta de referência

A Minimum Viable Product is a product that has just the bare minimum required features which can be demonstrated to the stakeholders and is eligible to be shipped to production.

3

Resposta de referência

Cycle time measures the time taken from starting work on an item to completing it.

4

Resposta de referência

Demos are typically held once at the end of each Sprint during the Sprint Review event. The frequency aligns with the Sprint cadence, so if Sprints are two weeks long, demos occur every two weeks.

5

Resposta de referência

A user story is a tool used in Agile software development that captures the description of a feature from an end-user perspective. It describes, among others, the type of users and their motivations. A user story creates a simplified description of a user's requirements.

6

Resposta de referência

I use data, such as the team's velocity and capacity, to communicate realistic expectations. I facilitate conversations where the team can explain their constraints and negotiate scope. I do not commit the team to work they cannot realistically deliver.

7

Resposta de referência

Ask this question to get a sense of what your candidate enjoys most about being a Scrum Master and also how they might stay up to date on the latest industry trends. They may also mention something they've recently learned about being a Scrum Master. Listen for: A sense of passion in their response. An ideal candidate enjoys what they do and should also see that there is always room to learn and grow in their career.

8

Resposta de referência

The candidate should explain the advantages (e.g., improved communication, quick issue identification) and disadvantages (e.g., potential for long meetings, lack of focus) of the daily stand-up meeting.

9

Resposta de referência

During the formation of the team, we collaboratively define roles and responsibilities. I also refer to the Scrum framework to clarify that the team is self-organizing. I regularly revisit these roles during retrospectives to ensure clarity and alignment.

10

Resposta de referência

It is recommended to have 2—4 weeks in the sprint cycle.

11

Resposta de referência

I empower the team to make decisions about how to do their work. I avoid assigning tasks and instead let them self-select. I hold the team collectively accountable for the Sprint goal, which encourages each member to take ownership of their contributions.

12

Resposta de referência

A proficient Scrum Master should explain strategies for avoiding these pitfalls through rigorous risk management and constant engagement with key stakeholders. This involves regularly updating the product manager and agile coach about progress in the current sprint and plans for the upcoming sprint. Effective use of the Agile framework and principles, such as the pillars of the scrum, ensures that each step, from product discovery to new sprint planning, aligns with the teamâs goals and experience level.

13

Resposta de referência

The candidate should explain that Waterfall is preferable for projects with well-defined, fixed requirements and little expected change, as it follows a sequential, phase-based approach. Kanban is better suited for teams dealing with continuous, variable workloads and high priority changes, as it focuses on workflow visualization and limiting work in progress without fixed timeboxes. Scrum is ideal for complex projects where requirements evolve and incremental delivery is needed.

14

Resposta de referência

Key focus areas include: - Clear communication protocols - Visual collaboration tools - Time-zone overlap windows - Written documentation standards - Strong facilitation discipline

15

Resposta de referência

A Burndown Chart shows how much work remains in a sprint plotted against time. The ideal line runs diagonally from total sprint work on day one to zero on the last day. If the actual line stays above the ideal line, the team is behind pace. If it drops sharply early, the team may have overestimated scope or not accounted for dependencies.

16

Resposta de referência

First thing, we will not mark the story as done. We will first confirm the actual requirement from the stakeholder and update the user story and put it into the backlog. Based on the priority, we would pull the story in the next sprint.

17

Resposta de referência

There are 3 main roles in a scrum: - Scrum Master: Helps facilitate the scrum process and events - Product Owner: Maintains the product backlog and is the interface between the scrum team and the end-user. - Scrum Team: Self-organizing and self-sufficient team to deliver the sprint goal. Scrum team generally consists of one product owner, one scrum master, and developers (sometimes separate testers and BA). There are no hierarchies in a scrum team.

18

Resposta de referência

If a team resists Scrum, I would listen to their concerns, address any misconceptions, and provide training or resources to help them understand the benefits of Scrum. I'd also start with small wins to show how Scrum practices improve efficiency, helping them gradually adopt the framework.

19

Resposta de referência

Candidates should be able to articulate their favorite Scrum event and explain its significance. Effective candidates will likely highlight events such as Sprint Planning, Daily Scrum, or Sprint Review, emphasizing their impact on team collaboration, transparency, and adaptability. This insight provides valuable context for evaluating their approach to facilitating Scrum events within a team environment.

20

Resposta de referência

Situation: Tasked with a project identified as high-risk due to its technical complexity and tight deadline. Action: Conducted thorough risk assessment, implemented stringent risk mitigation strategies, and increased communication with stakeholders. Result: Successfully delivered the project with minimal issues, on time and within budget.

21

Resposta de referência

I ensure timely delivery by setting clear deadlines, tracking progress in daily stand-ups, and holding the team accountable. I also work to remove any impediments that might delay progress, ensuring that the team has everything they need to meet deadlines.

22

Resposta de referência

A Product Owner has the authority to cancel a Sprint.

23

Resposta de referência

The progress is tracked by a "Sprint Burn-Down chart".

24

Resposta de referência

The user story obviously does not meet the definition of ready and could be refused by the team. However, Agile promotes people over process and thus other factors should be evaluated as well. Has the design team consistently met their deadlines in similar situations? Is there evidence that this user story of very high value to the client? In these circumstances, the team could make an exception and accept the story. However, it is important for the Scrum master to have a talk with the product owner and make sure that such exceptions do not become the rule. definition of ready is a valuable technique and ignoring it can derail the scrum team's efficiency and increase the risk of delays.

25

Resposta de referência

In one project, the team identified that too many context switches were hurting productivity. An action item was to establish a 'focus time' block with no meetings for the team. This simple change led to a measurable increase in velocity and team satisfaction.

26

Resposta de referência

Regularly working with the Product Owner to prioritize and refine the backlog is key. This helps in focusing on high-value items and keeping the backlog manageable and relevant.

27

Resposta de referência

The purpose of Sprint planning is to define what can be delivered in the upcoming Sprint and how that work will be achieved. It is important because it aligns the team on a shared Sprint goal, sets realistic expectations, and creates a plan that guides the team's work for the Sprint.

28

Resposta de referência

I tailor the meeting by considering the team's size, location (co-located or distributed), and the project's phase. For distributed teams, I might use video conferencing and collaborative tools. I also adjust the questions or structure based on team feedback to maximize relevance.

29

Resposta de referência

The product backlog is a list that contains and prioritizes the details of every little task you require to include in your product. If you want to make any changes to your product, then product backlog is the only source of requirements. Whereas, a Sprint Backlog is a list of tasks finalized by the Scrum team to work on during the current sprint.

30

Resposta de referência

Balancing innovation and meeting project deadlines requires a strategic approach that values creativity without compromising on delivery timelines. I allocate dedicated time for innovation within sprint planning, allowing the team to explore new ideas or technologies. During retrospective meetings, we discuss the balance between innovation and meeting deadlines, ensuring that the team's efforts align with project goals. Additionally, I work closely with the Product Owner to prioritize innovative features while maintaining a focus on delivering essential functionality within the agreed-upon timelines. By fostering a culture that values both innovation and project timelines, we strike a balance that enhances the team's creativity and productivity.

31

Resposta de referência

A Scrum Master is not required to be present; all that is required of him or her is that the Development Team has a Daily Scrum. Only Development Team members are allowed to participate in the Daily Scrum. Although the Scrum Master or Product Owner is welcome to attend this meeting to help with the Daily Scrum, Scrum does not necessitate it. During the Daily Scrum, the Development Team members synchronize their work, track their progress toward the Sprint Goal, and, if necessary, adjust the Sprint Backlog and the plan for the following 24 hours.

32

Resposta de referência

I use both quantitative techniques (e.g., analyzing burndown charts, cycle time) and qualitative techniques (e.g., observing collaboration, gathering feedback). I avoid using metrics for individual evaluation and instead use them to help the team improve its process.

33

Resposta de referência

The responsibility for resolving technical issues the development team identifies lies with the team itself. They are accountable for executing development tasks and achieving the Sprint Goal, including addressing any technical challenges within their realm of influence. The Scrum Master intervenes to address impediments that exceed the scope of the development team's control.

34

Resposta de referência

The purpose of daily stand-up meetings is to synchronize the team's activities, identify any impediments, and plan the next 24 hours of work. They are essential for promoting transparency, collaboration, and quick problem-solving, ensuring the team stays aligned with the sprint goal.

35

Resposta de referência

I believe in recognizing individual and team efforts, encouraging professional growth, and maintaining a positive work environment. Regular feedback and celebrating successes also play a key role in keeping the team motivated.

36

Resposta de referência

The term “Scrum of Scrum” is a Scaled Agile methodology, mainly used when required to coordinate with various teams to collaborate on complex assignments. This ensures transparency, adaption, adoption, and collaboration are established, and products are timely delivered.

37

Resposta de referência

Situation: A project was at risk of delay due to unresolved dependencies. Task: It was crucial to address these dependencies swiftly. Action: I organized a focused session with the involved teams to realign priorities and resources. Result: This led to a timely resolution of dependencies and kept the project on track.

38

Resposta de referência

Timeboxing implies the distribution of a set time unit for operation. However, the time is spent regardless of the outcome. This promotes consistency and predictability and provides a condition for examination and adaptation. Any Scrum case is time-packed and doesn't have to be stretched like Sprint, Regular Scrum, etc.

39

Resposta de referência

The first critical issue for the majority of newly formed Scrum Teams is the existing legacy Product Backlog. Answers to this question need not reference Tuckman's team development stages (see Question 28), additional team-building exercises, or any kind of Scrum training or workshop not concerned with the Product Backlog. It is a rare occasion for a Scrum Master to start from scratch with a brand new team and no existing product — even more so in a nascent organization like a startup. Most often, it's an existing product delivery organization with existing products and services that will 'go agile'. For these cases, your candidate should point out that refining the legacy Product Backlog is the practical first step. The legacy Product Backlog per se is an interesting artifact because it provides a comprehensive insight into the product delivery organization's history: this particular Product Backlog allows for identifying organizational debt, process insufficiencies, questionable product decisions, and other anti-patterns. Looking at a legacy Product Backlog, an excellent candidate will be able to point out some of these anti-patterns (e.g. outdated or poorly maintained tickets), and provide a good idea about how to transform the legacy Product Backlog into a well-refined, current Product Backlog such that a new Scrum Team could work with. Candidates should mention that running Product Backlog refinement workshops creates a good opportunity to provide a new Scrum Team and Product Owner hands-on training with Scrum. This is because a Product Backlog refinement workshop will typically cover user story creation, knowledge transfer among team members, the estimation process (if applicable), introductory agile metrics, technical debt analysis, and other topics critical to the success of Scrum.

40

Resposta de referência

Talk about how you'd improve communication with stakeholders, ensure the backlog reflects real value, and use reviews or demos to gather better feedback. Show that you care about customer satisfaction, not just internal metrics.

41

Resposta de referência

Yes, apart from Scrum, Agile includes: - Kanban – Focuses on visual workflow management and limiting work in progress. - Extreme Programming (XP) – Emphasizes frequent releases, continuous integration, and test-driven development. - Lean Agile – Eliminates waste while improving efficiency. - SAFe (Scaled Agile Framework) – Used for large organizations to implement Agile at scale.

42

Resposta de referência

It's central to learning cycles — I create feedback-safe environments.

43

Resposta de referência

I involve the team in risk identification sessions where we brainstorm potential obstacles. I also ask them to think about risks during Sprint planning. For mitigation, I ask the team to include risk-reducing tasks in their Sprint backlog, making risk management a shared responsibility.

44

Resposta de referência

Failure is data. I analyze: - Were Sprint Goals clear? - Were stories properly refined? - Did external blockers disrupt work? - Was estimation realistic? Then convert insights into concrete improvement actions. Blame destroys learning. Inspection creates growth.

45

Resposta de referência

I set up automated build and test processes, ensure frequent commits to the main branch, and educate the team on the importance of fixing broken builds immediately to maintain a stable baseline.

46

Resposta de referência

SCRUM is a holistic approach to solving a complex problem in a simple and sophisticated way scientifically. Scrum is an evidence-based, simple framework for professional agile leadership with effective team collaboration on complex products.

47

Resposta de referência

Sprint Planning is a meeting where the team selects backlog items and defines a Sprint Goal for the upcoming Sprint. The team decides - what can be delivered - and how the work will be completed.

48

Resposta de referência

The candidate should suggest actions like conducting knowledge transfer sessions, pairing experienced developers with newcomers, breaking down tasks into smaller chunks, investing in training or documentation, setting realistic sprint goals, and fostering a culture of experimentation and learning to gradually improve velocity and outcomes.

49

Resposta de referência

Certain situations where it is not suggested to use scrum: - (Content not explicitly listed in the provided text beyond the introductory statement).

50

Resposta de referência

A Scrum Master helps enhance team productivity by removing obstacles, facilitating Scrum ceremonies, coaching the team, and ensuring the process runs smoothly. They foster a positive, collaborative environment and ensure the team stays focused on delivering value, making the team more efficient and aligned.

51

Resposta de referência

The Daily Stand-up session is a short time-boxed meeting held every day of the Sprint. Here the Development Team synchronizes work and plans for the next 24 hours. Team members briefly discuss progress, upcoming work, and any blockers. Its purpose is to maintain transparency, identify impediments early and keep the team aligned toward the Sprint Goal.

52

Resposta de referência

Jira, Asana, Trello, Slack, Zoom, Confluence, Monday.com, ClickUp, Teamwork, Notion, etc., are some of the popular Scrum tools that facilitate project management and also enhance communication, visualisation, collaboration and flexibility within the projects.

53

Resposta de referência

Velocity is the sum of story points that a scrum team completes (meets the definition of done) over a sprint.

54

Resposta de referência

Sustaining team motivation and engagement involves a combination of recognizing achievements, fostering a positive team culture, and addressing individual needs. I celebrate milestones and accomplishments openly during ceremonies like sprint reviews and retrospectives, acknowledging the team's contributions. Additionally, I encourage a collaborative and supportive environment where team members feel valued and empowered to share ideas. Addressing individual needs involves regular check-ins, understanding personal development goals, and providing opportunities for skill growth. By creating a culture of appreciation, collaboration, and individual support, we maintain high levels of motivation and engagement throughout the duration of the project.

55

Resposta de referência

A Sprint forms the core of Scrum, lasting two weeks to one month, during which a potentially releasable product increment is produced. It starts after the previous Sprint ends, breaking down large tasks into manageable parts. Sprints enable teams to deliver high-quality work faster and more frequently, enhancing project manageability and providing flexibility to adapt to changes.

56

Resposta de referência

Various risks in Scrum include: - (Content not explicitly listed in the provided text beyond the introductory statement). To manage these risks, it's vital to: - (Content not explicitly listed in the provided text beyond the introductory statement).

57

Resposta de referência

Impediments are obstacles that prevent the Scrum team from completing work. Examples include: - Technical Issues – Bugs, infrastructure failures. - Resource Constraints – Lack of tools access to environments. - Team Conflicts – Miscommunication or unclear responsibilities. - External Dependencies – Waiting on third-party integrations or approvals.

58

Resposta de referência

Encouraging a culture of knowledge sharing and cross-functional collaboration involves creating an environment where team members feel empowered to share their expertise and collaborate across disciplines. I organize regular knowledge-sharing sessions, where team members have the opportunity to present and discuss their insights, learnings, or best practices. Additionally, I encourage pair programming, cross-functional training, and the rotation of roles to enhance the team's understanding of each other's responsibilities. By celebrating diverse skill sets, promoting continuous learning, and creating opportunities for cross-functional collaboration, we foster a culture that values knowledge sharing and strengthens the overall capability of the Scrum team.

59

Resposta de referência

The Cumulative Flow Diagram shows the amount of work in different stages of the development process over time. It helps in identifying bottlenecks and ensuring a balanced workflow.

60

Resposta de referência

I use metrics like velocity, burndown charts, and cycle time to track progress. However, I emphasize that these are for forecasting and improvement, not for evaluation. I also track team satisfaction and the quality of the product increment as key indicators of performance.

61

Resposta de referência

This Scrum Master interview question is all about feedback, which is a vital part of any team member's professional growth and development. Taking on feedback is tricky (and uncomfortable at times). But as an employer, you need to know that your candidate can embrace constructive feedback in a productive way, and and that they view feedback as a positive thing. Listen for: Someone who speaks of feedback as an opportunity for growth and development. They can both receive and deliver feedback professionally and positively.

62

Resposta de referência

A Scrum team usually consists of five to eleven team members collaborating on different tasks and duties for project/product delivery. It comprises motivated individuals who work together to ensure successful product delivery. Effective communication is crucial among Scrum team members to ensure alignment toward a common goal while upholding mutual respect throughout the project. Additionally, they adhere to a shared set of norms and rules.

63

Resposta de referência

Promoting a culture of shared responsibility is key. I encourage frequent communication, joint planning sessions, and shared KPIs to ensure alignment and collaboration between development and operations teams.

64

Resposta de referência

Agile Methodology refers to the software development process with an idea of iterative development between the self organised cross-functional team. The agile method emphasizes on breaking the whole process into different stages so as to keep track of every activity with constant collaboration resulting in improved and quality results at every stage of the workflow process. Keep reading scrum master interview questions. With the concepts of Agile Methodology, teams are able to self organised themselves with the constant collaborative approach between the cross-functional team. Once the process of work begins, the teams need to go through different stages of planning, execution, evaluation and delivery. The fundamentals of Agile Methodology relies on four core values: 1) Individual Interaction as well as Team Interaction over processes and tools. 2) Working Software over comprehensive documentation. 3) Customer collaboration over contract negotiation. 4) Responding to change over following a plan.

65

Resposta de referência

An Increment is the sum of all completed Product Backlog items during a sprint. It is a working, usable version of the product that meets the Definition of Done.

66

Resposta de referência

Building trust is key for a good scrum master. I do this by being steady, open, and reliable. I always try to match what I say with what I do. My main goal is to help the team, not to watch over everything they do. I try to make a safe place where people feel good about sharing their thoughts and even their mistakes. They know they do not need to worry. I ask for open talk, especially in Scrum meetings like Sprint Retrospectives. I also show the team that I can make mistakes and tell them when I do. I feel it is important to be real. To build trust, I: - Practice active listening so each person feels they are respected. - Honor commitments, mostly when you are working to remove blocks for the team. - Celebrate wins and help others learn from mistakes. This helps with continuous improvement.

67

Resposta de referência

A user story is an agile software development/ project management tool that offers teams ingenious, natural language justifications of one or more features of the project that's penned from the viewpoint of the end-user. - The user story doesn't go into detail but only refers to how certain types of work will fetch value to the end-user. The end-user, in this case, could be an outside component or an internal customer/colleague within the organization. - They also form the building block of agile frameworks like epics and other enterprises. - They confirm that the teams work concerning the goals of the organization, with the help of epics and initiatives. - We need to make a user story a reality and are added later, after discussions with the team. - They are detailed on post-it notes, index cards, or project management software.

68

Resposta de referência

In a previous project, I noticed our sprint planning meetings were taking too long, affecting productivity. I introduced a pre-planning session where team members could prepare their tasks in advance, which significantly reduced meeting time and improved focus.

69

Resposta de referência

The ideal duration for a one-month Sprint is a maximum of eight hours. For shorter Sprints, it is proportionally shorter. I manage time by creating a clear agenda, time-boxing each part (e.g., what vs. how), and keeping discussions focused on the Sprint goal and capacity.

70

Resposta de referência

Automation plays a vital role in Scrum. To have continuous feedback and ensure quality deliverables, we should try to implement TDD, BDD, and ATDD approaches during our development. Automation in scrum is not only related to testing, but it is to all aspects of software development. Introducing TDD, BDD, and ATDD will speed up our development process along with maintaining the quality standards; automating the build and deployment process will also speed up the feature availability in different environments – from QA to production. As far as testing is concerned, regression testing should be the one that will have the most attention. With the progress of every sprint, the regression suite keeps on increasing and it becomes practically very challenging to execute the regression suite manually for every sprint. Since we have a sprint duration of 2 – 4 weeks, automating it would be ideal.

71

Resposta de referência

Defines product vision and goals, manages and prioritizes the Product Backlog, writes and refines user stories, ensures maximum business value, communicates with stakeholders.

72

Resposta de referência

To integrate new team members effectively into an existing Scrum team, start with comprehensive onboarding that covers team processes, coding standards, and project details. Encourage pair programming and mentorship to facilitate knowledge transfer. During sprint ceremonies, ensure new members feel comfortable participating and sharing their perspectives. This approach fosters smooth integration, maintains team dynamics, and enhances productivity.

73

Resposta de referência

The collaboration between business stakeholders and developers is pivotal for a project's success. The scrum master should lead the daily standup meetings, emphasizing the importance of each stakeholder's presence by highlighting its significance to the project's progression. The daily scrum's primary purpose is to gauge the likelihood of achieving the sprint goal. When all stakeholders attend, they gain a holistic view of the product's evolution, enabling them to realign priorities accordingly. Moreover, this platform provides an opportunity to address challenges various members face, fostering collaboration and unity.

74

Resposta de referência

A Sprint is at the heart of Scrum. It is a two-week or one-month period in which a potentially releasable product increment is generated. Following the conclusion of the preceding Sprint, a new Sprint begins. It breaks down large, difficult undertakings into manageable chunks. It helps teams provide high-quality work faster and more frequently, making projects easier to manage. Sprints provide them with more flexibility in adapting to changes. Sprint planning, daily scrums, development work, Sprint review, and sprint retrospective are all part of a sprint. - The work to be done in the Sprint is planned collectively by the Scrum Team during Sprint planning. - The Daily Scrum Meeting is a 15-minute timed event in which the Scrum Team synchronizes efforts and creates a strategy for the following day. - At the end of each Sprint, a Sprint Review is held to review the Increment and, if necessary, make modifications to the Product Backlog. - After the Sprint Review and before the following Sprint Planning, there is a Sprint Retrospective. The Scrum Team will inspect itself and prepare a plan for changes to be implemented during the next Sprint during this meeting.

75

Resposta de referência

Yes, but with important caveats. It works better when the teams are mature, aligned, and the contexts are stable. It becomes a problem when teams are new, struggling, or have high complexity. The general guidance is one Scrum Master per team for new or struggling teams.

76

Resposta de referência

If anyone insists that there are too many meetings in Scrum, I always ask them which ones they'd like to remove: - Should teams skip sprint planning? - Should teams forgo sprint retrospectives to look for improvements? - Should teams not conduct sprint reviews to share their progress with the client? - Should developers not meet briefly each day to discuss progress? Each meeting in Scrum serves a specific purpose. Moreover, Scrum's events, and the transparency of its artifacts, are designed to eliminate the need for other meetings. This means Scrum actually should result in fewer meetings than efforts driven by other frameworks. If an organization schedules meetings outside of the events prescribed by the Scrum Guide, that is an impediment the Scrum master should work to remove.

77

Resposta de referência

The ongoing process of adding detail and estimates to Product Backlog items.

78

Resposta de referência

Responsibilities typically include facilitating Scrum ceremonies (daily stand-ups, sprint planning, sprint review, and retrospective), coaching the team on Scrum principles and practices, removing impediments, protecting the team from external distractions, ensuring the Scrum framework is followed, tracking sprint progress, and fostering a culture of continuous improvement.

79

Resposta de referência

Common risks include timeline problems as teams try to adapt to changes, difficulties with budget (i.e. running out of funds), and scope creep (new features added to products in development, due to inefficient requirement definition).

80

Resposta de referência

Effectiveness is measured by the quality and impact of the action items generated, the team's engagement during the meeting, and whether the team successfully implements the agreed-upon improvements in subsequent Sprints. I also periodically ask the team for feedback on the retrospective format.

81

Resposta de referência

No, and this is a trap question many candidates get wrong. DoD should be stable within a Sprint. If you change it mid-Sprint, you're either lowering quality standards under pressure (bad) or adding requirements nobody agreed to (also bad). DoD can be updated but only at Sprint boundaries, ideally discussed during Retrospective. Mid-Sprint changes create confusion and undermine team trust.

82

Resposta de referência

The Scrum Guide says that Scrum is immutable. That means teams must implement Scrum in its entirety; otherwise, what the team is doing can't be considered Scrum. ScrumBut occurs when teams make excuses for why they do not implement Scrum in a way that is fully aligned with the Scrum Guide. Some examples include the following: - We do Scrum, but we don't do daily Scrums. - We do Scrum, but we don't have sprint goals. - We do Scrum, but our project has two product owners. That's ScrumBut -- "Scrum, but …" -- and teams should avoid it at all costs.

83

Resposta de referência

A typical retrospective involves the team gathering to discuss what went well, what went wrong, and what could be improved. It often starts with setting the stage, then gathering data, generating insights, deciding on action items, and closing the meeting. The Scrum Master facilitates but does not dominate.

84

Resposta de referência

The three roles are the Product Owner (who maximizes the value of the product and manages the Product Backlog), the Scrum Master (who ensures the Scrum process is followed and removes impediments), and the Development Team (a self-organizing group that does the actual work of delivering the product increment).

85

Resposta de referência

It's likely your candidate will encounter this at some point or another in their career and it's their job as Scrum Master to keep everything in check. They need the ability to be empathetic while also figuring out a fix for the issue so the task can be completed successfully and on schedule. Listen for: How they approach the situation with the team member, ideally in a one-to-one conversation. They should also mention how they work to create an open and understanding work environment while providing suggestions and support for team members.

86

Resposta de referência

When the team's velocity is consistently lower than expected, I adopt a collaborative and analytical approach to identify and address the underlying issues. I start by conducting a retrospective to understand the factors contributing to the lower velocity, considering potential blockers, capacity constraints, or dependencies. If the issues are related to external factors, I collaborate with relevant stakeholders to mitigate them. For internal challenges, I work with the team to implement targeted improvements, such as refining estimation techniques or addressing bottlenecks. By approaching the issue systematically and collaboratively, we can increase the team's velocity over time while continuously improving our processes.

87

Resposta de referência

No, during product reviews, collaboration with stakeholders involves the entire team.

88

Resposta de referência

Backlog refinement is the ongoing process of reviewing, clarifying, estimating, and prioritizing Product Backlog items.

89

Resposta de referência

A Scrum framework has three roles: - Scrum Master - Product Owner - Development Team There are no other roles than these but beyond Product organization, they can have other organizational roles too. Scrum does not speak anything on these roles and this depends on organization to organization.

90

Resposta de referência

I don't see any disadvantages to using scrum. The problems mainly arise when the scrum team does not either understand the values and principles of the scrum or is not flexible enough to change.

91

Resposta de referência

The key principles of Agile Software Development, as outlined in the Agile Manifesto, include: - (Content not explicitly listed in the provided text beyond the introductory statement).

92

Resposta de referência

Effective communication in a Scrum team can be achieved through regular Scrum ceremonies, open feedback loops, and transparent information sharing. Team members should be encouraged to express their thoughts and concerns freely, and the Scrum Master should facilitate this process by creating an environment conducive to collaboration and trust.

93

Resposta de referência

Definition of Done is the checklist of activities that need to be completed in order to call the Product Backlog Item (requirements) DONE so that it can be part of potentially releasable increment. This is common understanding between the PO and Dev Team. This is generally formulated at the start of the first sprint and which can be enhanced later on as the understanding of the Scrum team enhances.

94

Resposta de referência

By enabling the team's success through: - Removing obstacles. - Encouraging collaboration. - Supporting team growth.

95

Resposta de referência

I use metrics such as Velocity, Burn-down charts, Sprint Goal Completion, and Lead Time to track progress and success. These metrics help assess the team's efficiency, identify areas for improvement, and ensure alignment with the project goals.

96

Resposta de referência

Facilitating a constructive and effective retrospective meeting involves creating a safe space for open communication, reflection, and collaborative problem-solving. I start by setting the tone for a positive and inclusive discussion, emphasizing the purpose of the retrospective as an opportunity for learning and improvement. During the meeting, I encourage team members to share both positive experiences and areas for improvement. I facilitate discussions on identified issues, encouraging the team to propose actionable solutions. Additionally, I ensure that the team reflects on the effectiveness of previously implemented improvements. By creating an environment that values transparency, constructive feedback, and continuous learning, we foster a culture of continuous improvement within the Scrum team.

97

Resposta de referência

Team autonomy, value delivery, continuous improvement, and reduced dependency.

98

Resposta de referência

The three C's in a User Story are: - Card : The "Card" aspect represents the physical or digital representation of the user story, often written on a physical index card or stored in a digital tool. It's a concise, written description of the user story that captures the essence of what needs to be done. - Conversation: The "Conversation" aspect emphasizes the importance of ongoing communication and collaboration between the Product Owner and the development team to clarify requirements, discuss details, and ensure a shared understanding of the user story. Instead of relying solely on documentation, the team engages in conversations to elaborate on the user story and address any questions or concerns. - Confirmation (or Criteria): The "Confirmation" aspect outlines the acceptance criteria or conditions of satisfaction that define when the user story is considered complete. These criteria provide clear, objective guidelines for the development team to validate that the user story meets the intended functionality and requirements.

99

Resposta de referência

The main artifacts in Scrum are: a)Sprint Backlog b) Product Backlog c) Velocity Chart d) Burn-down Chart

100

Resposta de referência

The Product Owner gathers user feedback through user testing, analytics, and direct customer interaction. This feedback is translated into backlog items. I encourage the team to participate in user research to understand the 'why' behind the items, ensuring the backlog truly reflects user needs.

101

Resposta de referência

All Scrum ceremonies have value, but Sprint Review is crucial as it ensures the product aligns with stakeholder expectations and gathers feedback for improvement.

102

Resposta de referência

Timeboxing in Scrum means setting a fixed activity time limit to improve focus and efficiency. It ensures tasks don't extend indefinitely. Examples include Sprint Planning (up to 8 hours), Daily Scrum (15 minutes), and Sprint Review (up to 4 hours). It keeps teams disciplined and on track.

103

Resposta de referência

Sprints are usually one month or less, in which a usable and potentially releasable product increment is created. But a sprint can be as short as a week. Two weeks, however, is the average. Where does your candidate fall on this spectrum? This can tell you a lot about how they'll work on your project.

104

Resposta de referência

The answer to this question will give you an idea if your candidate is going to be able to work well with your team. Working in a collaborative environment requires shared mutual respect among everyone — no matter the seniority level. Listen for: Talk of communication, mutual respect, teamwork and participation. Your candidate should display a sense of empathy, patience and openness in their response to how they work with others.

105

Resposta de referência

Commitment, courage, focus, openness, respect.

106

Resposta de referência

Dealing with a team member who does not take part in retrospectives can feel tough. To help, you need to make a safe space for your team. In this way, everyone can feel okay to talk about their thoughts and what they go through. It is good to start with clear communication. Speak with the person alone and try to find out why they are not joining in. Help them feel more ownership of their work. Talk about how important continuous improvement is for everyone who is part of the team. A team grows strong when people share and learn. You can try ideas like having people brainstorm ways to hit common goals or use user story mapping. This may bring the team member in and help them feel a part of what the group does. It is smart to show how coming to retrospectives can help. When the team joins in, there is often more team morale, better conflict resolution, and a sense that people work well together. In the end, just help your team member see that these talks can be good for everyone.

107

Resposta de referência

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.

108

Resposta de referência

Factors include business priorities, customer needs, team capacity, technical dependencies, market trends, and feedback from previous releases. Balancing these factors is crucial for a successful release plan.

109

Resposta de referência

Servant leadership' is a type of leadership that focuses on maintaining trust and confidence. What's great about this type of leadership is that it can apply to many situations, no matter what the industry or group may be. The scrum master needs to be a facilitator, a guide, and mentor/friend to all team members. As an example: facilitating meetings where they take notes on everyone's ideas, guiding team members through their error reports, mentoring them via one-to-one communication, anything that helps make each individual involved more empowered for the role in which they play.

110

Resposta de referência

Agile testing breaks work into smaller steps. Testers and developers collaborate continuously, adapt quickly, and test early, unlike traditional testing, which often happens after development ends.

111

Resposta de referência

The term "servant leader" mainly spotlights the service orientation which a leader should reveal. - The Scrum Master needs to be an expediter, a guide, an advisor, etc. - This helps the team have added involvement, inspiration, empowerment, etc.

112

Resposta de referência

You should know that a Scrum Sprint is a repeatable work cycle which usually runs no longer than 30 days, and can often be considerably shorter (even a week). The time-frame is set at the start of the sprint, during a planning meeting, and the length varies depending on the project's size. During the Scrum Sprint, specific work is finished and prepared for review. Progress is shared and evaluated during stand-up meetings each day. A Sprint Review allows the team to follow-up the process, identifying issues and learning lessons to improve subsequent Sprints. This is followed by a Sprint retrospective, in which improvements are planned. Sprint retrospective books can help you learn more about this stage.

113

Resposta de referência

Scrum Master could use the following techniques: A. Involve the complete Development Team. B. Use coaching techniques; such as open questions and active listening.

114

Resposta de referência

A Scrum Master should facilitate team processes effectively to achieve optimal outcomes. However, they should refrain from facilitating workshops where impartiality is crucial, particularly when discussing changes to the company's Scrum processes. In such instances, the Scrum Master should maintain neutrality and avoid injecting personal opinions or biases into the discussions.

115

Resposta de referência

DoD stands for Definition of Done. It is the set of deliverables that contain written codes, comments on coding, unit tests, integration testing, design documents, release notes, and so on. This provides project development with quantifiable and demonstrable benefits. It is quite beneficial to scrum when it comes to identifying deliverables that will assist the project reach its goal. It assists with: - Identifying the steps necessary to complete the iteration. - The use of appropriate technologies, such as burndown, to improve the efficiency of the process. - Providing timely input at all stages of the project's life cycle. - Assuring that the product backlog items are properly walked through and understood. - The establishment of a checklist for the backlog items in the product. - Assuring that it is defined in such a way that it is task-oriented. - Including the product owner in the sprint review and sprint retrospective.

116

Resposta de referência

Impediments in Scrum are obstacles or issues that slow down the team's progress, preventing them from delivering a “Done” increment. Examples of impediments include: a) Missing resources or sick team members b) Technical or operational challenges c) Lack of support from management

117

Resposta de referência

I'd first make sure both sides understand each other's constraints and reasoning. Sometimes the disagreement comes from missing information. I'd facilitate a conversation where the Product Owner explains the business priorities and the team explains their technical concerns or capacity limits. Then I'd dig into the specifics—are they disagreeing on priority, feasibility, or scope? Once everyone understands the real issue, the answer usually becomes clearer. In one case, the PO wanted to build a feature the team thought was technically risky. By bringing in the tech lead to discuss the actual risks versus assumptions, we found a phased approach that reduced risk while still delivering value in the sprint. My role was making sure the conversation stayed respectful and focused on solving the problem, not winning the argument.

118

Resposta de referência

A product owner is a part of scrum team, who is reponsible making sure that the project is a success in Scrum. The product owner is also responsible for defining user stories and creating product backlog. One of the major responsiblity of the product owner is to identify product requirements for the development team on behalf of customers. The Product Owner is responsible for defining and communicating the vision for the product. They have a deep understanding of the market, users, and business goals, and they use this knowledge to shape the direction of the product and prioritize features accordingly.

119

Resposta de referência

The key components of Agile include: Iterative Development – Delivering work in small increments. Collaboration – Engaging customers, stakeholders, and teams in the process. Adaptability – Responding to changes quickly. Continuous Feedback – Regular reviews to refine the product. Transparency – Open communication and visibility into progress.

120

Resposta de referência

I use tools like Burndown Charts and Sprint Reviews to track the progress of the team. These tools provide real-time visibility into how much work remains and whether the team is on track to meet their goals. During a scrum master interview, expect scrum master questions related to your leadership style and how you facilitate collaboration within the team.

121

Resposta de referência

Measuring and improving team collaboration involves a combination of qualitative and quantitative assessments. I regularly gather feedback through retrospectives, encouraging team members to share their perspectives on collaboration and communication. Additionally, I track key performance indicators such as sprint velocity, cycle time, and the frequency of blocked tasks. Analyzing these metrics helps identify areas for improvement and informs strategies to enhance collaboration. To actively promote collaboration, I organize team-building activities, facilitate cross-functional training, and encourage the use of collaborative tools. By continuously monitoring collaboration and implementing targeted interventions, we create an environment that fosters effective teamwork and communication.

122

Resposta de referência

Conflict within a Scrum team can be handled through several approaches, including having one-on-one meetings with interested parties to understand the issue, organizing the Scrum team to brainstorm solutions, escalating if the decision-making capacity is out of your power, or allowing team members to sort out differences themselves if it doesn't hamper project performance. Preventative measures like effective communication plans and icebreaker sessions can also minimize conflict.

123

Resposta de referência

No matter how beneficial Scrum is, it also has certain limitations or disadvantages. We have listed them right below: - Projects in Scrum can extend over a long period due to the absence of a specified timeline. - As Scrum is all about an ongoing process (consistent development and constant improvement), there is no exact closure or final step. - The Scrum methodology does not yield great results when implemented in a large team, as it is specifically designed for smaller teams. - Only experienced team members or employees can make the most out of this methodology, and not everyone. - The daily standup meeting in Scrum is often considered impractical for the team members, as it fails to show significant work done over a period of time, but only reflects primarily on the previous day's progress. - As Scrum prioritises regular changes, the product delivery remains changing - If the scrum teams are not trained properly, the developments cannot be implemented easily.

124

Resposta de referência

Every framework or methodology has both disadvantages and advantages. The Scrum methodology is no exception. Here are the disadvantages of practising Scrum, presented in pointer format: - (Content not explicitly listed in the provided text beyond the introductory statement).

125

Resposta de referência

Not always. Velocity measures work completed in story points but does not account for quality, complexity, or business value. A high velocity does not always mean higher productivity.

126

Resposta de referência

A Minimum Viable Product (MVP) in Scrum is defined as a product with the minimum required features displayed to the stakeholders and eligible for the production process.

127

Resposta de referência

I handle resistance by first understanding the concerns of the team members and addressing them through open communication. I then demonstrate the benefits of Scrum practices with real-world examples and provide the necessary support and training to facilitate a smooth transition.

128

Resposta de referência

I have one-on-one conversations to understand the root cause of their demotivation. I try to reconnect their work with the product's purpose and their personal goals. I also provide them with new challenges or learning opportunities to re-engage them.

129

Resposta de referência

I have facilitated various types, including the "What Went Well" and "What Didn't," "Start-Stop-Continue," "Fishbone Analysis," and "Sailboat" Retrospectives. Each type serves different needs and helps keep the process fresh and engaging.

130

Resposta de referência

A Scrum Master fosters innovation by creating a safe environment for experimentation and encouraging the team to think outside the box. By facilitating brainstorming sessions and providing the necessary resources, they help the team explore new ideas and drive continuous improvement.

131

Resposta de referência

In Scrum, Epics, User Stories, and Tasks are ways to break down work into manageable chunks: a) Epic: Think of an Epic as a big goal or feature that's too large to complete in one go. b) User Story: A User Story is a smaller, more focused piece of work that comes from an Epic. c) Task: Tasks are the smallest units of work. They break a User Story down into specific steps, which are assigned to individual team members during a sprint.

132

Resposta de referência

The term” Ready” defines what has to be included in the user story before the team can estimate it. It's the responsibility of the team or the product owner to ensure that user stories are ready before the beginning of the sprint phase.

133

Resposta de referência

I use a combination of regular status meetings, release burndown charts, and email updates to keep stakeholders informed. Transparency and clarity in communication are my top priorities.

134

Resposta de referência

The Scrum framework includes: - The organization - Product owner - Scrum team

135

Resposta de referência

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.

136

Resposta de referência

I measure effectiveness by tracking the number of risks that materialized versus those that were mitigated. I also assess how quickly the team responds to unexpected obstacles. Ultimately, the process is effective if the team can deliver the project's goals despite uncertainties.

137

Resposta de referência

Each team member gets a set of cards. For each item, after a brief discussion, everyone simultaneously reveals their card. If estimates vary widely, we discuss reasons and re-estimate until we reach a consensus.

138

Resposta de referência

The Scrum Master plays a crucial role in facilitating the Sprint Retrospective. Their responsibilities include: - Facilitating the Session: Ensuring the retrospective is productive and focused on continuous improvement. This involves setting the stage, managing the timebox, and creating a psychologically safe environment for open discussions. - Participating as a Team Member: The Scrum Master participates in discussions, identifying improvement areas and helping the team adapt their processes. - Encouraging Active Participation: They ensure all team members have a chance to contribute by asking open-ended questions and engaging quieter team members. - Ensuring Follow-Up: While not responsible for prioritizing action items, they help implement agreed-upon improvements by facilitating follow-up discussions.

139

Resposta de referência

Since scrum is part of the larger agile idea, it's always good to see how the person distinguishes between the waterfall model that moves one phase at a time and the short, frequent feedback loops of agile. If the person is unable to make these distinctions clear to you, they will not serve as an influential scrum master.

140

Resposta de referência

Share how you encourage team-owned commitments, promote shared responsibility, and focus on continuous improvement. Mention retrospectives, working agreements, or visual tools like Kanban boards.

141

Resposta de referência

The Daily Stand-up is a 15-minute time-boxed event for the Scrum Team to synchronize. Each team member answers three questions: What did I do yesterday that helped the team meet the Sprint Goal? What will I do today to help the team meet the Sprint Goal? Do I see any impediments that prevent me or the team from meeting the Sprint Goal? It is not a status report to management. It is a team coordination event that surfaces blockers early so they can be resolved quickly.

142

Resposta de referência

Use breakout groups, visual aids, clear timeboxes, and structured techniques.

143

Resposta de referência

There are multiple options a) Scenario 1: I can have 2 different teams – 1 for Feature Development and other for defect fixing. (Ideal) b) Scenario 2: Based on the trend of defects, I can limit my planned features and leave the scope for defects handling. This way you are not playing with Sprint Goal c) Scenario 3: Reduce the sprint length if the defects SLA is not too short like something below a week to accommodate incoming defects in next sprint. How to: • You can go through a Scrum Master Certification or Kanban KMP1 Certification and KMP2 Certification will give you in depth knowledge. Read more about Scrum master interview questions.

144

Resposta de referência

Scrum uses time-boxed Sprints and defined roles, while Kanban focuses on continuous flow without fixed iterations. Scrum: - Fixed Sprint length - Defined roles (Scrum Master, Product Owner, Developers) - Sprint commitments Kanban: - Continuous delivery - Work-in-progress limits - Flow-based metrics like cycle time Both are Agile approaches but differ in structure and cadence.

145

Resposta de referência

The Sprint Retrospective is held at the end of each sprint. The Scrum Team reflects on how they worked during the sprint and identifies specific improvements to make in the next cycle. It covers three areas: What went well during the sprint, what did not go well, and what specific improvements can be made. The keyword is specific. Vague observations without committed actions make Retrospectives ineffective.

146

Resposta de referência

Ensure it happens but not necessarily attend or facilitate.

147

Resposta de referência

During a Sprint, the Product Backlog can be re-prioritized for future Sprints, but the Sprint Backlog should not be changed unless it is absolutely necessary and the team agrees. Changes are managed by adding new items to the Product Backlog and re-prioritizing for the next Sprint Planning.

148

Resposta de referência

Confidence Vote is not a standard Scrum concept but is used in Agile environments to enhance decision-making. It involves team members expressing their agreement or disagreement with a decision and their confidence level in it. This is typically done on a scale (e.g., 1-5) to gauge collective certainty or uncertainty.

149

Resposta de referência

A Burndown chart shows the amount of work remaining (typically measured in story points or tasks) on the vertical axis against time on the horizontal axis, usually represented in Sprint increments. A BurnUp chart tracks the total amount of work completed (cumulative) over time, illustrating progress towards completing the project scope or release goals.

150

Resposta de referência

When dealing with a Product Owner who is disengaged or accessible, it's crucial to address the situation proactively. Begin by opening lines of communication to understand the reasons for their limited involvement. If conflicting priorities are the issue, collaborate to find common ground and include them in essential decisions. In the absence of the Product Owner, act as their proxy to support the team in making informed decisions with available resources. Maintain focus on preserving the product's vision, ensuring continuous value delivery, and overcoming challenges.

151

Resposta de referência

The candidate should describe a constructive feedback approach, such as using the SBI model (Situation-Behavior-Impact), providing timely and specific feedback in private, focusing on actions rather than personality, and encouraging a growth mindset. They should also mention how they create a safe environment for receiving feedback.

152

Resposta de referência

I motivate by connecting their work to a larger purpose and by giving them autonomy and mastery. I celebrate their achievements and provide opportunities for growth. I also create a supportive environment where they feel safe to take risks and innovate.

153

Resposta de referência

I support team members by identifying their individual strengths and areas for improvement, providing access to relevant training and development resources. Additionally, I encourage mentorship and peer learning opportunities to foster a culture of continuous growth.

154

Resposta de referência

Clear and concise - Do not "bury the lead" - communicate bottom line - Avoid going too deep (more detail means less comprehension) - No emotion/blaming/justification - just the facts

155

Resposta de referência

Use Waterfall over Scrum when: - Requirements are stable and unlikely to change. - Budget and timeline are fixed. - Regulatory compliance is critical. - There's a single delivery with no need for iterative development. - There's low team autonomy and a hierarchical organizational structure.

156

Resposta de referência

Waterfall method and the Scrum method can be used hand in hand to get the maximum desired output with the collaborative approach. But at times, there is a need when you need to go with the waterfall method despite of the Scrum method or their collaborative approach. The waterfall method is the simplest approach to the software development process while Scrum is specially designed to have long term effect with complex integration of its principle. So here are some of the places where one needs to prefer waterfall method over scrum method. When the project is simple: The waterfall method is the best possible process to use for simple project development and implementation. Unlike big projects which need teams building with a cross-functional collaborative approach and appropriate use of Agile Methodology, Waterfall method should be preferred to have a simple approach for the small projects. When the project is complicated: Waterfall method can be preferred for complicated projects. But the thing which makes appropriate use of the Waterfall method with complicated projects are expertise hands. Expertise hands are best to analyse the complications of a project and with approach of the waterfall model, they can design a simple and subtle approach to develop the projects. To focus on delivery date and budget: If with the development of software budget there comes a deadline then the waterfall method should be preferred over any other. The deadlines can be the delivery date of product or with the budget of software development or on the focused approach of performance the developed software. When Investment is not risky: The software development cycle is a long process and the risk of investment needs to get configured accordingly with the need. But with the software development method where investment is not risky and they have a path for the simplest approach, the Waterfall method needs to be preferred at first for the development process.

157

Resposta de referência

Psychological safety builds through: - Modeling vulnerability - Encouraging respectful dissent - Celebrating learning over perfection - Protecting teams from external blame Without safety, retrospectives become silent rituals.

158

Resposta de referência

When assessing the answers, look for examples of how the individual coached their teams to become more self-sufficient. Good responses will indicate the candidate's ability to foster growth and improvement in their team members. For instance, a strong answer would detail how the candidate identified the team member's skill gaps, designed a learning plan, and supported them throughout the process. This indicates the applicant is a proactive mentor. Another example of a good answer would be an explanation of how the candidate encouraged team decision-making while ensuring alignment with objectives. This answer shows they can balance leadership with empowerment.

159

Resposta de referência

Maintaining a focus on delivering value to end-users involves continuous alignment with user needs and priorities. I work closely with the Product Owner to ensure that user stories and features prioritize value and align with user expectations. During sprint planning and reviews, we regularly assess the impact of each increment on end-users and make adjustments accordingly. Additionally, I encourage direct interactions with end-users, such as user testing or feedback sessions, to gather insights and validate the value delivered. By emphasizing a user-centric approach and actively involving the team in understanding end-user needs, we ensure that the Scrum team consistently delivers valuable outcomes.

160

Resposta de referência

In Scrum of Scrums, I ensure representation from each team. The focus is on discussing inter-team dependencies, progress towards milestones, and resolving impediments that affect multiple teams. It's about coordination and alignment, not status updates.

161

Resposta de referência

Managing technical dependencies is crucial for maintaining a smooth development process. I promote proactive communication and collaboration among team members to identify and address potential dependencies early on. During sprint planning, I facilitate discussions about technical dependencies and work with the team to develop strategies for mitigating risks. Additionally, I encourage the use of tools and techniques such as dependency mapping to visualize and manage interdependencies. By fostering a culture of transparency and collaboration, the Scrum team can effectively navigate technical dependencies, ensuring a streamlined development process.

162

Resposta de referência

I use public recognition during team meetings or in company-wide channels. I also advocate for tangible rewards like training opportunities or small gifts. The most effective method is genuine, specific, and timely praise that connects their work to the team's success.

163

Resposta de referência

The five phases are: - Identifying risks - Categorizing risks - Risk response - Reviewing risks - Risk closure.

164

Resposta de referência

Understanding the team's dynamics holds paramount importance for a Scrum Master. If a team member perceives meetings as futile, it becomes imperative to investigate the reasons behind such behavior. Instead of focusing solely on the individual, the Scrum Master should engage in dialogue, utilizing open-ended questions to uncover the underlying reasons for non-attendance. Identifying the cause is crucial, followed by elucidating the significance of these meetings (Scrum ceremonies). In the Scrum framework, each team member plays an important role, similar to the wheels of a truck. Any deviation or malfunction affects the entire team's performance. Therefore, it's essential to elucidate the repercussions of their absence during planning meetings, as it can lead to imbalance within the team. If the issue persists, involving the reporting manager in a discussion can provide insights and potential solutions to support both the team members and the team as a whole.

165

Resposta de referência

Scrum Masters and Product Owners oversee the product backlog in Agile projects and understand the user stories necessary for successful product delivery. However, their primary contributions to the Scrum process differ significantly. Product Owners primarily focus on long-term planning, while Scrum Masters concentrate on the day-to-day operations of Scrum teams.

166

Resposta de referência

I would not reject planning. Instead I would: - Offer rolling wave planning - Provide forecast ranges - Show empirical velocity trends - Educate on uncertainty reduction over time Agile plans progressively instead of rigid upfront planning.

167

Resposta de referência

Staying current in the agile space is essential, as our understanding of effective practices continues to evolve. I am an active member of the broader agile community, participating in the Agile Alliance and attending conferences like Agile 20XX when possible. I follow several thought leaders through their blogs, podcasts, and books. People like Mary and Tom Poppendieck on Lean, Esther Derby on team dynamics, and Allen Holub on technical agility have significantly influenced my thinking. I'm part of a local Scrum Master community of practice where we meet monthly to share experiences. I regularly experiment with new techniques in my day-to-day work. Perhaps most importantly, I treat my own practice as an empirical process—trying new approaches, reflecting on what works, and continuously evolving my toolkit. I keep a professional journal where I capture insights and questions from my daily work.

168

Resposta de referência

For inspection and adaptation within a containing event, the Sprint, Scrum combines four formal events. These events play an important role in implementing the empirical Scrum pillars of transparency, inspection, and adaptation.

169

Resposta de referência

During Sprint Review, we walk through and demonstrate the features or stories implemented to the stakeholders. During the Retrospective, we try to identify collaboratively what went well, what could be done better, and action items to have continuous improvement.

170

Resposta de referência

Low participation usually signals low psychological safety. I would: - Change retrospective formats - Use anonymous feedback tools - Start with small wins - Model vulnerability myself If silence persists, I would explore: - Fear of conflict - Leadership interference - Cultural constraints Retrospectives fail when trust is low.

171

Resposta de referência

Changing retrospective criticism into concrete enhancements requires a structured method. First, make sure the team thinks about both the good and bad parts of the sprint, finding certain actions that helped or hindered progress. In the retrospective, we work together to decide which improvement opportunities are most important and create concrete plans to tackle them. Collaborate with the team to include these action items in the upcoming sprint, keeping track of progress and making necessary adjustments. Converting retro feedback into concrete enhancements requires a systematic approach. Initially, ensure the team reviews both the pros and cons of the sprint, identifying specific actions that contributed to successes or difficulties. During the retrospective, collaborate to identify areas for improvement and develop specific steps to address them. Next, work with the team to integrate these action items into the upcoming sprint, monitor progress, and make necessary adjustments.

172

Resposta de referência

The Product Owner is primarily responsible for writing user stories, but the development team and stakeholders can collaborate to refine them.

173

Resposta de referência

There are several tools, charts, and techniques to track sprint progress. Teams can use Kanban boards, burndown, or burnup charts, cumulative flow diagrams, and participate in the daily scrum meetings to track the sprint progress. All of these tools and software work as a central system that allows the team members to visualise everything happening within a project at a glance, so that it becomes easier to track the work being done by the team at a point.

174

Resposta de referência

What I value most about Agile methodologies is how they acknowledge and embrace the fundamental uncertainty in complex work. Rather than pretending we can predict everything upfront, Agile approaches create tight feedback loops that allow us to learn and adapt as we go. This shows up in three ways I find particularly powerful. First, the focus is on delivering tangible value early and often. By breaking work into small increments and getting real feedback, we avoid the waste of building features no one wants or needs. Second, the emphasis is on empowered, self-organizing teams. Agile recognizes that the people doing the work have the best insight into how to do it effectively. Third, the commitment to continuous improvement creates a discipline of learning and adapting that's often missing in traditional approaches. What connects all these elements is a profound respect for reality over theory, for adaptation over rigid planning, and for the human dimensions of work.

175

Resposta de referência

Underestimation patterns signal: - Poor refinement - Hidden technical complexity - Optimism bias I would: - Strengthen backlog refinement - Encourage reference-based estimation - Review historical estimation accuracy - Introduce better story slicing

176

Resposta de referência

Through shadowing, reflective debriefs, role-plays, and coaching practice.

177

Resposta de referência

I lead by example, being honest about my own challenges. I establish a norm of transparency and respect, ensuring no one is penalized for raising problems. I also celebrate when team members openly discuss impediments, reinforcing the behavior.

178

Resposta de referência

A storyboard is a visual representation of a software project's progress. There are generally four columns, namely, ‘To do', In Progress', ‘Test', and ‘Done'. Different colored posts and their notes are placed in each column indicating the progress of individual development items. A storyboard is typically used in Agile development.

179

Resposta de referência

Empiricism means working based on facts, experience, and evidence. The empirical process control in Scrum includes the following: - (Content not explicitly listed in the provided text beyond the introductory statement).

180

Resposta de referência

Scrum is iterative, flexible, and based on sprints. The waterfall is sequential and rigid. Scrum encourages early feedback, quick changes, and continuous collaboration, while Waterfall requires completing each phase before moving forward.

181

Resposta de referência

The three primary roles in Scrum are: Product Owner: Responsible for defining and prioritizing the product backlog, ensuring it aligns with business and customer needs. Scrum Master: Facilitates the Scrum process, removes obstacles, and ensures the team follows Scrum principles. Development Team: A cross-functional group responsible for developing the product during sprints.

182

Resposta de referência

I use metrics like velocity, burndown/burnup charts, and cumulative flow diagrams. These help with forecasting and identifying bottlenecks. I also use qualitative metrics like team morale and stakeholder satisfaction to get a complete picture.

183

Resposta de referência

Daily scrum is timeboxed to 15 minutes and is a chance for the team to meet daily and discuss progress on sprint backlog items. Scrum Master runs the daily scrum and every team member gets a chance to talk about their progress or issues. The usual discussion is about what I have done today and what I will do tomorrow.

184

Resposta de referência

No, the focus should be on achieving an optimal velocity that balances speed and quality. Pushing to increase velocity may compromise product quality, leading to bugs or incomplete features. Sustainable velocity helps maintain team health while delivering quality work consistently.

185

Resposta de referência

Use frameworks like Nexus, LeSS, or SAFe with an emphasis on empirical scaling.

186

Resposta de referência

As a manager, it is important to imbibe the right guidance and principles for any team that they are overseeing. At times, scrum masters do find employees who are not flexible enough to embrace change, and it becomes difficult for everyone in the team to align their way of working with those stubborn employees. This is where open communication does the job. Not only does clear communication with the team members help the scrum master understand the root cause, but it also gives them a chance to assess what the employee's actual perception is regarding the matter. If I ever face this kind of situation, I will highlight the advantages of acknowledging change to my team members and share past instances where taking risks and tackling complex situations pushed projects to their successful completion. And I would be supportive enough to them because I know changes take time to be embraced.

187

Resposta de referência

The presence of the Scrum Master at the Daily Scrum serves several important purposes within the Scrum framework. Firstly, the Scrum Master plays a crucial role in facilitating the Daily Scrum meeting. They ensure that the meeting stays focused, time-boxed, and productive, guiding the team through the three key questions: What did we do yesterday? What will we do today? Are there any impediments in our way? By facilitating the meeting, the Scrum Master helps ensure that each team member has an opportunity to speak and that discussions remain relevant to the team's goals.

188

Resposta de referência

Candidates must explain their proactive stance on risk management within the Agile framework. They should describe their routine of identifying potential risks during backlog refinement and daily scrum meetings. Effective scrum masters utilize the retrospective meeting to reflect on risks encountered and refine their strategies, ensuring the teamâs adaptability and continuous improvement in handling new technologies and development challenges.

189

Resposta de referência

Scrum masters shouldn't actively participate in the daily Scrum at all. The daily Scrum is an opportunity for the developers to discuss progress and motivate each other as they move closer to the end of the sprint. The daily Scrum is for the developers, and run by the developers. Neither the product owner nor the Scrum master should be active participants in the daily Scrum. If the developers must call upon the product owner to answer a question, that's fine. If the developers want the Scrum master to attend and provide coaching or feedback regarding how to get more out of the daily Scrum, that is allowed as well. However, a Scrum master's or product owner's involvement in the daily Scrum must be at the behest of the developers. Otherwise, they shouldn't actively participate at all.

190

Resposta de referência

Change is facilitated through education, transparent communication, and demonstrating the benefits of Agile. I involve key stakeholders in the change process and address concerns proactively.

191

Resposta de referência

Share a story where things got too complicated and you helped reduce overhead—maybe by focusing on smaller team coordination or cutting out extra ceremonies. Show that you can tailor Agile, not just follow it.

192

Resposta de referência

A Product Backlog is a prioritized list of all work items needed to build and improve a product. It acts as the single source of requirements and evolves continuously as the product and business needs change. The Product Owner is the sole owner of the Product Backlog.

193

Resposta de referência

I address conflicts by creating an open, respectful environment where team members can express concerns and work through issues together. I facilitate discussions, encourage active listening, and help the team focus on the common goal, fostering collaboration and alignment.

194

Resposta de referência

Despite the fact that Scrum describes the Scrum Master as the person in charge of enforcing the process, it is critical to understand what this enforcing position entails and what its limitations are. Enforcement does not imply forcing the team to follow the process; rather, it entails putting Scrum's essential elements into practice to aid the teams' success. The Scrum Master is a facilitator who assists the teams in achieving their objectives. The Scrum Master will apply Scrum methods and urge the team to follow the scrum values during facilitation. It is critical to emphasize that we are discussing encouragement rather than coercion. It is not a project manager's role, but it will assist teams in resolving their roadblocks; it will be a collaborative effort rather than a directive one. The scrum master will try to demonstrate the benefits of adopting the processes and assist the team in gaining a grasp of the scrum processes from time to time, which is similar to demonstrating the proper route but allowing the team to choose whether or not to go down it. The scrum master will also serve as a mentor for the team, assisting them in achieving success in their agile journey.

195

Resposta de referência

Following are the five Scrum values: - Commitment: Scrum teams must be able to function as a team to accomplish a common goal. This entails putting faith in one another to complete their jobs and deliver to the best of their abilities. It will only occur if each team member is completely dedicated to the project and the team. Scrum masters and team leaders can aid commitment by facilitating good sprint preparation and shielding teams from mid-sprint scope changes and undue product owner pressure. - Focus: Each member of the team must remain focused on the work at hand as well as how it affects the sprint goal in order to get the most out of each sprint. Scrum masters might limit the number of tasks or priorities assigned to each team member throughout sprints to help them stay focused. Individuals can also stay focused on their assigned work by encouraging full team participation in daily Scrum meetings. - Openness: Each member of the team must be absolutely truthful about their personal progress in order for the Scrum team to accomplish the maximum progress in the quickest period possible. The daily Scrum meeting's goal is to identify and solve problems. That won't happen if team members aren't honest about any problems or hurdles they're facing. Team members must also be willing to collaborate with one another and see each other as vital contributors to the project's success. Being upfront with their teams is one of the finest methods for Scrum masters to foster openness. Giving honest feedback at daily Scrum meetings is not only crucial for making required adjustments, but it will also inspire team members to be honest and open in return. - Respect: Respect in a Scrum team implies understanding that no single individual or their contribution is more valuable than another. Respect also entails putting your faith in your coworkers to complete their jobs, listening to and considering their suggestions, and praising their achievements. Scrum masters may assist their teams to develop regard for each other by exhibiting respect for the product owner, stakeholders, and team members. - Courage: Scrum teams must have the guts to be genuine, upfront, and honest about the project's progress and any bottlenecks they encounter, both with themselves and with stakeholders. Members of the team must also have the bravery to seek assistance when needed, attempt new techniques or procedures that they are unfamiliar with, and respectfully disagree and engage in open debate. Scrum masters, like respect, can first and foremost promote courage by displaying it. To avoid mid-sprint adjustments or scope creep, the Scrum Master must have the confidence to stand up to stakeholders and product owners.

196

Resposta de referência

While a typical waterfall work environment focuses on the end product, Agile environments compartmentalize projects into individual tasks with realistic timelines. This maximizes productivity and quality. Here are some ways in which you can instill an Agile mindset: - A Scrum Master needs to discuss the idea of the outcome of projects with the team members. All performance metrics need to be defined and communicated to stakeholders. - Regular engagement with customers is necessary to further the sense of shared ownership. - Team members should be involved in all processes to gradually facilitate the shift to an Agile environment. - Make flexible strategies that can be changed based on situations

197

Resposta de referência

Talk about involving the team in PI planning, reviewing OKRs during backlog grooming, or creating sprint goals tied to outcomes. Show how you help the team focus on value.

198

Resposta de referência

The modest amount of effort put in to establish a rough skeleton of the product backlog is referred to as Sprint 0. It also contains information on calculating product release dates. Sprint 0 is necessary for the following tasks: - Creating a skeleton for the project, as well as research spikes - Maintaining a minimalist design - Creating a few stories completely - Being lightweight and having a low velocity The spike is a collection of activities that use Extreme Programming for research, design, investigation, prototyping, and other purposes. It tries to mitigate the technical approach's risks by assisting with the acquisition of knowledge in order to better comprehend requirements and increase reliability.

199

Resposta de referência

Timeboxing refers to devoting a time slot to an activity. A timebox is a unit of time. A timebox should not exceed 15 minutes for Daily Scrum or 8 hours for Sprint Planning.

200

Resposta de referência

Anybody can pursue becoming a scrum master if they are keen to know and learn about the agile principles. There is no specific set of guidelines or requirements that one has to follow to be a scrum master. All it requires for an individual with no prior relevant experience in Scrum methodology is to be interested in managing teams and prioritising timely outcomes. Some of the key scrum master skills include: - Being collaborative and understanding - Being a keen observer and communicator - Having core leadership and management skills - Being open to exploring, experimenting and learning new things - Supervising and guiding the scrum team on the scrum framework - Fostering a sense of practice of the Scrum principles by the team - Resolving conflicts within the team and eliminating obstacles from the process - Keeping a problem-solving attitude towards any small and big issues

NÃO QUER PERDER NADA?

Os testes práticos Cisco, PMP, CISA, CISM e AWS 100% aprovados estão à venda!
Obtenha agora

Obtenha uma certificação para destacar o seu currículo.

NÃO QUER PERDER NADA?

Os testes práticos Cisco, PMP, CISA, CISM e AWS 100% aprovados estão à venda! Obtenha agora

Obtenha uma certificação para destacar o seu currículo.

Os testes práticos Cisco, PMP, CISA, CISM e AWS 100% aprovados estão à venda!
Obtenha agora