아무것도 놓치고 싶지 않으신가요?

인증 시험 합격 팁

최신 시험 소식 및 할인 정보

전문가가 선별하고 최신 정보를 제공합니다.

예, 뉴스레터를 보내주세요

다른 면접 문제 보기
1
참고 답변
I would first have a private conversation to understand the underlying reasons, such as disengagement or scheduling conflicts. Then, I would reiterate the value of the meeting for the team's success and collaboratively find solutions, such as adjusting the meeting time or addressing any impediments causing absence.
2
참고 답변
First, I would not jump to blame or push harder delivery. I would analyze: - Are stories properly refined? - Is Sprint capacity calculated realistically? - Are external dependencies causing delays? - Is there hidden scope creep mid-Sprint? Then I would: - Facilitate a focused Retrospective around commitment reliability - Review Definition of Ready compliance - Compare planned vs delivered trends across 3–5 Sprints - Adjust forecasting method if necessary Consistent misses indicate a systemic issue, not a motivation issue.
커리어 가속

자격증을 취득하여 이력서를 돋보이게 하세요.

데이터 분석에 따르면 IT 자격증 보유자의 연봉은 평균 구직자보다 26% 높습니다. SPOTO에서 자격증 취득과 면접 준비를 동시에 진행하여 경력 성장을 가속할 수 있습니다.

1 100% 합격률
2 2주간 덤프 연습
3 자격증 시험 합격
전 세계적으로 인정 100만+ 자격증 취득 일하면서 학습
학습 계획 만들기
3
참고 답변
Story points measure effort, not value. I would redirect focus toward: - Sprint Goal achievement - Customer impact - Defect rates - Outcome delivery
4
참고 답변
- Capacity: Total available hours per sprint (team members' working hours minus non-project time). - Velocity: Based on past performance, the average number of story points completed per sprint.
5
참고 답변
I would focus on: - Backlog clarity - Stakeholder communication - Outcome-based thinking - Prioritization frameworks - Definition of Ready enforcement Many Scrum failures stem from weak Product Ownership.
6
참고 답변
Velocity is the amount of work a team completes in a sprint, typically measured in story points. It is calculated by averaging the story points completed across several recent sprints. Velocity is a planning tool, not a performance target. It helps the team forecast how much work they can realistically commit to in future sprints based on historical data.
7
참고 답변
I ensure continuous improvement during Sprint Retrospectives by making them action-oriented rather than discussion-oriented. The focus is not just on identifying what went well or what went wrong, but on agreeing to measurable improvement actions. I create a safe environment where the team can speak openly, analyze root causes, and commit to small or realistic changes that can be implemented in the very next sprint.
8
참고 답변
Early in my Scrum Master career, I was so focused on following the Scrum Guide perfectly that I was running a very rigid retrospective format. One team member finally said in a retro, ‘These feel really fake. Can we just talk about what's broken?' I realized I was so focused on process that I'd missed the point—the team needed safety and honesty, not a perfectly formatted meeting. I completely changed my approach. I started asking better questions instead of having a rigid format. Turns out when you give people space to actually say what's going on, you get way better insights. That taught me that Scrum is a framework, not scripture. You adapt it based on what the team needs.
9
참고 답변
A scrum master instructs and guides the product owner from the beginning to the end, and also assists in eliminating limitations or hindrances from the project so they can prioritise the product being built seamlessly. With their guidance, they make sure their team is aware of maximising the product value, product backlog refinement, and enabling communication.
10
참고 답변
The Scrum Master's presence at the Daily Scrum is optional; the development team is responsible for conducting it. Only development team members are required to participate in the Daily Scrum. However, the Scrum Master often attends to observe and identify any obstacles the team faces.
11
참고 답변
Some of the most widely used scrum tools are: - (Content not explicitly listed in the provided text beyond the introductory statement).
12
참고 답변
Scrum defines three primary roles for successful project delivery: the Product Owner, the Scrum Master, and the Development Team. Each role has distinct responsibilities and contributions to the Scrum framework, ensuring that teams can operate effectively within Agile methodologies. There are three different roles in Scrum: - (Content not explicitly listed in the provided text beyond the introductory statement).
13
참고 답변
I find Jira to be incredibly effective for managing Scrum projects due to its robust features for tracking sprints and managing backlogs. Additionally, tools like Trello and Asana offer great flexibility and ease of use for team collaboration and task management.
14
참고 답변
The story point can be understood as a parameter used in agile project management to assess the difficulty of executing a given user story.
15
참고 답변
Explore their pain points, gather feedback, and adjust the framework respectfully.
16
참고 답변
There is a step-by-step process that can be followed when guiding a scrum team. These steps are defined to acclimate the team members to using the agile methodology. It all begins with extending quality training to the members, imbibing a sense of collaboration and cooperation within the team by defining clear goals for everyone to achieve. Additionally, it also involves altering the perspectives and mindsets of the members, asking for continual feedback from both the internal and external parties, using productive tools and techniques to boost deliverables and following an iterative process throughout the cycle.
17
참고 답변
The candidate should describe a structured onboarding process, including assigning a buddy or mentor, introducing them to team norms and tools, providing context on current projects and past decisions, gradually involving them in Scrum ceremonies, and scheduling regular check-ins to address questions and build trust.
18
참고 답변
Finding a balance between documentation requirements and prioritizing functional software is crucial to upholding agility and productivity. Promote a practical strategy in which documentation improves comprehension and teamwork without causing delays. Important documentation like user stories and acceptance criteria is given higher importance to ensure the team is on the same page.
19
참고 답변
Scrum is a lightweight, agile framework for managing and completing complex projects. It emphasizes iterative and incremental delivery, using time-boxed iterations called sprints. Scrum is based on empiricism and lean thinking principles, focusing on collaboration, rapid feedback, and continuous improvement.
20
참고 답변
This could be considered something of a trick question, though you should know this if you're interviewing for a Scrum Master role. Scrum is part of the Agile philosophy, which has its own principles and values (as does Scrum). Essentially, Scrum is a framework that helps teams deliver value in a short period. So, while Scrum and Agile differ, they are part of the same methodology. Consider reading some agile blogs and agile books for deeper insights, and to shape an informed answer of your own.
21
참고 답변
A Scrum Master supports and promotes Scrum, assisting their Scrum team to meet goals and perform to the highest standards. They need to work with the team to identify risks to a project's success, and serve as a mentor/coach. The Scrum Master will help others in the organization understand how Scrum works, and why it matters, to ensure smooth collaboration. Strong motivation skills are fundamental, as Scrum Masters must help teams to maintain interest in projects and stay focused on their objectives over time. But remember: as Scrum Master, you're not the only one accountable for results — that falls on the Scrum team as a whole.
22
참고 답변
Impediment removal speed matters. Blockers that sit unresolved for days compound into sprint failures. My strategies include escalating quickly, building relationships with stakeholders who can remove blockers, and maintaining a visible impediment log.
23
참고 답변
A number of metrics can be used to measure project progress — team velocity, sprint burndown, capital redeployment, and time to market (to name just a few). Show that you know popular metrics and why they matter.
24
참고 답변
We can define a scrum sprint as a time-boxed period where a defined set of tasks is accomplished and presented to the stakeholders for review. In a scrum sprint, the deliverables primarily consist of the improvements and additions made to the product from the developers' end, as per the client's request and suggestions. A scrum sprint typically lasts for about one month (i.e. 3-4 weeks).
25
참고 답변
There are many ways to answer this, from burndown charts to burn-up charts, which are the standard metric for determining how much you've done within the time you've allotted for the work. But it's always good to know how the person measures the project, as it's the only way to determine how well things are progressing.
26
참고 답변
The effectiveness is measured by the team's progress in adopting Agile practices, improvements in delivery timelines, quality of work, and team satisfaction. Feedback from the team and stakeholders also provides valuable insights.
27
참고 답변
[Expect mention of CTC/CEC, ICAgile, peer mentoring, retrospectives.]
28
참고 답변
- Sashimi: A term used for a feature that is fully completed. - Impediments: Blockers preventing work progress.
29
참고 답변
I create a culture of psychological safety where team members feel comfortable raising issues without fear of blame. I explicitly ask about blockers and model vulnerability by discussing impediments openly. I also follow up on blockers promptly to show the team that raising them leads to action.
30
참고 답변
Effective dependency management involves early identification, clear documentation, and regular monitoring. I use tools like dependency matrices or Program Boards and facilitate proactive communication between teams.
31
참고 답변
By coaching on artifact clarity and supporting honest inspection and adaptation.
32
참고 답변
Use collaboration tools, set team norms, and coach on asynchronous communication.
33
참고 답변
- Requires experienced teams for effective execution. - It can be time-consuming with frequent meetings. - Less suitable for projects with fixed requirements. - Scope creep risk due to flexibility.
34
참고 답변
Daily Scrum is 15 minute sync up for the team which happens the same time – the same location every day. It helps the team self-organize towards their sprint goal and set the context for the day's work. It is an inspect and adapt meeting where they inspect if the progress towards sprint goal is good and adapt if any changes required. This sync up event sets the tone for the day and reduced the need for any more meetings throughout the day. Scrum Master makes sure this event happens and helps the team understand how to do a Daily Scrum effectively.
35
참고 답변
I ensure the proper implementation by guiding the team rather than policing them. Our goal is to build understanding and ownership, not compliance through authority. Here are the steps I usually follows.
36
참고 답변
Sometimes team members might be influenced by others' estimates. To address this, I ensure everyone understands the importance of independent thinking and encourage them to stick to their initial estimates unless convinced otherwise by the discussion.
37
참고 답변
The difference between doing Agile and being Agile is the difference between going through the motions and actually embracing an Agile philosophy toward work, life and relationships. There are many tools on the market that help you do Agile. You can have a list of product backlog items in Jira and schedule monthly sprint retrospectives on Teams, and pay lip service to the continuous delivery of software to your clients -- but that doesn't actually mean you're being Agile. It just means you're doing Agile things. To truly be Agile, you must embrace the concept that things constantly change, and constantly inspect and adapt to ensure your goals stay on target. That means you embrace an Agile mindset and push for Agile transformations throughout the organizations in which you work, not just in the localized development environment. Being Agile takes far more effort and commitment than simply doing Agile, but the extra effort is worth the reward.
38
참고 답변
Agile Release Planning involves outlining the roadmap for product releases over a period. It includes defining the goals, identifying key features, and estimating timelines. My approach emphasizes collaboration with stakeholders and continuous adaptation based on feedback and progress.
39
참고 답변
Ensuring the Scrum team remains adaptable involves creating a mindset that embraces change and a development process that accommodates evolving requirements. I emphasize the value of the Scrum framework, which inherently supports adaptability through iterative development and regular reassessment of priorities. During sprint planning, I encourage discussions around flexibility and the team's ability to pivot based on changing circumstances. Additionally, I maintain an open dialogue with the Product Owner to ensure the product backlog reflects the latest priorities. By fostering a culture that values adaptability and aligning the development process with agile principles, the Scrum team can navigate changes effectively.
40
참고 답변
Situation: A team struggled with meeting Sprint goals. Task: My goal was to identify and address the root cause. Action: I analyzed the Sprint Burndown and Velocity to identify inconsistencies in estimation and workload distribution. Result: This led to more accurate estimations and better workload management, improving Sprint completion rates.
41
참고 답변
Scrum has a defined set of guidelines, ceremonies and artifacts, but it's also a flexible methodology that allows scrum masters to apply their unique touch while guiding teams through the process of implementing scrum. This open-ended question allows employers to get a quick overview of how the scrum master being interviewed sees scrum and how he interacts with the scrum team and project stakeholders.
42
참고 답변
There are no definite best qualities for them. It changes with the teams and the organization they are working with. The common ones are as follows.
43
참고 답변
Agile has a new breed of PM tools including Rally Software, VersionOne, XPlanner, EasyBacklog, IceScrum, Agilefant, and Agilo. These tools bear no resemblance to the waterfall PM tools like MS Project or Clarity.
44
참고 답변
Any incomplete work getting postponed to the next sprint is called scope creep if it happens regularly. The work gets postponed to the upcoming sprints and we never catch up. This can be due to many factors like - Unclear requirements accepted in Sprint - Skills not available - Definition of Done is not clear - No intermediate and immediate Demo to PO and last minute changes suggested - Acceptance criteria keep changing - Silos in requirement implementation in place of combined ownership - Improper or no Backlog refinement To prevent it: - A proper and effective retrospective to understand the root causes and eradicate the top reasons for creep - The requirements must be clearly specified with acceptance criteria - Daily progress monitoring by team during Daily Scrum. - Effective backlog refinement of sprint backlog must be done. - Combined ownership of features/stories so that we focus on work completion than individual ownership and silos
45
참고 답변
Scrum artifacts are key deliverables that provide transparency and track progress: - Product Backlog: A list of all features and requirements. - Sprint Backlog: The selected backlog items for a sprint. - Increment: The working product delivered at the end of a sprint.
46
참고 답변
Backlog refinement, also popularly known as backlog grooming, is an ongoing (continuous) process where the agile team goes through a sequence of steps to oversee the development done to that date. This involves assessment, elucidation, prioritisation and estimation of the product backlog items to ensure the top-ranking items in the backlog are ready for release. Since this is a regular, systematised activity, it often takes place through planned meetings. A few key aspects of the Backlog Refinement process are mentioned below: - New, useful ideas are taken into consideration - Irrelevant user stories are removed from the list - Stories are adjusted all over again based on priority - Stories without a specified estimate are allotted one - Items are categorised as per priority, using story points - Complex items are simplified into small, manageable chunks - Dependencies are identified in the tasks, and collaboration is done - Estimations are reworked, provided new data is found
47
참고 답변
SAFe (Scaled Agile Framework) uses Scrum as the team-level delivery mechanism within a larger program structure. Key integration points include synchronization at the Program Increment (PI) level and alignment with larger organizational goals. Understanding where Scrum ends and the broader SAFe structure begins is important for Scrum Masters operating in SAFe environments.
48
참고 답변
I track different metrics for this purpose. These metrics focus on flow, predictability, quality, and continuous improvement, rather than individual productivity. The goal is to understand how effectively the team delivers value and how consistently they improve over time. Metrics include: Velocity, Sprint Goal Success Rate, Cycle Time, Lead Time, Burndown Chart, Defect Rate, Escaped Defects, Retrospective Action Completion, and Team Happiness/Engagement.
49
참고 답변
One of the most common approaches for evaluating teamwork is to estimate in man-hours. While man-hours are simple to comprehend, they have a number of significant drawbacks: - Few activities, such as legacy work, are difficult to estimate precisely. - If one team member delivers the estimate but the task is completed by another, the estimate is useless. - The amount of time it takes to perform a task depends on the developer's level of experience. - Teams frequently overestimate the obstacles they may face and simply consider the best-case scenario. The benefits of estimating user stories in points include the following: There is no association between the estimator's skills and experience, and story points are independent of the story's author. The team members can estimate more correctly since story points are a measurement of relative sizes, and the size of the story cannot be changed by external forces. As team behavior takes precedence over individual conduct, Story Points encourages collaboration. The team comes together when they use planning poker to estimate story points. As teams exchange, constructively criticize, argue, and have fun playing poker cards to arrive at an agreement on estimations, it serves as a team-building activity.
50
참고 답변
A process control theory emphasizing transparency, inspection, and adaptation.
51
참고 답변
Code coverage is managed by setting realistic targets and using automated tools to track coverage. Regular code reviews and encouraging a culture that values thorough testing help in maintaining and improving code coverage.
52
참고 답변
That is quite concerning if the Product Owner is absent. There are a few things to figure out here. I would need to speak with the Product Owner to understand why they don't have time with the team on a regular basis. It might be that they don't really understand their role and how much time they need to dedicate to the Product Backlog management and to the team. They also might be spread too thin. And then the question would be whether we have the right person to play the role of the Product Owner. We need to have someone who can work closely with the team, and if they are too busy doing something else, another person may be a better fit. One more thing that comes to mind is if our Product Owner is actually a proxy, as in, they always need to ask someone else for the approval or additional information and that is what's taking so much time. There definitely will be some opportunities for knowledge transfer and delegation. Then I'm also thinking about the Backlog Refinement - is it even happening? And if yes, how productive is it? Does the Product Owner attend? There might be some improvements we can implement around regular refinement.
53
참고 답변
I ensure the timely delivery of action items in Scrum by making them visible, owned, and prioritized just like regular backlog items. Instead of treating action items as side tasks, I integrate them into the team's workflow, assign clear ownership, and track progress regularly. I also keep them small and achievable within a sprint, and review their status frequently to ensure follow-through.
54
참고 답변
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.
55
참고 답변
I assess the team's capacity and throughput to set WIP limits, adjusting them as we review our workflow and gather data on our efficiency and delivery rate.
56
참고 답변
I actively work to remove impediments, whether they are technical, organizational, or process-related. I prioritize the team's needs and advocate for them with management. I also coach the team to become more self-sufficient in resolving their own obstacles over time.
57
참고 답변
Yes, we can very well do our daily stand-up meeting.
58
참고 답변
The Scrum Master has to be present during the following events: - Sprint Planning: Here, the whole team participates and decides the scope and task list for the project. At this stage, the Scrum master aids in estimating the task list and resolving questions. They also help the team decide on what could be delivered realistically. - Daily Stand-Ups: A Scrum Master must initiate and facilitate daily stand-ups to inspect the project's progress and check on the team members. - Sprint Review: The entire Scrum team and stakeholders participate in this meeting to review completed work and update accordingly. - Retrospectives: After the sprint review, the Scrum master and the entire team attend the retrospective to examine how the just-completed sprint went, how the team performed, and note areas of improvement for the team for future sprints. - One-on-One Meetings: The Scrum master meets individually with the team members to address any roadblocks and resolve them.
59
참고 답변
Techniques like user story mapping, estimation games, and defining acceptance criteria are useful. These help the team break down complex items, estimate effort, and understand requirements better.
60
참고 답변
The candidate should provide a concrete example of an impediment they identified and resolved. For instance, they might describe a situation where a team was blocked by a dependency on another department, and they facilitated a cross-team meeting to prioritize the task, or where a technical debt issue was slowing progress, and they worked with the team to allocate time for refactoring within the sprint.
61
참고 답변
Predictability improves when: - Backlog refinement is strong - User stories are properly sliced - Capacity planning is realistic - External interruptions are minimized I track planned vs completed trends across multiple Sprints to stabilize forecasting.
62
참고 답변
- A servant-leader is someone who : - Focuses on establishing a trusting relationship. - Encourages transparency and empowerment. - Encourages teamwork and collaboration - Demonstrates ethical and compassionate behavior by prioritizing the needs of others. - Is humble, well-informed, upbeat, socially conscious, and situationally aware. A Scrum Master is a master at motivating, enabling, and inspiring individuals to work together as a team and reach their maximum potential. A Scrum Master is a servant-leader who prioritizes the needs of team members and those they serve (customers), with the purpose of generating results that are consistent with the organization's values, principles, and goals. The Scrum Master's responsibilities as a servant-leader include: - Setting Scrum up as a servant rather than a commanding process. - Assisting the Development team in becoming self-organized. - Guiding the group via constructive conflict and debate. - Scrum adoption and use are taught, coached, and mentored by the organization and team.
63
참고 답변
I encourage regular reflection in Sprint Retrospectives to identify improvement areas. I also promote a learning culture to help the team improve continuously.
64
참고 답변
- Regular Retrospectives: Encouraging open discussions on what went well and areas to improve. - Actionable Feedback: Implementing changes based on retrospective insights. - Knowledge Sharing: Promoting cross-training, workshops, and mentorship. - Experimentation: Trying new approaches and adapting based on results. - Encouraging Open Communication: Creating a safe space for feedback and new ideas.
65
참고 답변
A manager once asked the team to add a new feature during a Sprint. I explained the impact on the Sprint goal and suggested adding it to the Product Backlog for the next Sprint. I protected the team's focus by absorbing the pressure myself and deferring the request.
66
참고 답변
T-shirt sizes are helpful during initial backlog estimations or when dealing with high-level items. They're less granular and more intuitive, making them suitable for early project discussions or with teams new to Agile.
67
참고 답변
If the team often misses what they plan to do in a sprint, I try to find the real reasons behind it. I do not blame anyone. I use the Sprint Retrospective to start an open talk with the team. We look at things like overcommitting during sprint planning, unclear user stories, or any problems that come from outside the team. It helps to get some data so we can make good choices. After we find out more, we make a plan to get better. This plan might include: - We use the team's past speed, known as team velocity, to help us make better plans. - We work on making our list of tasks clearer and easier to follow. This helps us be sure each story is set and good to go. - We point out things that slow us down and fix them early. This helps us do better as a team all the time.
68
참고 답변
I remind the team of the Daily Scrum's purpose and time limit. If conversations drift, I suggest taking them offline after the meeting, ensuring the Daily Scrum remains concise and on track.
69
참고 답변
As we noted above, the scrum master is a unique position. Scrum has three main roles, which are the product owner, scrum master and delivery team. They're cross-functional but not shared among other projects. But not all projects follow these rules precisely. How you run the organization and how well the candidate can be flexible or has experience in your way of doing the work will determine how good a fit they'll be.
70
참고 답변
The four values of Agile Software Development, as stated in the Agile Manifesto, are: - (Content not explicitly listed in the provided text beyond the introductory statement).
71
참고 답변
The Scrum Master's role is to facilitate the Sprint Review, ensure the event stays within its time-box, encourage stakeholder feedback, and help the team present their work effectively. The Scrum Master does not present the work themselves but ensures the event runs smoothly.
72
참고 답변
The five major events that are involved in a scrum framework include: - The Sprint: Known as the Scrum fundamental, the sprint is defined as a fixed duration that typically lasts for about one month or, at times, less than that, to deliver a valuable product. - Sprint Planning: As the term makes it evident enough, sprint planning is all about structuring the ultimate sprint goal, typically scheduled at the onset of the sprint, where the scrum team collaborates to evaluate the what, why, and how behind a product delivery. - Daily Scrum: A short, everyday meeting that typically runs for 15 minutes to oversee the overall development of the work done towards achieving the final Scrum goal. This also involves curating the next day's plan for the team to work on. - Sprint Review: Usually takes place at the closure of the Sprint to assess the status of the development done to date and update the product backlog. In this, future decisions are taken based on the inputs received from the stakeholders and clients. - Sprint Retrospective: This is the last leg of the Sprint, where the Scrum team assesses their process and focuses on the areas of concern that can be taken care of in the next sprint, so that effectiveness can be maintained.
73
참고 답변
A User Story is a simple description of a feature or functionality from the user's perspective. It's written in a way that focuses on the value the feature brings to the user, usually following this format: "As a [type of user], I want [a goal] so that [I can achieve a benefit]." Example: "As a customer, I want to be able to reset my password so that I can regain access to my account if I forget my password."
74
참고 답변
I would avoid taking sides. Approach: - Separate facts from emotions - Facilitate structured dialogue - Bring the conversation back to the Sprint Goal - Reinforce shared ownership Conflict is natural. Unresolved conflict is toxic.
75
참고 답변
Metrics employed to measure the work completed by Scrum teams include: [not explicitly listed in the text, but implied from context]
76
참고 답변
I would organize a retrospective focused on estimation accuracy. We would analyze past estimations and outcomes, discuss discrepancies, and work together to find ways to improve future estimation accuracy.
77
참고 답변
I would: - Check workload balance - Explore personal constraints - Review clarity of stories - Offer support Accountability comes after understanding context.
78
참고 답변
Scrum values are the key elements that form the bedrock for team behavior, foster trust, and enable effective collaboration. This helps to achieve goals within the framework, guide how teams interact, make decisions, and deliver value by supporting the core pillars of transparency, inspection, and adaptation. They give purpose to the practices to prevent them from becoming rote.
79
참고 답변
Inspect the cause, address impediments, and coach on planning realism and focus.
80
참고 답변
Scaling Scrum for more than one team means using tools like SAFe or LeSS. These tools help teams work together, stay on the same page, and use effective communication. When you focus on teams working with each other and set up clear rules, it is easier to handle any work that connects different groups. This helps everyone move toward the same project goals as one team.
81
참고 답변
It's only natural that conflict among team members will happen. When it does, it's important that a Scrum Master can resolve it quickly, with calmness, empathy and a healthy dose of communication. Listen for: Your candidate's ability to de-escalate a situation. Pay attention to their conflict resolution skills and how they manage to take care of their team members in the face of an internal issue. It would be helpful if they mention one-to-one meetings, encouraging team members to come up with a solution and bringing the issue to leadership only if necessary.
82
참고 답변
The definition itself should be relatively simple and easy to understand. Your candidate should also be able to speak about the importance of Scrum (including how it can benefit your team and add value to your business). Listen for: Your candidate's ability to address ways that Scrum can help your company specifically. They should have a strong idea of what it means to be a Scrum Master and why it's a key role for an Agile team. Additionally, listen out for mention of the artifacts of Scrum.
83
참고 답변
Sprint Retrospective is a meeting where the team reflects on the Sprint and identifies improvement actions. It strengthens continuous improvement and team maturity.
84
참고 답변
Ensuring alignment between the Scrum team and the organization's strategic goals involves regular communication and collaboration. I establish clear channels for information flow between the team and organizational leadership, ensuring that the team understands the broader strategic context. During sprint planning and review meetings, I emphasize the connection between the team's work and the achievement of organizational objectives. Additionally, I encourage collaboration with stakeholders and departments outside the immediate team to promote a holistic understanding of the organization's goals. By fostering a sense of purpose and alignment, we ensure that the Scrum team's efforts contribute directly to the organization's overall success.
85
참고 답변
A Scrum master is a project leader who uses Agile techniques. He collaborates and communicates between team members and the project manager to ensure proper outcomes. - He/she mentors the development team and product owner so that they can easily understand the Agile process thereby contributing effectively in their role and dedication to the project. - He/she tracks the project at regular intervals and shares the updates with the product stakeholders. - He/she eliminates external blocker and internal roadblocks by assessing the workflow.
86
참고 답변
I emphasize the importance of Agile ceremonies, ensure they are effectively conducted, and encourage the team to reflect on Agile principles regularly. Maintaining Agile discipline is key to success in a fast-paced environment.
87
참고 답변
Scrum is a specific framework with defined roles, events, and artifacts. Unlike Kanban, which focuses on continuous flow, Scrum works in fixed-length Sprints. It provides more structure than extreme Programming (XP) in terms of management, but it can be combined with XP's technical practices.
88
참고 답변
The three daily Scrum questions are: - What did I do yesterday? - What will I do today? - Are there any impediments or blockers? These questions help ensure team members are aligned and aware of each other's progress and challenges. While they are commonly used, they should be adapted or modified if they do not add value to the team's daily Scrum discussions.
89
참고 답변
Scrum is a combination of iterative and incremental model.
90
참고 답변
Situation: A project I managed had shifting requirements and tight deadlines. Task: My task was to deliver the project successfully despite these challenges. Action: I focused on maintaining regular communication with stakeholders and the team, frequent backlog refinement, and adaptive planning. Result: Despite the challenges, the project was delivered on time and met all key requirements.
91
참고 답변
The Product Backlog contains all the work needed for the product, while the Sprint Backlog is a smaller subset of the Product Backlog. The Sprint Backlog is selected by the team during Sprint Planning and focuses on the tasks to be completed in the current sprint. Interview questions for Scrum Master often revolve around your experience with Scrum ceremonies, such as sprint planning, retrospectives, and daily stand-ups.
92
참고 답변
On a philosophical level, Scrum rests on "three pillars of empiricism": - Adaptation (changing as circumstances demand) - Transparency (know everything that's going on) - Inspection (check your work and establish good feedback loops)
93
참고 답변
Scrum is an Agile framework that helps teams work together. Scrum can enable teams to learn from experiences, self-organize while working on problems, reflect on their victories and failures, and make improvements. This Agile Scrum interview question is often used as a starter question to get the interview moving.
94
참고 답변
Resistance usually means: - They do not see value - Previous Agile experience failed - Change fatigue I would: - Start with the why - Show measurable improvements - Remove ceremony overhead - Focus on outcomes, not rituals Agile adoption succeeds when teams feel benefit, not enforcement.
95
참고 답변
First, understand the urgency drivers. Then: - Quantify trade-offs - Make WIP visible - Present impact on the current Sprint Goal - Offer data-driven decision options Agility does not mean saying yes to everything. It means making informed decisions transparently.
96
참고 답변
While each member of a scrum team has a unique set of skills that allow them to excel at certain areas of work, the scrum master uses the scrum artifacts to see the big picture of an agile project. They can be seen as the scrum master's toolbox which allows him or her to have a clear understanding of what a project is about. They can assist the scrum teams and help them to find the best way to prioritize and coordinate their efforts. The seven scrum artifacts are the product vision, product backlog, sprint vision, sprint backlog, the definition of done, product increments and burndown chart.
97
참고 답변
Analyzing both quantitative and qualitative criteria is crucial to verify the efficiency of a Scrum team. Regarding quantity, tracking metrics like speed, burndown charts, and sprint progress ensure a steady value delivery. Evaluating team satisfaction, effectiveness of collaboration, and adaptability to change provides further qualitative insights. By combining these strategies, you can understand how the team is doing and identify areas that need continual enhancements.
98
참고 답변
Burn-down chart is a graph that shows the estimated v/s actual effort of the scrum tasks. It is a tracking mechanism by which for a particular sprint; day to day tasks are tracked to check whether the stories are progressing towards the completion of the committed story points or not. Here, we should remember that the effort is measured in terms of user story points and not hours.
99
참고 답변
DoD stands for "Definition of Done." It's a clear and concise set of criteria or standards that must be met for a Product Backlog item to be considered completed or "done." The Definition of Done is established collaboratively by the Scrum Team, typically during Sprint Planning or early in the project, and serves as a guideline for the quality and completeness of work. The Definition of Done may include various criteria, such as: - Code being reviewed and merged - Automated tests passing - Documentation being updated - User acceptance testing (UAT) completed - Product increment demonstrated and accepted by the Product Owner
100
참고 답변
Timeboxing limits activities to a fixed duration to ensure focus, discipline, and predictable delivery cycles.
101
참고 답변
The Scrum framework includes five key events, each serving a specific purpose to ensure the team stays aligned and productive: - (Content not explicitly listed in the provided text beyond the introductory statement).
102
참고 답변
During a project, if the requirements are not properly defined and additional features are added to an existing product, scope creep occurs. There are points to consider to prevent scope creep: - (Content not explicitly listed in the provided text beyond the introductory statement).
103
참고 답변
There are multiple approaches to it. Scrum has given SoS (Scrum of Scrums Model) which is very simplistic or there are quite a few situation specific and proven models like - SAFe ( Scaled Agile Framework ) - Nexus - And many more We can use anything suitable or even customize one for ours based on need and taking learning's from above. Scrum@Scale by Jeff Sutherland (Co-Creator of Scrum)
104
참고 답변
One popular technique is to follow the 15-10-5 rule: - 15% of a team's capacity to technical debt. - 10% to bugs and defects. - 5% to exploring new ideas. This distribution ensures enough attention is given to cleaning up code and technical upkeep. Such a setup should be discussed with the product owner and the necessary stakeholders beforehand to avoid misunderstandings.
105
참고 답변
Subject: Update on Release Timeline Dear [Client Name], I hope this message finds you well. I am writing to inform you that after our mid-iteration assessment, we have identified internal team reasons that require us to adjust the release timeline significantly. We understand that this impacts your marketing and operational activities that depend on the product release date. To minimize disruption, our next steps include: (1) Conducting a root cause analysis to prevent future delays, (2) Re-prioritizing the backlog to deliver the most critical features first, (3) Increasing collaboration with your team to align on revised milestones, and (4) Providing regular updates on our progress. We apologize for any inconvenience and are committed to delivering a high-quality product. Please let us know if you have any questions or would like to schedule a call to discuss the revised plan. Best regards, [Your Name]
106
참고 답변
Cancellation of a sprint is generally a rare case as there are losses associated with it. Cancellation seems viable only in case of the Sprint Goal is no more valid and changes cannot be finished in the given sprint. A Sprint can be canceled before the Sprint time box ends & only the Product Owner can cancel the sprint. In case of cancellation, the DONE PBI's (PBI = Product Backlog Items) are marked done and remaining goes back to PB. After this we plan for new sprint. Issues: This can be a little impractical in case if there are multiple teams working together on the same Product and all the teams are dependent on each other. However, the situation sensitivity needs to be exercised in such cases.
107
참고 답변
During a retrospective meeting, the Scrum Master facilitates the session. Their responsibilities include: [not explicitly listed in the text, but implied from context]
108
참고 답변
The Sprint Review is important for gathering stakeholder feedback and aligning the product direction. The Sprint Retrospective is important for the team to inspect its own process and make improvements, ensuring continuous improvement in how they work.
109
참고 답변
Agile is a broader project management philosophy emphasizing flexibility and continuous iteration. Scrum, on the other hand, is a specific Agile framework that structures projects into sprints with defined roles and ceremonies. While Agile is more flexible, Scrum provides a structured approach to deliver results quickly.
110
참고 답변
Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective, and Sprint itself.
111
참고 답변
Project management software greatly increases the productivity of scrum teams. Therefore, any scrum master should be familiar with agile project management software tools like kanban boards, Gantt charts, project dashboards and any other features to help them plan and track agile sprints.
112
참고 답변
I support product owners by helping to create a prioritized and well-understood backlog for the Dev team.
113
참고 답변
A user story is a short description of a feature from the perspective of the end user. The standard format is: As a [type of user], I want [some goal] so that [some reason]. Good user stories follow the INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, and Testable.
114
참고 답변
The team must identify action items in order for the retrospective to be effective. This provides the team with a starting point for a discussion, but simply naming will not suffice. The action items should be closed as soon as possible, and the scrum master should take steps to accomplish this. Every action item should have an owner, and teams should avoid assigning several owners to a single item because ownership becomes diluted. The scrum master should keep track of action items in a programme or spreadsheet that is accessible to everyone on the team. Having a backlog of action items is also beneficial since it allows the team to prioritize.
115
참고 답변
The Product Backlog is a prioritized list of all features, enhancements, and fixes required for the entire product and is owned by the Product Owner. The Sprint Backlog is a subset of the Product Backlog selected for a specific Sprint, owned by the Development Team, and includes a plan to deliver the Sprint Goal.
116
참고 답변
Scrum teams utilize various metrics to gauge their performance and progress. Here are some key metrics: - (Content not explicitly listed in the provided text beyond the introductory statement).
117
참고 답변
I acknowledge the conflict and reframe it as a topic for constructive discussion. I facilitate the conversation to understand all perspectives and guide the team towards a solution that benefits the team's process. If necessary, I take the discussion offline to resolve it privately.
118
참고 답변
I assess the causes of the delay, re-prioritize tasks, and if necessary, negotiate scope or deadline adjustments with stakeholders, ensuring transparent communication throughout the process.
119
참고 답변
I stay updated by attending workshops, taking additional Scrum Master Training, and staying involved in the Agile community. Whether through advanced training or learning from real-world experience, I ensure I keep my knowledge fresh and relevant to the current trends in Scrum.
120
참고 답변
Two other agile methodologies apart from Scrum are KanBan and Lean.
121
참고 답변
The ideal Scrum team size is 3 to 9 members, excluding the Scrum Master and Product Owner. This range allows for effective communication and flexibility while ensuring the team has enough skills to complete tasks efficiently. Teams smaller than three may lack the necessary skills, and teams larger than nine can face communication challenges.
122
참고 답변
Here are the benefits of implementing the Scrum framework: - The Scrum Masters are responsible for promoting and facilitating Scrum. - They help their colleagues reach their expectations, handle project risks, and advise the Team as coaches. - The Scrum Masters are also regarded as servant leaders, offering cohesion and inspiring their Squad to achieve the best they can.
123
참고 답변
MoSCoW Method – Categorizes user stories into Must-have, Should-have, Could-have, and Won't-have. Kano Model – Prioritizes based on customer satisfaction and functionality.
124
참고 답변
For any project or product development, we need an efficient framework to empower members, individuals, and organizations with agile practices, agile approaches, principles, and values.
125
참고 답변
Release Candidate is software that is yet to be developed in its final stage. It's the preview of the software. The core focus of the release candidate is on the functionality, security codes, and quality.
126
참고 답변
Scrum is a type of iterative model only but it is iterative + incremental.
127
참고 답변
A Sprint Goal is a single objective that provides focus and purpose for the Sprint, guiding the team's work and decisions.
128
참고 답변
We had a director who kept asking us to commit to fixed scope over fixed time. She wanted to tell customers exactly what we'd deliver and when, which kills the benefit of Agile. Instead of telling her she was wrong, I suggested a conversation where I showed her the data from two teams—one with fixed scope that missed dates constantly, and one with fixed time that shipped on schedule but with flexible scope. Then I asked her what was actually important to her: shipping on time, or shipping every feature? She said on time. Then I explained that we could guarantee delivery dates if we gave ourselves flexibility on features. We worked out a model where she got predictable release dates, and the team got realistic commitments. Everyone won.
129
참고 답변
An informal, general description of a software feature written from the viewpoint of the end user is called a user Story. Its goal is to clarify how a feature of the software could help the user. Agile software development places a strong emphasis on prioritising people, and a user narrative effectively does this by placing end users at the center of the conversation. The development team and their work are described in these anecdotes using simple language. The team knows why they are developing, what they are building, and what value it brings after reading a user story. Benefits of using user stories in Scrum include: - User-Centric Focus: User stories emphasize the needs and goals of end users, helping teams to prioritize features and functionalities based on their value to users. By focusing on user needs, teams can deliver products that better meet customer expectations and satisfaction. - Easy to Understand: User stories are written in plain language and follow a simple template, making them easy to understand by all stakeholders, including non-technical team members and customers. This clarity promotes collaboration and ensures a shared understanding of project requirements. - Incremental Delivery: User stories support the iterative and incremental development approach of Scrum. By breaking down requirements into small, manageable chunks, teams can deliver value to customers incrementally with each iteration, enabling faster time-to-market and feedback. - Flexibility and Adaptability: User stories allow for flexibility and adaptability in responding to changing requirements and priorities. They can be easily added, modified, or reprioritized based on feedback, new information, or evolving business needs, without disrupting the overall project plan.
130
참고 답변
I had a mid-level developer who was really talented technically but would sometimes code review other people's work dismissively—basically rejecting PRs without explaining why. I could see it was damaging relationships. In our one-on-one, I said, ‘I've noticed your code reviews have been brief, and a couple people mentioned they didn't understand your feedback. I know you're thorough, and I think you want people to learn from your suggestions. Can we talk about how to make the feedback more constructive?' He was defensive at first, but I pointed to a specific example. We talked through the fact that his style could come across as gatekeeping rather than mentoring. He agreed to be more explicit in his reviews. Over the next sprint, I saw a real shift. He started explaining why he was suggesting changes, and the team actually started valuing his reviews more because they were learning something.
131
참고 답변
To keep up with the daily work without any hindrances and delays, and to sustain a healthy and sound environment for everyone in the team, it is important to resolve the conflicts that arise. As a scrum master, make sure whenever you come across a situation like this, you take time to reflect first, rather than react. Have a word with the respective team members so you can understand their points of view before you conclude something out of it. Identify the issue and have a one-on-one discussion with the members, where you can suggest to them alternatives they can consider to resolve the issue. While speaking to both team members, show how each of their roles and responsibilities is dependent on one another and how they both play a crucial role in the project and therefore their collaboration is valuable for the company's goals.
132
참고 답변
My response in the moment is to have a direct conversation about the impact on the sprint goal and team focus. My longer-term response involves working with the Product Owner to improve backlog prioritization and refinement so that mid-sprint changes are minimized.
133
참고 답변
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.
134
참고 답변
I empower the team to self-organize by letting them decide how to do the work. I avoid assigning tasks and instead let team members pull work from the Sprint backlog. I celebrate ownership and hold the team collectively accountable for the Sprint goal, not individual tasks.
135
참고 답변
A scrum master is in charge of the scrum team and oversees whether they follow the scrum rules to deliver the product. They are primarily the coach who instructs and guides the team members to integrate Scrum practices into their work, schedule meetings (including daily stand-ups, sprint planning and retrospective sessions), and identify problem areas to deliver successful solutions. On the other hand, the project managers are responsible for seamless handling and timely delivery of projects to the stakeholders and clients. Project managers are the ones who outline projects, define timelines, maintain clear communication with the client party, allocate the required resources and funds to projects and constantly keep an eye on how things turn out. In addition to this, they also keep a plan B ready, which comes into action during contingency situations.
136
참고 답변
By maintaining a prioritized backlog and conducting regular backlog refinement sessions, scope creep is managed. Any changes in scope are discussed with stakeholders, assessing their impact on timelines and resources.
137
참고 답변
Talking about technical debt means having clear talks with the team about how it can hurt how fast you work and the quality of what you make. Make a list of the things you need to fix and give them an order. Write them down. Work with everyone to plan together, and make sure all important people understand why fixing technical debt should be part of upcoming sprints. Doing this helps make every project go well.
138
참고 답변
Waterfall is best for projects with well-defined, fixed requirements, such as construction or manufacturing. If the scope, timelines, and budget are rigid, Waterfall may be more suitable than Scrum, which works best for projects with evolving requirements and the need for flexibility.
139
참고 답변
A Scrum Master has three areas of service: the Product Owner, the Developers, and the organization.
140
참고 답변
The key features of agile are: - Daily stand-up meetings - CRC (Class Responsibility Collaborator) cards - Timeboxed task boards - TDD (test-driven development), continuous integration, regular code reviews, pair programming, continuous deployment and delivery, automated builds, etc. - Iteration planning meetings and iterative development
141
참고 답변
A user story is a tool used in the development of Agile software that captures a feature's explanation from an end-user perspective. It explains users' forms, motives, and other aspects of their behavior. A user narrative provides a condensed explanation of what a customer wants. User Story Format: “As a [role], I want [goal/desire] so that [benefit].” Example of a User Story: “As a customer, I want to receive an email notification after I place an order so that I can confirm that my order was successful.”
142
참고 답변
By enforcing: - Stable Sprint scope - Clear Definition of Ready - Product Owner prioritization discipline - Transparent backlog visibility
143
참고 답변
- Product Backlog: It is a list that consists of new features, changes to features, bug fixes, changes to the infrastructure, and other activities to ensure a particular output can be obtained. - Sprint Backlog: It is a subset of the product backlog that contains tasks focused on by the team to satisfy the sprint goal. Teams first identify the tasks to be completed from the product backlog. These are then added to the sprint backlog. - Product Increment: It is a combination of all product backlog items completed in a sprint and the value of previous sprints' increments. The output must be in usable condition, even if the product owner doesn't release it.
144
참고 답변
- A solid grasp of the concepts of Agile and Scrum - While not always required, having a basic understanding of the technical aspects of software development can be beneficial for a Scrum Master in facilitating discussions and understanding the team's work. - The ability to coach the team on Agile principles and practices, providing guidance, support, and encouragement to help them continuously improve and deliver value. - Strong communication skills are vital for a Scrum Master to facilitate collaboration, convey information clearly, and foster a culture of transparency within the team and with stakeholders.
145
참고 답변
Burndown and Burnup charts are visual Agile tools tracking project progress. Burndown charts track remaining work. These charts add a scope line to show new work, which provides a fuller picture of scope changes. Burnup charts track completed work. These charts offer a simple view of work left to finish a fixed set of tasks.
146
참고 답변
An ideal timeframe for a sprint can be two to four weeks.
147
참고 답변
An effective Scrum Master must possess strong communication and facilitation skills to ensure team alignment and productivity. Additionally, they should foster a collaborative environment and be adaptable to changing circumstances, always prioritizing the team's needs.
148
참고 답변
To measure how well a scrum master is doing, you need to look at how the team is working and what they get done. The main things to check are team velocity, how many sprints the team finishes, and if the people that have a stake in the work are happy. There is also value in asking the team for feedback in meetings after each sprint. This can help you see if the scrum master is helping the team feel good about their work and stay productive.
149
참고 답변
GROW, ORSC, Clean Language, Systemic Coaching.
150
참고 답변
I celebrate team achievements, both big and small. I encourage social bonding activities and ensure the team has a healthy work-life balance. I also address negative behavior or conflicts quickly to prevent them from poisoning the culture.
151
참고 답변
The techniques used for estimation in Scrum are-
152
참고 답변
Scrum is an iterative and incremental product development framework that helps teams get started and keep going. In contrast, Kanban is more singularly concerned with visualizing how work and tasks move through the software development process. Scrum describes itself as an incomplete framework. Teams can include best practices from various popular processes and methodologies into their development practices. Many Scrum teams use Kanban boards to help gauge progress and minimize the amount of work in progress while they implement the various practices prescribed by the Scrum Guide. Scrum always encourages teams to experiment, explore and embrace new practices that make them more effective. If a team believes Scrum and Kanban will help them better achieve their sprint goals, then they are definitely encouraged to experiment and combine them.
153
참고 답변
Agile is a collection of values and guiding principles stated in the Agile Manifesto, which is a mindset together with a philosophy that is used in software development. Scrum is an example of a framework that applies Agile principles. While Agile tells us what to value, such as individuals and interactions over tools and processes, Scrum outlines a framework for how to implement those values through roles, events, artifacts, and rules. It is more helpful to think of Scrum as a possible 'how' and Agile as the 'why', being centered in delivering value instead of following a process.
154
참고 답변
Scrum artifacts are key tools that provide transparency, facilitate collaboration, and enable teams to track progress throughout the Scrum process. They serve as essential sources of information for stakeholders and help ensure that everyone involved in the project clearly understands the work being done. The primary Scrum artifacts include: (content not explicitly listed in the provided text beyond the introductory statement).
155
참고 답변
A Spike is an Enabler Story that checks out the viability of a proposed technical approach, gains the knowledge necessary to understand a requirement, or optimizes the reliability of a story estimate.
156
참고 답변
Their answer will let you know if they see themselves thriving in your particular work environment and what they'll bring to the team. Listen For: Examples of their strong communication skills, a collaborative spirit, and leadership qualities. Their answer should also demonstrate organizational skills and attention to detail.
157
참고 답변
The only rule the Scrum Guide provides about the length of an Agile sprint is that it must be a calendar month or less. Beyond that guidance, the established length is up to the team to decide. The project's vulnerability to risk is one of the primary factors to consider when establishing how long or short a sprint should be. The further you envision a project into the future, the wider the cone of uncertainty becomes. To minimize risk, two-week sprints are preferable to ones that last a month. At the same time, teams must also factor in stakeholder involvement. At the end of every sprint, stakeholders are expected to participate in a sprint review, which may take up to four hours of their time. If a Scrum team has sprints that last a week, stakeholders might get annoyed that their Friday afternoon calendar is blocked off indefinitely to inspect the team's progress. New projects, where uncertainty is the greatest, often have short, two-week sprints. As projects mature, the sprint length's duration might creep up to three or four weeks -- but under no circumstances should the sprint length ever exceed a single calendar month.
158
참고 답변
The correct answer to this is yes. Agile requires a lot of feedback from both customers and stakeholders. The goal is to improve the product. Change is the constant in agile, so much as it's embraced as a means of getting the project done better and faster.
159
참고 답변
Scrum is a framework for implementing Agile project management. It involves roles, events, artifacts, and values that help teams self-manage and deliver value iteratively. Scrum brings value to a team and business by promoting adaptability, transparency, and continuous improvement. Its advantages include faster delivery, better quality, and increased team collaboration.
160
참고 답변
Scrum artifacts are documents that provide stakeholders and the Scrum team information about the project scope, progress, and action plan. The three Scrum artifacts are- the product backlog, sprint backlog, and product increment. - Product Backlog: It is an ordered list of everything needed to build a product. It includes a short description of the desired features, bugs to be resolved, and more. - Sprint Backlog: A document stating the tasks that a team wants to accomplish during a sprint. - Product Increment: At the end of each sprint, the product increment document states the deliverables achieved by completing the product backlog tasks.
161
참고 답변
Agile is a mindset based on the Agile Manifesto principles, while Scrum is a framework used to implement Agile. Agile defines values like customer collaboration and adaptability. Scrum provides structured roles, events, and artifacts to apply those values in real projects. Agile = philosophy Scrum = execution framework
162
참고 답변
Every scrum team indeed undergoes a lot of pressure when it comes to keeping up with the targets. But it is important to set boundaries in addition to maintaining the work progress. What the team can do here is that they can remain clear about the deliverables they can make within a defined timeline (set realistic targets), assess how much they can easily deliver without feeling overwhelmed (burnout), and swap the visual work board in front of them with only one checklist of priority items they are working on presently. In addition to these, advise the team members to take breaks, and refuse additional work if not informed beforehand and openly highlight imbalanced work-life issues so that things can be improved.
163
참고 답변
I frame conflicts as opportunities for better solutions. I facilitate discussions where each viewpoint is heard and evaluated based on facts and the project's goals. I encourage the team to experiment with different approaches and use data to decide which one works best.
164
참고 답변
I foster a culture of open communication by encouraging daily stand-ups, pairing, and collaborative refinement sessions. I also help the team establish shared norms for communication and use tools that facilitate transparency, such as task boards and chat channels.
165
참고 답변
If you're unfamiliar with the waterfall model (in which a product lifecycle's progress flows through a linear sequence of phases), now's the time to change that. If you're asked this question, you'll need to explain that there's no change management plan in Agile, as work delivery is based on the product backlog definition. But in the more rigid waterfall, change management depends on the change management plan, change tracker, and release plan instead.
166
참고 답변
Timeboxing in Scrum refers to the practice of allocating a fixed amount of time to specific activities, events, or tasks within the Scrum framework. Timeboxing helps create a sense of urgency, maintain focus, and ensure that activities are completed within predefined time limits. timeboxing is a valuable practice in Scrum for managing time effectively, maintaining focus, and ensuring that activities and events are completed within predefined time limits. It encourages disciplined and efficient work practices while providing a framework for predictable and sustainable delivery.
167
참고 답변
A scrum master candidate must explain how these artifacts help manage the development process, ensuring that all team members understand the tasks and the product features being developed. They should illustrate their role in guiding the team through backlog refinement and emphasizing the importance of the sprint goal in every new sprint.
168
참고 답변
The product backlog is a dynamic list of all the features, enhancements, bug fixes, and technical work needed for a product. Managed by the Product Owner, it prioritizes items based on business value, customer needs, and market demands. It evolves continuously, with new items added and existing ones refined. The product backlog represents the long-term vision of the product and is not tied to a specific sprint. On the other hand, the sprint backlog is a subset of the product backlog. It consists of the user stories and tasks selected for a single sprint. Owned by the Scrum Team, it provides a detailed plan for delivering the sprint goal. Unlike the product backlog, the sprint backlog is fixed during the sprint, ensuring the team remains focused.
169
참고 답변
While both the product owner and the scrum master play important roles in a scrum team, they each have different jobs. The product owner decides what the team needs to build. The product owner sets the order of tasks in the product backlog and speaks for what the customer wants. They help the team focus on the features that give the most value. The scrum master, on the other hand, looks after how the team works each day. The scrum master guides everyone in using scrum practices, leads meetings, and clears problems that may slow the team down. They work to improve teamwork, keep people productive, and support continuous improvement. | Role | Focus | | Product Owner | Maximizing product value, managing the Product Backlog, prioritizing. | | Scrum Master | Facilitating Scrum process, coaching team, removing impediments. |
170
참고 답변
The three major ceremonies performed in scrum are Planning meeting, review meeting and retrospective meeting.
171
참고 답변
The candidate should provide an example of removing a bottleneck, explain the results, and how it helped the team or project progress.
172
참고 답변
Success is not simply teams doing stand-ups. It is measured by: - Faster decision cycles - Higher customer satisfaction - Increased adaptability - Reduced delivery risk - Transparent portfolio visibility
173
참고 답변
User stories can be written by anyone. Although it is the product owner's job to ensure that an agile user story backlog exists, this does not imply that the product owner is the one who produces them. During the early stages of product development, the team discusses needs and records them as user stories. As long as there is a product backlog, it will never be frozen. As a result, if someone thinks there's a missing requirement or anything that could benefit the client, they can add it to the queue as a user story. There is no rule or guideline indicating that the stories must be written solely by the product owner. Because there is a set format, anyone creating the story should know exactly what it means and how to write it.
174
참고 답변
A successful Scrum Master possesses a unique blend of skills and qualities that enable them to facilitate Agile practices within a team effectively. These include: (content not explicitly listed in the provided text beyond the introductory statement).
175
참고 답변
- Sprint 0 denotes the little amount of work set to form a basic structure of the product backlog. It also comprises insights about valuing the release of products. Sprint 0 is required for: - Generating the project skeleton, along with research spikes - Retaining minimal design - Evolving some stories entirely - Taking low velocity and being lightweight - The spike is a set of actions that involve Extreme Programming (XP) for research, design, investigation, creating POCs, etc. - The spike targets to lower risks of the technical approach, facilitating knowledge to better understand necessities and increase reliability
176
참고 답변
I create opportunities for knowledge sharing, such as 'lunch and learn' sessions, pair programming, and internal tech talks. I also encourage a culture where asking for help is seen as a strength, not a weakness, by modeling this behavior myself.
177
참고 답변
Talk about coaching the PO on respecting the sprint plan and educating stakeholders on the cost of switching. Mention how you work with the team and PO to build trust and improve planning.
178
참고 답변
A Sprint Spike is a time-boxed research or investigation activity used when the team needs to gather information before they can estimate or commit to a piece of work. Common uses include exploring a new technology, evaluating an approach, or investigating a bug. Spikes have a defined output, usually knowledge or a recommendation, rather than a shippable product feature.
179
참고 답변
- Identify blockers and provide support. - Encourage collaboration with other team members. - Reassess priorities and adjust workload if necessary. - Offer coaching to improve efficiency in future sprints.
180
참고 답변
Scrum teams are self-organizing and cross-functional, which means individuals within the team have the autonomy to decide how they'd like to execute the work and collaborate. So while scrum masters don't tell scrum team members what to do, they can still support their efforts and help organizations track their progress through daily scrum meetings, sprint planning sessions and sprint retrospectives. These agile meetings let scrum masters understand what each team member is working on, how they're doing, and how to be more efficient in the next sprint.
181
참고 답변
I would explore the reasons for their absence, addressing any scheduling or logistical issues, and reiterating the meeting's value in aligning the team's daily efforts.
182
참고 답변
The Scrum Master: - Is responsible for promoting and supporting Scrum as defined in the Scrum Guide. Scrum Masters do this by helping everyone understand Scrum theory, practices, rules, and values. - Acts as a servant-leader for the Scrum Team. - Helps those outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and which aren't. - It helps everyone change these interactions to maximize the value created by the Scrum Team. In simple words, SM is a person who believes in Scrum Values and processes and motivates everyone to follow it and creates an environment for everyone to follow it.
183
참고 답변
Scrum is a lightweight Agile framework used to deliver products incrementally through time-boxed iterations called Sprints. It focuses on collaboration, adaptability, and continuous improvement. Scrum is based on empirical process control, meaning decisions are made using transparency, inspection, and adaptation. It is widely used in software development and product-based companies.
184
참고 답변
I mediate conflicts by encouraging open communication and understanding both sides. I work with the team to find a mutually acceptable solution.
185
참고 답변
A key team member was going on leave during a critical Sprint. The risk was a potential bottleneck. I facilitated a session for the team to cross-train on that member's tasks. This mitigation ensured the team could continue working without major delays.
186
참고 답변
There are many widespread benefits to using Scrum in your organization. But there are also some less talked about limitations to Scrum. It's crucial that your Scrum Master knows how to recognize the limitations of the framework and how to overcome them as well. Listen for: Other project management methods your candidate may have worked with in the past. They should also display an ability to recognize when Scrum won't work for your team and how to continue the project with another management method.
187
참고 답변
There are three primary roles in Scrum: - Product Owner: The person responsible for defining and prioritizing features and requirements in the Product Backlog. - Scrum Master: The facilitator of the Scrum process, ensuring that the team follows Scrum practices, removes obstacles, and improves continuously. - Scrum Team: The self-organizing group of professionals who work together to deliver the product increment during each sprint.
188
참고 답변
When faced with scope changes or feature additions during a sprint, I follow a structured approach to minimize disruption. I evaluate the impact on the sprint goal and team capacity, considering whether the change is critical for achieving the overall project objectives. If the change aligns with the sprint goal and doesn't compromise delivery, we may adjust priorities collaboratively. However, if the change poses a significant risk to the sprint goal, I guide the team to capture the request in the product backlog for consideration in future sprints. It's crucial to balance flexibility with the commitment to delivering a cohesive increment at the end of each sprint.
189
참고 답변
A Sprint Review focuses on the product and value delivered, with an audience of the Scrum Team plus stakeholders, with the purpose of getting feedback on the product. A Sprint Retrospective focuses on the process and team performance, with an audience of only the Scrum Team, with the purpose of improving how the team works.
190
참고 답변
This is a common failure point. Action items from Retrospectives get noted and forgotten because nobody owns them. My approach is to ensure each action item has a clear owner and a deadline, and to follow up on them in subsequent retrospectives. Accountability does not require pressure. It requires clarity about who does what by when.
191
참고 답변
The three pillars of Scrum are Transparency, Inspection, and Adaptation. They form a framework for continuous improvement by ensuring clear visibility of work, regular assessment, and necessary adjustments to achieve better outcomes.
192
참고 답변
The "Three Amigos" practice in Scrum is teamwork and collaboration. It is where three important individuals—the Product Owner, Scrum Master, and Development Team—sit down together to discuss and clarify the specifics of a user story or feature prior to beginning any work on it.
193
참고 답변
A Scrum Master is the leader or facilitator of a team using Agile. They oversee all communication and collaboration between leadership and team members to ensure a successful outcome. The Scrum Master assists the team by addressing any obstacles and distractions. They act as servant leaders, helping the team become self-sufficient through self-organization and conflict-resolution techniques.
194
참고 답변
The scrum requirements are written as user stories and the scrum master isn't usually the one who writes them. But they might help the product owner do so. That way, the stories can be prioritized and ready for the sprint.
195
참고 답변
Act transparently, uphold Scrum values, and escalate respectfully if needed.
196
참고 답변
The three main scrum artifacts are the product backlog, sprint backlog, and increment. The product backlog has a list of things that need to be added or fixed. It shows what work is most important. The sprint backlog has a list of jobs for one sprint. The increment is what has been finished at the end of each sprint.
197
참고 답변
A Product Owner (one of the three key roles in Scrum) is responsible for driving a product's success and ensuring it offers business value. They establish what must be delivered based on an understanding of the target customer and the stakeholders' needs. Their responsibilities include managing Scrum backlogs, release management, and stakeholder management.
198
참고 답변
Managing expectations and communication with stakeholders unfamiliar with Scrum involves a dual approach of education and transparency. I proactively engage stakeholders in conversations to explain the Scrum framework, its benefits, and how it aligns with agile principles. I provide educational materials and facilitate workshops if needed. Additionally, I establish clear communication channels and regular updates to keep stakeholders informed about project progress. By fostering an understanding of Scrum and maintaining transparent communication, I build trust and alignment between the Scrum team and stakeholders, even those less familiar with the framework.
199
참고 답변
I'd look at team velocity and predictability first—can we reliably forecast what gets done? But beyond the numbers, I'd ask: Is the team solving problems independently, or do they need me for everything? Are retrospective action items actually being implemented? Is the Product Owner clear on priorities and comfortable with the team? When I'm doing my job well, the team becomes more self-organizing and needs less of my facilitation over time. I also look at team satisfaction and retention—are people happy? Do they feel empowered? In my last role, I didn't just measure success by velocity; I asked the team in retrospectives if they felt I was removing real obstacles and coaching them effectively. That feedback made me more effective than any metric could.
200
참고 답변
The five Scrum events are: Sprint, Sprint Planning, Daily Scrum/Standup, Sprint Review, Sprint Retrospective.


Copyright © 2024. Designer by SPOTO Official Website. All Rights Reserved.