1

參考答案

Situation: A team was skeptical about transitioning to Agile. Task: To coach them through this transition effectively. Action: I tailored the training to address their concerns, provided continuous support, and highlighted quick wins. Result: Gradually, the team embraced Agile practices, seeing improvements in their workflow and product quality.

2

參考答案

- Scrum Master - Product Owner - Scrum team.

3

參考答案

Stand-ups should be quick—I keep ours to 15 minutes hard stop. I frame it as: what did you accomplish yesterday, what are you working on today, and what's blocking you? But here's the key—if someone goes into detail about their technical approach, I gently redirect it. I might say, ‘That's a great discussion, but let's take it offline.' The daily stand-up is about information sharing and identifying blockers, not problem-solving. I also rotate who talks first to keep energy up, and I pay attention to who's quiet. If the same person never shares blockers, I'll follow up after the meeting because that might mean they're struggling but don't feel safe bringing it up. Early in my time with a team, I'll attend every stand-up. As the team gets better at it and needs less facilitation, I might step back.

4

參考答案

Scrum artifacts are the important information sources that provide transparency and focus for the Scrum Team and stakeholders. They represent work or value in development. There are three types of core artifacts in Scrum.

5

參考答案

A Scrum Master possesses several key skills and qualities: [not explicitly listed in the text, but implied from context]

6

參考答案

Quality is maintained by integrating automated testing, conducting regular code reviews, and fostering a team culture that prioritizes quality. Additionally, I encourage frequent releases and feedback loops to quickly identify and address issues.

7

參考答案

Self-organization means the team decides how to accomplish work without external micromanagement.

8

參考答案

A product backlog is an ordered list of everything that is known to be needed in the product. It is the single source of requirements for any changes to be made to the product. Its purpose is to capture and prioritize all work items, ensuring the team is always working on the most valuable features.

9

參考答案

Usually, a user story is marked done when the following criteria are met: - (Content not explicitly listed in the provided text beyond the introductory statement). When a user story has defects, you can mark it as partially done and move it to the next sprint.

10

參考答案

The 5 phases of risk management are as follows-

11

參考答案

Scope creep refers to the continuous and uncontrolled changes that occur after the project begins. Scope creep can be handled through the below:

12

參考答案

Leading indicators include: - Reduced cycle time - Stable velocity trends - Higher stakeholder engagement - Increased release frequency - Lower escaped defect rate Lagging indicators like revenue growth come later.

13

參考答案

A Scrum Master helps a Product Owner by: - Helping them to keep an updated list of tasks to be completed and release objectives - Ensuring Product Backlogs are prioritized to align with the Product Owner's most recent input - Making sure all stakeholder requirements are covered by backlog items - Encouraging a shared product vision amongst the Scrum team.

14

參考答案

- Delivering high-value products - Scrum is a framework within which people can innovate products with maximum utility and value for people, teams, and organizations. - Creating adaptive solutions for complex problems is Scrum.

15

參考答案

Neither the scrum master nor the product owner. It's the responsibility of the scrum team to own the deliverable.

16

參考答案

No, maximum velocity does not always mean maximum productivity. Focusing solely on maximising velocity may lead to shortcuts in quality, such as skipping testing or customer collaboration, and neglecting bug fixes.

17

參考答案

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.

18

參考答案

Burndown chart is a visual representation of a graph that assesses how much work a development team has done through a user story. Burnup chart is a graph that shows the amount of the work done against the total project work.

19

參考答案

The Product Owner, in collaboration with stakeholders and the Scrum Team, is primarily responsible for writing User Stories. User Stories are concise descriptions of functionality or features from an end user's perspective, written in simple language. They capture the requirements and needs of users and serve as the basis for prioritizing and planning the work to be done.

20

參考答案

Handling what stakeholders want can be hard, especially when they ask for detailed reports every day. The main thing is to use good and clear talk. A scrum master should make sure there is a set time for reports to be shared. This could be during daily standups or maybe as a short summary once a week. This helps everyone see what is happening and keeps things open. When you use things like team velocity and how far people are on user stories from the sprint backlog, you can answer questions stakeholders have. This keeps them in the loop without giving too much to the team. Letting people join in on sprint reviews gives them a way to see the current work. At the same time, this helps team morale stay steady. If you focus on business value in your reports, this will line up with what the company wants to see and reach its needs. This all shows how important effective communication is in scrum.

21

參考答案

Galvanizing a team that's new to Scrum (and Agile itself) can be tough, as they may be skeptical and/or reluctant to change their ways. You need to discuss how you'd highlight the benefits of Scrum and how you'd encourage team members to get involved — listening to their concerns and addressing them one by one.

22

參考答案

The primary objective of the retrospective is for the team to inspect itself and create a plan for improvements to be enacted during the next Sprint. It is focused on process and collaboration, not the product.

23

參考答案

I have a private, respectful conversation to understand their situation. I focus on the specific behaviors and their impact, and I work with them to create a plan for improvement. I ensure that these discussions are confidential and do not undermine their standing in the team.

24

參考答案

The primary artifacts in Agile Scrum are the product backlog, sprint backlog, and increments.

25

參考答案

Burndown shows remaining work the line goes down toward zero as Sprint progresses. Burnup shows completed work the line goes up toward the total scope line. Key difference: Burnup makes scope changes visible. If work is added mid-Sprint, the total line moves up everyone sees it immediately. Burndown hides scope changes the line just stops decreasing and no one understands why. For teams with frequent scope changes, burnup is more honest.

26

參考答案

Scrumban is an agile methodology which is the fusion of the best features of Scrum and Kanban.

27

參考答案

Velocity is a metric used to measure the completed amount of work by the team during the sprint session. It also indicates the number of user stories completed during each sprint. It also acts as a guideline for the team to understand the user stories that could be completed during the sprint.

28

參考答案

Difficult stakeholders are usually either uninformed about how Agile works or genuinely concerned about delivery outcomes. Both are addressable. My approach involves educating them on Agile principles, addressing their concerns directly, and building a collaborative relationship.

29

參考答案

To support a team member falling behind, you might have one-on-one conversations to understand the root cause, such as being overworked, lacking tool knowledge, or having personal issues. Then, you administer an appropriate fix, like spreading out the workload or bringing in a subject matter expert. This also involves creating an environment where team members feel empowered to speak up about issues.

30

參考答案

Addressing conflicting priorities involves a combination of communication, prioritization, and collaboration. I regularly check in with team members to understand their workload and identify potential conflicts. During sprint planning, we collaboratively prioritize tasks and ensure that the team's capacity aligns with the sprint goals. If conflicts persist due to involvement in multiple projects, I work with relevant stakeholders to adjust priorities or allocate resources appropriately. Additionally, I advocate for realistic task estimation and transparent communication about individual workloads. By actively managing conflicting priorities and fostering an environment of open communication, we enable the Scrum team to navigate multiple responsibilities effectively.

31

參考答案

Here are five common issues faced in a Scrum project: - (Content not explicitly listed in the provided text beyond the introductory statement).

32

參考答案

answer should show person took responsibility and owned fixing the problem

33

參考答案

In one project, we identified a risk that a key third-party API might change during our Sprint. I proactively contacted the vendor and arranged for early access to the new version. This allowed the team to test and adapt before the change went live, avoiding a major blocker.

34

參考答案

In Agile, tracer bullets are small, functional parts of a system built early to test the path forward. They help teams explore technical feasibility, validate architecture, and guide future development by showing how components work together without building the full solution upfront.

35

參考答案

To break the ice and also to make the candidate comfortable, the HR might ask this question. This can be answered amicably by providing a quick brief as to how you feel about the interview round. The answer can further be closed with a short introduction of the self before the recruiter starts asking the main interview questions for the scrum master role.

36

參考答案

Dealing with a product owner who often changes priorities during a sprint can be hard for the scrum master. The key in this situation is clear communication. The scrum master can bring everyone together for a talk with the product owner. This helps the development team and product owner agree on the top priorities. It also lets them know how these changes can slow down the development team. Using tools like a sprint backlog session also helps. This way, everyone can see how new tasks or changes can change the project timeline. The development team needs to feel safe to share any worry they have. A safe space lets them take ownership of their work, feel good about it, and handle new changes better.

37

參考答案

Evaluating team well-being during a sprint retrospective is indeed important. Start by assessing team culture, technical practices, and collaboration parameters. Use tools like rating scales or specialized software to assign ratings. A spider chart guided by the Scrum Master can visually highlight areas for improvement.

38

參考答案

Transforming retrospective feedback into tangible improvements involves a systematic approach. First, I ensure that the team reflects on both positive and negative aspects of the sprint, identifying specific actions that contributed to success or challenges. During the retrospective, we collaboratively prioritize improvement opportunities and define actionable steps to address them. I then work closely with the team to incorporate these action items into the next sprint, monitoring progress and adjusting the approach as needed. By closing the feedback loop and consistently implementing improvements, we create a culture of continuous learning and refinement.

39

參考答案

Sprint 0: A preparatory sprint before development starts, used for setting up environments, defining high-level architecture, and refining the backlog. Spike: A time-boxed research task within a sprint to explore solutions, reduce technical uncertainty, or evaluate feasibility.

40

參考答案

Timeboxing is a time management method that includes assigning a fixed, maximum duration for a specific task. The decider has to work only within that slot, then stop when time's up. They may have to force focus, prevent procrastination, and combat perfectionism by prioritizing progress over endless polishing.

41

參考答案

Handling resistance to Scrum involves various strategies. Some Scrum masters refer back to the Scrum values and encourage teams to think differently. Others instill a sense of ownership of the product in team members to invest them in the process. Bringing in a certified trainer for formal training can also be effective.

42

參考答案

Test-Driven Development is integrated by writing tests before the actual code. I encourage developers to start with small, fail-fast tests, and then write the minimum code needed to pass these tests, iteratively improving both tests and code.

43

參考答案

Celebrate success, then explore opportunities for sustainability and learning.

44

參考答案

Effective communication is very important for distributed teams, especially when people are in different time zones in the U.S. A clear plan helps every team member stay on the same page and get the information they need. This helps keep misunderstandings low. Video calls and chat tools make it easy for people to talk in real time. Keeping records of talks and decisions helps things stay clear for everyone. It's a good idea for teams to have working hours that can overlap. This makes it easy for team members to talk and work together. Regular standups also help, and everyone needs to join in. This lets the team feel more responsible for their work. A scrum master should build a safe space where people feel they can talk about their worries. When team members do this, the scrum master can solve problems with communication and help people of the scrum team work better together.

45

參考答案

I provide feedback regularly and in a timely manner, focusing on specific behaviors and their impact. I use the 'SBI' (Situation-Behavior-Impact) model. For coaching, I ask open-ended questions to help them find their own solutions and offer resources for skill development.

46

參考答案

Expect scrum master candidates to discuss facilitating backlog refinement and sprint planning meetings to align stakeholder expectations with the team's sprint goals. They might explain using retrospective meetings to address concerns and improve stakeholder relationships. Successful candidates will demonstrate how they ensure stakeholder satisfaction without compromising the teamâs performance or delivering new features.

47

參考答案

Scrum helps to continuously improve the process by repeatedly looking into the actual performance of the software. It has more transparency and visibility. It also reduces the cost of failure and boosts the ROI for the project.

48

參考答案

Through leadership coaching, storytelling, system visualizations, and feedback loops.

49

參考答案

Velocity is the average size of DONE requirements (Stories or any form of requirement) successfully delivered by the team every sprint in the past. Generally, it is calculated by averaging all the story points from the previous Sprints. It works as a guideline for the team to understand the number of stories they can do in a Sprint on an average.

50

參考答案

Although a Scrum Master is supposed to help the team get the best results, workshop facilitation can be tricky at times. A workshop facilitator must be impartial to the topics being addressed and should refrain from adding facts or opinions to the discussion. If the Scrum Master has the necessary expertise, he or she can facilitate most general product development workshops. However, if the workshop is about changing the Scrum process, the Scrum Master should not facilitate that session.

51

參考答案

Regular communication with stakeholders and the Product Owner is key. I ensure that the release plan reflects business priorities and adapt it as necessary based on changing business needs and customer feedback.

52

參考答案

I provide training on how to interpret metrics and emphasize their use as a tool for improvement, not as a measure for individual performance. Regular discussions on metrics in retrospectives help in correct interpretation and application.

53

參考答案

A servant-leader is an individual who excels in encouraging, facilitating, and uplifting individuals to collaborate as a team and achieve their full potential. A Scrum Master is a leader who serves the team and users by focusing on their needs to achieve results aligned with the organization's values, principles, and goals. The duties of a Scrum Master as a servant-leader involve managing the Agile projects along with other key responsibilities.

54

參考答案

Being a Scrum Master comes with a lot of responsibilities — one being the infamous sprint planning. These meetings are super important to Agile teams and they help make sure a Scrum team runs smoothly. It's possible that a team member may become bored of the meetings and eventually skeptical of their effectiveness. It's a Scrum Master's job to get to the bottom of this. Listen for: What the candidate does to come up with a solution. They should first try to understand why the team member is feeling this way. They should also communicate to them that each Scrum team member is integral to the project, as are Scrum planning meetings.

55

參考答案

The Scrum Master plays a crucial role in facilitating the Scrum framework, acting as a servant-leader to the team. Unlike traditional project managers, the Scrum Master doesn't have direct authority over the team but focuses on removing impediments, fostering collaboration, and ensuring adherence to Scrum principles. In essence, the Scrum Master is a facilitator who empowers the team to self-organize and achieve their objectives.

56

參考答案

Balancing the need for regular feedback with the Scrum principle of giving autonomy involves a delicate approach that values collaboration and self-organization. I create a feedback culture that emphasizes constructive communication and continuous improvement. During sprint reviews and retrospectives, I provide feedback on the team's performance and encourage team members to share their insights. However, I respect the autonomy of the development team by avoiding micromanagement and allowing them to make decisions collaboratively. By fostering a culture where feedback is a two-way street and empowering the team to self-organize, we strike a balance that enhances both autonomy and continuous improvement.

57

參考答案

Stand-up sessions are daily dialogs that take place and are usually 15 minutes long. Daily Stand-up sessions support us understand: - What tasks went well - What tasks were accomplished - What tasks are incomplete, and - The obstacles the team is facing The meeting helps in accepting the overall scope and status of the project. Further thoughts and steps can take place after the stand-up sessions.

58

參考答案

Sprint 0 is a preparation sprint before development begins, focusing on setting up the environment and refining the backlog. A Spike is a time-boxed research task used to explore unknowns or gather information needed to make decisions in future sprints.

59

參考答案

A release burndown chart tracks remaining work across multiple Sprints toward a larger release goal.

60

參考答案

To identify areas for improvement as a Scrum Master, it's essential to continuously seek feedback, reflect on practices, and assess team outcomes. Here's how you can approach this: - (Content not explicitly listed in the provided text beyond the introductory statement).

61

參考答案

Coach leadership on focus, support delegation, and facilitate clarity of responsibility.

62

參考答案

In a project with a tight deadline, we identified a risk that the integration with a legacy system could cause delays. We prioritized building a mock interface early to test the integration. This risk mitigation allowed us to identify issues early and deliver the project on time.

63

參考答案

When the backlog became too large, I facilitated a session with the Product Owner and stakeholders to cull old, irrelevant items and group related items into themes. We also created an 'icebox' for low-priority items. This made the backlog more manageable and focused.

64

參考答案

Scrum is built on five values: Commitment, Courage, Focus, Openness, and Respect. These values guide team behaviour and support a healthy Agile mindset.

65

參考答案

This is a simple question: Regularly ask your team and stakeholders how you can improve as a Scrum Master. Why not run a Sprint Retrospective on yourself? A dedicated Sprint Retrospective is much more effective than spending five minutes, asking for hints at how you might improve, at the end of each regular team Sprint Retrospective. Good candidates also note that they proactively provide user manuals on how to work with themselves to other team members and the organization.

66

參考答案

Addressing frustrations or dissatisfaction with the agile or Scrum framework involves a combination of empathy, education, and continuous improvement. I initiate open conversations with team members to understand the specific aspects causing frustration. Through these discussions, I provide explanations on the underlying principles of agile and Scrum, emphasizing their benefits. Additionally, I actively incorporate team feedback during retrospective meetings to identify areas for improvement in our implementation of agile practices. By acknowledging concerns, offering explanations, and actively involving the team in refining our agile processes, we create a collaborative environment that fosters a positive relationship with the Scrum framework.

67

參考答案

I start with a comprehensive overview of Agile principles, focusing on the Product Owner's role in backlog management, prioritization, and stakeholder engagement. I also provide ongoing support through regular one-on-one sessions and practical guidance during Agile ceremonies.

68

參考答案

Promoting self-organization in the Scrum team involves establishing a setting where team members can assume responsibility and collaborate on decisions. Give direction on Scrum principles, encourage transparent communication, and highlight the significance of shared accountability. During sprint planning, help the team have discussions that enable them to self-organize and agree on possible goals. To ensure that the project stays on track with its goals, it is important to have a distinct vision and communicate the main objectives to the team. By giving the team the power to make decisions together and offering a structure for unity, we find a middle ground between independence and project unity.

69

參考答案

I deal with difficult stakeholders by actively listening to their concerns, managing expectations, and fostering open communication. I work to build trust by regularly updating them, ensuring their needs are met, and aligning their expectations with the team's progress.

70

參考答案

I address conflicts privately and constructively, focusing on resolving the issue without assigning blame. I ensure that conflicts do not affect the entire team's morale by containing the discussion and preventing gossip. I also support affected team members.

71

參考答案

Should get a concise 2-3 minute career summary including years of experience as a TPM and years of experience with Scrum - Looking for clear communication - Great candidates may ask questions to get feedback like "would you like to know more?" "is that summary enough?"

72

參考答案

The fact is that there is no universal way to answer this question. As a rule of thumb, most Scrum masters can handle 2-3 teams. But every company has unique project management requirements, so the answer of the candidates may differ. Here, you can frame the answer per your experience and skills. You can also mention why you enjoy this role and openly discuss the pain points. If you are a fresher, you can be honest about your lack of experience and instead share your perspective on how you will manage teams.

73

參考答案

In an increasingly remote-first world, it's likely that you're looking for a Scrum Master with remote work experience or a preference for remote work. Your candidate will need to understand the limitations of remote work and how to excel despite them. Listen for: Examples of strong communication skills, adaptability, organizational skills and solution-based action. Also make sure they understand the importance of being accessible to their remote team members.

74

參考答案

A Scrum Team comprises the Product Owner, who defines and prioritizes the work; the Scrum Master, who facilitates the process and removes impediments; and the Developers, who are responsible for delivering the product incrementally.

75

參考答案

Backlog Refinement should be a regular, ongoing activity, ideally happening once per Sprint. It's important to involve the entire Scrum Team to ensure shared understanding and alignment on the work ahead.

76

參考答案

Encouraging a culture of continuous improvement involves creating an environment that supports introspection, collaboration, and ongoing learning. Initiate regular retrospective meetings where the team can assess their processes, communication skills, and productivity. These sessions foster open discussions about achievements, areas for improvement, and actionable steps. Additionally, it promotes experimentation with different approaches, technologies, or methods to nurture a culture of learning and innovation. It's crucial to consistently track and review the team's efforts to ensure sustained performance enhancement.

77

參考答案

In a Daily Stand-up is a brief meeting to keep everyone aligned and on track. Each team member answers three simple questions to update the group on their progress: a) What did you complete since the last meeting? b) What do you plan to complete by the next meeting? c) What obstacles are getting in your way?

78

參考答案

Indeed, it becomes really difficult for the team members to work under pressure, especially when new tasks are delegated to them without prior indication. But if they are capable enough and have previous experience of surviving in complex, overwhelming situations without feeling burnt out, they will be able to get through it, provided it is a rare situation and does not occur every other day. If this is an urgent task, I will make sure to sit with the team over a discussion as to how to proceed with this additional set of tasks from another department. I will try to communicate our work process, tight timelines and the targets we have to achieve in every sprint, to those who delegated the work, so that there is utmost transparency and there is enough room for understanding each other's priorities and scope of work.

79

參考答案

This question can help you gauge whether their career aspirations align with your needs as an employer. It will also help you gain a deeper understanding of their motivators which is an integral part of keeping employees happy, productive and loyal. Listen for: What makes this person tick and what it will take to help you keep them around for the long haul. That could be money, growth opportunities or a passion for the work. Listen without judgment and try to meet them where they're at.

80

參考答案

When unforeseen challenges arise that threaten the sprint goal, I approach the situation with a focus on collaboration and problem-solving. First, I gather input from team members to understand the nature and severity of the challenges. I then facilitate a discussion to explore potential solutions, considering both short-term mitigation and long-term resolution strategies. If the challenges require adjustments to the sprint goal, I work with the team and stakeholders to make informed decisions and communicate changes transparently. By fostering a culture of adaptability and providing support during challenging times, we ensure the team can navigate unforeseen obstacles while maintaining a commitment to delivering value.

81

參考答案

Prior to Sprint Planning, I review the Product Backlog with the Product Owner to ensure it's well-prioritized. I also confirm that key stakeholders are available for the meeting and that any necessary materials or data are prepared in advance.

82

參考答案

Maintaining compliance with regulations and industry standards involves a proactive and collaborative approach. I work closely with relevant stakeholders, including legal and compliance teams, to stay informed about regulatory requirements. During sprint planning, I ensure that compliance considerations are incorporated into user stories and acceptance criteria. Additionally, I organize training sessions for the team to raise awareness of industry standards and compliance requirements. By integrating compliance into the development process, we ensure that the Scrum team's work aligns with regulatory expectations, reducing the risk of non-compliance.

83

參考答案

A waterfall is a conservative project management approach where teams do not need to communicate and emphasizes a linear progression. In this methodology, the next project phase follows after the completion of the previous one, hence, the name 'Waterfall'. On the flip side, the Scrum framework follows an iterative approach where the development team is in constant contact with each other. It has three crucial principles- Transparency, Inspection, and Adaption.

84

參考答案

HEre are the following Difference Between Agile and Scrum: Parameters | Agile | Scrum | |---|---|---| Methodology | Agile is a set of principles that's iterative and incremental. | Scrum is an implementation of the agile methodology. | Projects | Suited for projects involving a small team of experts. | They are used in projects where the requirements are constantly changing. | Leadership | The project head takes care of all tasks is vital to the project. | There's no leader, the scrum master, and the team addresses the issues. It involves cross-functional, self-organizing teams. | Flexibility | In agile, changes cannot be handled frequently. | It enables teams to react to changes quickly. | Delivery | The methodology requires frequent delivery to the end user. | With sprints, builds are delivered to clients for feedback. | Collaboration | Face-to-face interaction takes place between cross-functional teams. | Daily stand-up meetings help with collaboration. |

85

參考答案

Scrum Master, Product Owner, Developers.

86

參考答案

As a scrum master or an instructor of a group of people, it is imperative to be open to listening to a variety of perspectives. Listening is highly underestimated by people, but it plays a crucial role in establishing and training the scrum team. Additionally, a scrum master can consider the following steps to properly coach and empower the scrum team: - Avoid listening to their concerns just for the sake of it. Listen to understand their deep-seated issues and why they do things the way they do. Question them on the various aspects of their work, and also how they function in the team, not to raise a problem, but to help them pivot to the right roadmap to resolve the uncertainties. - Make sure to foster a collaborative and safe environment for the team members so they can freely discuss their issues without the fear of being judged. Do not focus solely on your rapport with the team members, but also on how they are with one another. See if everyone is eager to help the other person understand things and participate in interactive discussions. - Develop a sense of learning and growing among the team members, because this forms an integral aspect of the Scrum framework. Being committed, focused and transparent, other than being respectful and courageous, are a few things that help the scrum team members to be excellent problem solvers and decision makers. - Conduct interactive sessions where you ask multiple questions to your team members, which are both important and relevant to everyone. Try to keep the questions open-ended so you can listen to diverse perspectives from each one and gain a deeper insight into their experiences, knowledge, and understanding. - Uphold the principles of Scrum in every discussion conducted with the team members. Trust the process where you train the Scrum team to emphasise the Scrum framework and incorporate it in their day-to-day operations. Support open communication and a positive attitude towards the feedback received, so they can only look forward to improvements and growth. - Always keep in the back of your head to always support your team, track down hindrances in the process, external influences and triggers, so you are aware of the outside factors affecting the performance of your team. For this, make sure daily meetings are carried out where problem areas are openly discussed and a practical solution is developed. Note: Advise the team to abide by the Scrum principles (theory). Understand the problems faced by your team members so they can focus on their goals without being affected by the disruptions along the process. Give time, stay patient and be open to implementing new strategies to drive maximum product value.

87

參考答案

Incremental delivery means delivering small, usable portions of a product regularly instead of waiting for a full release. Each Sprint produces a potentially releasable product increment. This reduces risk and improves stakeholder feedback loops.

88

參考答案

A Scrum Master focuses on a team. An Agile Coach operates at: - Multi-team level - Leadership level - Organizational system level Scrum Master = team-level execution. Agile Coach = enterprise capability building.

89

參考答案

A good user story comprises a description as well as set acceptance criteria. It should be a piece that can be completed in a sprint and has the fewest dependencies possible. Within the sprint's constraints, the team should be able to build and test while also delivering estimations. In a nutshell, the INVEST principle is followed by good user stories. - I stands for Independent - The user story should be such that the team members are less reliant on others - N stands for Negotiable - It should describe the functionality and is subject to agreement between the Team and the Product Owner. - V stands for Valuable - It should add value to the customer's experience. - E stands for Estimable - It should be such that the time requirement can be approximately estimated. - S stands for Small - It should be small enough so that the team can complete it in a sprint. - T stands for Testable - It should have good acceptance criteria. During backlog refinement or sprint preparation, the scrum master can assist the team in producing good user stories so that they can be picked up for the commitment.

90

參考答案

Success is measured by the quality of feedback received from stakeholders, the alignment of the product increment with their expectations, and the actionable insights generated that lead to improvements in the Product Backlog. Stakeholder satisfaction is a key indicator.

91

參考答案

A burndown chart visually represents the amount of work remaining in a sprint or project over time. It typically displays: - (Content not explicitly listed in the provided text beyond the introductory statement).

92

參考答案

Addressing burnout or high levels of stress within the team involves a combination of empathy, proactive communication, and supportive measures. I regularly check in with team members to gauge their workload and stress levels, creating a space for open conversations. If burnout is identified, I work collaboratively with the team to adjust workloads, redistribute tasks, or introduce additional resources. I also emphasize the importance of maintaining a healthy work-life balance and encourage team members to take breaks when needed. By proactively addressing stressors and creating an environment that prioritizes well-being, we foster a positive and sustainable work culture within the Scrum team.

93

參考答案

Retrospectives should be conducted at the end of every Sprint. The frequency is tied to the Sprint cycle, typically every one to four weeks, allowing the team to continuously inspect and adapt their process.

94

參考答案

Here's another practical interview question. There's always going to be some conflict when a group of people is working together for a common goal, and sometimes that conflict is a positive thing. However, too much will derail the project. Have the person explain when there was team conflict and what they did to resolve that conflict in such a fashion that egos weren't bruised, and the team remained bonded afterward.

95

參考答案

Addressing time management challenges involves a combination of coaching, support, and collaborative problem-solving. I engage in one-on-one conversations with team members to understand the root causes of their time management struggles. Together, we identify areas for improvement and develop strategies to enhance their organizational skills. If needed, I provide resources or training on effective time management techniques. Additionally, I emphasize the importance of realistic task estimation during sprint planning and encourage regular check-ins to monitor progress. By taking a proactive and supportive approach, we help team members develop effective time management habits and improve their ability to meet deadlines consistently.

96

參考答案

After the risk analysis, the Confidence Vote is conducted at the Program Increment Planning session. It is when all members of the team meet together and raise their voices and vote with their fingers on their confidence level in the completion of the PI Targets. Only when all of the features and user stories have been appropriately estimated and prioritized can the confidence vote be used. All of the work that is being done must be transparent to all parties involved, with all dependencies and hazards clearly defined. With a vote of confidence, you can create an environment where individuals feel free to share and express their opinions. It boosts team members' morale since they should feel that their opinions are respected.

97

參考答案

Scrum of Scrums is a coordination technique used when multiple Scrum teams are working on the same product. Representatives from each team meet regularly to discuss progress, dependencies, and impediments that impact other teams. Its purpose is to improve communication, manage cross-team dependencies, and ensure alignment toward a common product goal without disrupting individual team Scrum ceremonies.

98

參考答案

I've been a software developer for five years, and I realized I got the most energy from helping my teammates solve problems and removing roadblocks. In my last role, I started informally taking on facilitation duties during sprint planning, and I noticed how much smoother our process became when someone was truly focused on team dynamics rather than just shipping code. I completed my CSM certification because I wanted to formalize these skills and bring structure to what I was already doing intuitively. I'm drawn to the Scrum Master role because it's about making others successful, not about being in charge.

99

參考答案

Mentoring junior scrum masters means helping them understand the scrum framework and the values behind it. I share things I have learned from my own work to guide them through the scrum process. I make sure to talk a lot about servant leadership and the need for good, clear, and effective communication. We have practice sessions where they act out real-life cases. This gives them chances to practice leading scrum ceremonies like daily standups and sprint retrospectives. I also push them to take ownership of their work. I tell them to speak up when there are team conflicts. This helps them learn and feel strong in their jobs. Watching how they grow makes a friendly place where team morale goes up. This helps them feel ready to face problems and lead their teams well.

100

參考答案

Definition of done is the team's contract with each other about quality. I'd facilitate a workshop where we ask, ‘What has to be true before we call something done?' I'd push the team to think beyond just ‘coded'—what about code review? Tests? Documentation? Deployment? I'd also separate what's always done from what might depend on the story. For us, DoD always included code review, unit tests, and passing the staging deployment. Some stories also needed documentation or database migration notes. I'd make sure it's visible on the wall and referenced during sprint review—when someone asks if a story is done, we check it against DoD. It's not bureaucracy; it's clarity.

101

參考答案

Scrum maturity is not measured by ceremony compliance it's measured by behavioral and outcome indicators. I evaluate maturity across five dimensions: - Backlog quality and refinement discipline - Sprint predictability trends - Psychological safety in discussions - Cross-functional collaboration depth - Continuous improvement follow-through True maturity shows in ownership, not process adherence.

102

參考答案

I monitor the team's workload and velocity, guard against overcommitment, and advocate for realistic Sprint goals. Ensuring the team takes regular breaks and respects work-life balance is also crucial.

103

參考答案

After analyzing risks, the Confidence Vote occurs during the Program Increment (PI) Planning session in the Scaled Agile Framework (SAFe). Team members vote on their confidence in meeting the PI targets. This vote is based on well-estimated and prioritized features and user stories, with transparent work, dependencies, and risks. The Confidence Vote allows team members to freely share their opinions, which enhances morale and ensures their views are valued.

104

參考答案

The candidate should describe onboarding practices like assigning a buddy, providing documentation, conducting orientation sessions, and ensuring the new member understands team processes and Scrum roles.

105

參考答案

Sprint Review is conducted at the end of a Sprint to inspect the product increment and gather stakeholder feedback. It ensures alignment between the product vision and delivered value.

106

參考答案

Situation: A release faced significant scope changes mid-cycle. Task: My responsibility was to manage these changes without derailing the release schedule. Action: I facilitated additional planning sessions to reassess priorities and reallocate resources. Result: Despite the challenges, we managed to release on time with critical features, satisfying key stakeholders.

107

參考答案

I've worked with SAFe on a program with three teams building an integrated product. The challenge was that each team had different velocities and sprint cycles, which made it hard to know when dependencies would be ready. We aligned on the same sprint schedule and implemented a ‘Program Increment' planning session where all teams came together to identify cross-team dependencies upfront. We also created a shared definition of done that ensured quality standards across teams. One key practice was having Scrum Masters meet between sprints to talk about blockers and coordinate the next sprint. It wasn't perfect—scaling is messy—but it reduced the friction and helped teams deliver features instead of getting stuck waiting on each other.

108

參考答案

Technical debt must be made visible. I encourage: - Dedicated backlog items for technical debt - Capacity allocation in each Sprint - Measuring defect trends - Linking debt impact to velocity stability Ignoring technical debt reduces long-term predictability.

109

參考答案

Handling external pressures and urgent requests involves a combination of communication, prioritization, and collaboration. I work closely with the Product Owner to assess the impact of external requests on the sprint goal and prioritize accordingly. If urgent requests arise during the sprint, I facilitate discussions within the team to determine the best course of action, considering potential adjustments to the sprint backlog or reprioritization of tasks. Additionally, I communicate transparently with stakeholders about the impact on the sprint goal and collaborate on alternative solutions. By managing external pressures effectively and involving the team in decision-making, we ensure that the Scrum team can navigate challenges while maintaining a focus on delivering value.

110

參考答案

Situation: Changes to the Product Backlog were frequent in a project I managed. Task: It was crucial to incorporate these changes without disrupting ongoing work. Action: I coordinated with the Product Owner for timely backlog refinement and ensured the team was adaptable to changes, balancing new requirements with ongoing tasks. Result: This approach led to a more dynamic and responsive project execution while maintaining focus on the Sprint Goals.

111

參考答案

I keep meetings time-boxed to 15 minutes, enforce a strict focus on the three key questions, and discourage detailed discussions. If a topic requires deeper conversation, I note it and suggest a follow-up meeting with the relevant parties after the stand-up.

112

參考答案

Servant leadership is a leadership style where the leader serves the team by enabling success rather than controlling work. A Scrum Master practices servant leadership by: - Removing blockers - Coaching team members - Protecting focus - Encouraging ownership This is a frequently asked Agile Scrum interview question.

113

參考答案

During refinement, I encourage discussions on technical challenges and dependencies. Bringing in technical experts or conducting exploratory spikes can be helpful for complex items.

114

參考答案

Here are the following Difference Between Sprint Retrospective and Sprint Review: | Aspect | Sprint Retrospective | Sprint Review | |---|---|---| | Purpose | Reflect on the past Sprint and identify improvements | Demonstrate the work completed during the Sprint | | Attendees | Scrum Team (Development Team, Scrum Master, Product Owner) | Scrum Team (Development Team, Scrum Master, Product Owner), Stakeholders, Customers | | Timing | Held at the end of each Sprint | Held at the end of each Sprint | | Duration | Typically 1-2 hours | Typically 1-2 hours | | Focus | Process improvement and team collaboration | Product demonstration and feedback from stakeholders | | Agenda | Discuss what went well, what could be improved, and action items for improvement | Demonstrate completed work, review Sprint goals and backlog, gather feedback | | Outputs | Action items for process improvement | Feedback on the product increment, potential adjustments to the Product Backlog | | Facilitator | Scrum Master | Scrum Master or Product Owner (or both) |

115

參考答案

When faced with disagreements on the best approach to solving a problem, I leverage the principles of Scrum to guide the resolution process. I facilitate open and constructive discussions during ceremonies like Sprint Planning or Daily Standups to ensure all perspectives are heard. If consensus is challenging to achieve, I may suggest a time-boxed workshop or brainstorming session to explore alternative solutions collaboratively. Ultimately, the goal is to reach a decision that aligns with the team's objectives and values. By promoting a culture of respect and open communication, I create an environment where diverse viewpoints contribute to innovative problem-solving.

116

參考答案

Promoting a culture of trust and psychological safety is foundational for a high-performing Scrum team. I lead by example, demonstrating openness, vulnerability, and a willingness to admit mistakes. During team interactions, I encourage active listening and create space for diverse perspectives. I address conflicts promptly and constructively, ensuring that team members feel heard and valued. Additionally, I facilitate team-building activities that strengthen interpersonal relationships and create a supportive environment. By fostering a culture where team members feel safe to express themselves, take risks, and collaborate openly, we build a foundation for trust that enhances overall team performance.

117

參考答案

The Product Backlog is important because it is the single source of work for the team, ensuring transparency and alignment. Items are prioritized by the Product Owner based on business value, customer feedback, and dependencies. The team provides estimates to inform this prioritization.

118

參考答案

No. The entire team collaborates with stakeholders and subject matter experts during the product review. The Scrum Master is responsible for educating stakeholders in order to make sure they're communicating effectively with the rest of the team and that everyone is on the same page when it comes to getting things done by certain deadlines.

119

參考答案

I ensure adherence to Scrum principles by regularly conducting training sessions and workshops. Additionally, I monitor the team's progress through Scrum artifacts and provide continuous feedback to keep everyone aligned.

120

參考答案

Scrum Artifacts contain critical information that the Scrum Team and stakeholders need to know in order to understand the product being developed, the activities that have been completed, and the activities that are planned for the project. The Scrum Process Framework defines the following artifacts: - Product Backlog: The Product Backlog is a list of all the features, functionalities, requirements, additions, and fixes that will be included in future releases of the product. Description, order, estimate, and value are all properties of Product Backlog items. The Product Owner is in charge of the Product Backlog's content, as well as its availability and ordering. - Sprint Backlog: The Sprint Backlog consists of the Product Backlog items chosen for the Sprint, as well as a strategy for delivering the product increment and achieving the Sprint Goal. It is the Team's projection of what feature will be available in the next Increment, as well as the work required to turn that functionality into a working product Increment. - Increment: The Increment is the total of all Product Backlog items accomplished throughout a Sprint plus all preceding Sprint increments. The new Increment must be a working product at the end of a Sprint, which means it must be in usable form. Regardless of whether the Product Owner decides to release it, it must be in functioning condition. - Sprint Burn-Down Chart: The total work remaining in the Sprint Backlog can be totalled at any point throughout the Sprint. The team keeps track of the overall work remaining for each Daily Scrum to estimate the chances of meeting the Sprint Goal. The Team can control its progress by keeping track of the remaining work during the Sprint. The Sprint Burn-Down Chart is a method of tracking how much work the Scrum Team has done in a given sprint. This has been shown to be an effective method for tracking Sprint progress toward the Sprint Goal.

121

參考答案

Following are the different roles in Scrum:- - Product Owner: The product owner is in charge of enhancing ROI by determining product features, prioritizing these items into a list, determining what should be prioritized for the next sprint, and much more. These are re-prioritized and modified on a regular basis. - Scrum Master: This person assists the team in learning how to use Scrum to maximize business value. The scrum master removes roadblocks, keeps the team focused, and helps the team embrace agile methods. - Scrum Team: A Scrum Team is a group of people who work together to guarantee that the stakeholders' needs are met.

122

參考答案

Stakeholders are involved by the Product Owner, who regularly shares the backlog's state and upcoming priorities. I facilitate sessions where stakeholders can provide input on item value and acceptance criteria. This ensures the backlog reflects stakeholder needs.

123

參考答案

A user story is a casual, generic explanation of a software feature written from the end user's perspective. Its goal is to communicate how a software feature will benefit the customer. Putting people first is a critical component of agile software development, and a user story does just that by putting end-users at the heart of the discussion. The development team and their efforts are described in these anecdotes using non-technical language. The team knows why they're developing, what they're building, and what value it adds after reading a user story. Following are the advantages of using User Story:- - The main advantage of User Story is the user-centric definition. This is because, in the end, the user will be the one who uses the product in the relevant user scenarios. It establishes a link between end-users and team members. - The User Story's syntax ensures that the objective, benefit, or value that the user wishes to attain is captured. - The Scrum Team will benefit from the acceptance criteria because they are included in the user story. It is possible to make changes to a user story throughout the project's execution. If the user story's scope grows too large, it must be divided into smaller user stories. The acceptance criterion's conditions can also be changed.

124

參考答案

Adaptations often involve modifying sprint lengths, refining backlog prioritization, or improving communication. For example, if frequent scope changes disrupt sprints, a Scrum Master may implement shorter iterations or stronger backlog grooming.

125

參考答案

In contrast to a traditional waterfall work environment that emphasizes the final outcome, Agile settings break down projects into separate tasks with practical deadlines. This enhances efficiency and standards. Below are a few methods to cultivate an Agile mindset: [not explicitly listed in the text, but implied from context]

126

參考答案

Scrum and Waterfall are quite different. There are two different methodologies that can be used to deliver any particular project. The following are the major differences between them: - Waterfall is a sequential method where one phase is followed by the other in a sequence. Scrum is more value-driven and is an agile process, which is iterative. - In Waterfall approach, the end-user will see the final product near the end. In Scrum, the end-user is involved at each stage of the process right from the design phase. - Change management is easy in the scrum, where a change can be incorporated even later in the stage without much cost. In Waterfall, making a change later in the process is very costly and is generally not feasible. - Waterfall is broken into phases, usually referred to as the requirements phase, development phase, testing phase, deployment phase, etc. Scrum is broken down into sprints (usually 2 weeks) in which the planning, development, testing, and deployment happen for a set of features.

127

參考答案

Addressing external disruptions involves a combination of communication, adaptation, and strategic alignment. I maintain open communication channels with stakeholders to stay informed about changes in organizational priorities or market conditions. If these disruptions impact the team's goals, I work collaboratively with the Product Owner to reassess priorities and adjust the product backlog accordingly. Additionally, I facilitate discussions within the team to ensure everyone is aware of the changes and aligned on the adjusted objectives. By fostering a culture of adaptability and providing clear communication, we can navigate external disruptions while maintaining a focused and resilient Scrum team.

128

參考答案

Addressing dissatisfaction or frustration with the Scrum process involves active listening, empathy, and proactive problem-solving. I initiate one-on-one conversations with team members to understand their specific concerns and perspectives. By actively listening and acknowledging their feelings, I demonstrate a commitment to understanding their experiences. If the dissatisfaction stems from a misunderstanding or misapplication of Scrum principles, I provide clarification and offer guidance on best practices. Additionally, I leverage retrospective meetings to openly discuss challenges and collaboratively find solutions. By fostering a culture where concerns are addressed transparently and constructively, we build trust and enhance the team's commitment to the Scrum process.

129

參考答案

Tightly coupled systems introduce significant risks in Scrum-based delivery as they reduce team autonomy and slow down the ability to deliver incremental value. In the high independent condition, a change in one area can impact multiple teams or systems that can increase coordination overhead and the likelihood of defects. This weakens Scrum principles such as fast feedback, frequent releases, and self-organizing teams. As a result, delivery becomes less predictable, testing becomes harder, and the team's ability to respond to change is compromised.

130

參考答案

Balancing short-term priorities with the long-term product vision requires ongoing communication and strategic alignment. I work closely with the Product Owner to ensure that short-term goals contribute directly to the overall product vision. During sprint planning, I emphasize the connection between user stories and the broader product roadmap, providing context for the team's work. Additionally, I facilitate discussions about the strategic impact of our short-term decisions, ensuring that each sprint increment aligns with the evolving product vision. By maintaining a clear link between immediate priorities and the long-term strategy, we foster a sense of purpose and direction within the Scrum team.

131

參考答案

When Scrum teams repeat the same pattern of a retrospective sprint after sprint, the teams become tired of it. The Scrum Master must be willing to experiment with different patterns and, on occasion, change the location. Anything that occurs on a regular basis in the same format tends to generate a dull meeting setting. Some teams may choose to go out to lunch and have a conversation there; this not only facilitates collaboration but also creates a safe setting in which to speak. The Scrum Master must ensure that the substance of a retrospective is not lost while creating a favorable environment to prevent boredom. Even if you're employing various patterns, the intent should remain the same.

132

參考答案

The ideal size of a scrum team is between 3 and 9 people

133

參考答案

I regularly solicit feedback from the team about the format and effectiveness of the stand-up. I adapt the meeting to the team's evolving needs, such as adjusting the questions or time, while ensuring it continues to serve its core purpose of synchronization and impediment removal.

134

參考答案

Continuing on with the theme of feedback, ask this interview question to get insight into what your candidate has learned from feedback in the past and how they've improved with it. You can make this question more interesting by opening it up to their personal life as well — there's no doubt the feedback we get in our personal lives can positively impact our professional lives too! A Homerun team fav. ? Listen for: A real-life scenario and how they took on this feedback to improve themselves. And remember, an example from outside of the workplace could be incredibly enlightening!

135

參考答案

During a retrospective meeting, a Scrum Master facilitates discussions to help the team reflect on the recent Sprint, identify what went well and what could be improved, and collaboratively decide on action items for the next Sprint. They ensure that the meeting stays focused, encourages open communication, and fosters a constructive and blame-free environment for continuous improvement.

136

參考答案

The Scrum Master provides support to the Scrum Team in a variety of ways, including: - Mentoring members of the team in self-management and cross-functionality - Assisting the Scrum Team in focusing on creating elevated Increments that meet the Definition of Done - Removing roadblocks to the Scrum Team's progress - Ensuring that all Scrum events occur and are positive, productive, and kept within the timeframe. The Product Owner benefits from the Scrum Master in a variety of ways, including: - Assisting in the use of strategies for successful product goal definition and backlog management; - Assisting the Scrum Team in comprehending the need of having clear and precise Product Backlog items; - Assisting in the development of empirical product planning for a complicated environment The Scrum Master helps the company in a variety of ways, including: - Leading, mentoring, and training the organization's Scrum adoption. - Making plans and recommending Scrum implementations within the organization assisting employees and stakeholders in understanding and putting into practice an empirical approach to complex work. - Removing barriers between stakeholders and Scrum Teams.

137

參考答案

The main Scrum ceremonies include: - Sprint Planning: The team decides on the tasks and user stories they will work on during the sprint. - Daily Standup: A brief meeting where team members discuss what they did yesterday, what they will do today, and any obstacles they are facing. - Sprint Review: A meeting to review the progress made during the sprint and gather feedback from stakeholders. - Sprint Retrospective: A meeting where the team reflects on the sprint to identify what went well and where they can improve.

138

參考答案

The scrum master helps teams during PI planning. They make sure there is clear communication between the teams. The scrum master also helps the team set common goals. They guide everyone through each step of the process. If any problems come up, they work to solve them. The scrum master also helps everyone work together, so all teams agree on what is most important and what needs to be finished.

139

參考答案

A Scrum Master does not have to be there; he or she only has to ensure the Development Team has a Daily Scrum. The Scrum Master enforces the rule that only Development Team members participate in the Daily Scrum. Although the Scrum Master or Product Owner can attend this meeting to facilitate the Daily Scrum, this is certainly not required by Scrum. The Development Team members synchronize their work, monitor their progress toward the Sprint Goal and if required they adapt the Sprint Backlog and the plan for the next 24 hours during the Daily Scrum

140

參考答案

- Enforce work distribution through better backlog grooming. - Rotate responsibilities. - Encourage ownership of all tasks.

141

參考答案

In the short term, the candidate would raise awareness of the impact of tech debt during sprint planning, advocate for allocating capacity to bug fixes, and use data to show how crashes slow progress. In the mid-term, they would work with the Product Owner to prioritize technical debt, incorporate it into the backlog as stories, and educate on the long-term benefits of maintaining code quality.

142

參考答案

I start with foundational training on Agile principles and methodologies. Then, through regular workshops and one-on-one sessions, I guide the team in adopting Agile practices, emphasizing continuous learning and improvement.

143

參考答案

Sustainable pace means the team can maintain their productivity and quality indefinitely without burning out. I track this by watching commitment versus completion rate, but also by paying attention to the team. If people are working nights and weekends, or if I'm seeing more bugs, or if people seem exhausted, the pace isn't sustainable. I work with the Product Owner to make sure we're committing to work that the team can realistically finish in a sprint with time for learning and slack. I also make sure retros include a question about pace and workload—if people feel overloaded, we talk about it. In one case, a team was consistently pulling in extra work to try to impress the executives. I had a conversation about the data: the team's bugs went up 30% when they worked overtime, so actually they were slower overall. We committed to realistic scope, quality went back up, and paradoxically they shipped more value.

144

參考答案

This is your candidate's chance to brag and demonstrate their abilities. It will provide you with a glimpse into their personality as well as their passion and dedication to their work as a Scrum Master. Listen for: Excitement or pride as they talk about their accomplishments. Listen out for what motivates them and consider if you as an employer can meet that motivational need — Is it money for them and their family? Promotion potential?

145

參考答案

Addressing a desire for more autonomy involves creating an environment that supports self-organization and shared decision-making. I conduct discussions with team members to understand their perspectives and expectations regarding autonomy. Whenever feasible, I delegate decision-making responsibilities to the team, especially during sprint planning and daily stand-ups. Additionally, I encourage the team to identify areas where they can take ownership and make decisions collectively. By fostering a sense of empowerment and trust, we create a culture that values autonomy and allows team members to contribute actively to the decision-making process.

146

參考答案

Scrum Framework is itself an approach of Agile Methodology for product development. Agile is a long term process and Scrum is a slow term process. So going with the Scrum makes work more process more efficient by breaking the system into sprints. These Sprints help in delivering quality product in a short time period and adds the value for the subtle approach with Agile Methodology. Their collaborative approach not only gives quality product but also helps to remove blockages very easily with high efficiency. Agile and scrum are two different approaches and so here are some differences between features of both of them: Agile development is based on the iterative and incremental approach and with Scrum Framework it is implemented a way with which incremental builds are delivered to customer every 2-3 weeks. - Agile gives a leader and Scrum is mostly dependent on self-organised cross-team functioning. Eventually when both have a collaborative approach to product development high-quality product is delivered. - Agile is rigid method while Scrum Framework is rather a flexible approach. - Agile asks for a simple design and execution of software product but Scrum fosters innovative and incremental approach. - The most elementary measure of progress in the Agile Method is working software but with Scrum, working software is not a priority. - Customer competitive advantage through everyday work approach, technical advancements and adjusting the behavior is the principle of Agile Methodology which when structured with Scrum Framework gives a more incremental approach to a self-organised cross functional team with the efficient performance for collaborative iterative development approach.

147

參考答案

I address conflicts early by facilitating a private discussion between the parties. I help them focus on the problem, not the person, and find common ground. I also encourage collaborative activities like pair programming to rebuild trust and teamwork.

148

參考答案

The ideal Scrum team consists of 7 ± 2 members (5 to 9 people). This size ensures: - Effective collaboration without excessive communication overhead. - Sufficient skills and expertise to complete work efficiently. - A balance between flexibility and coordination.

149

參考答案

Sprint Planning is a Scrum event or meeting where the team decides what work will be done in the upcoming Sprint. They also strategize how it will be accomplished. It sets a clear direction for the team and aligns everyone on the same objectives before execution begins.

150

參考答案

Effective communication is foundational to Scrum success. I ensure communication clarity by organizing regular ceremonies like Daily Standups, Sprint Planning, and Retrospectives. Additionally, I facilitate constant communication through tools like Slack or Microsoft Teams and encourage face-to-face interactions when possible. By fostering an environment where information flows freely and transparently, the team can collaborate seamlessly towards achieving their sprint goals.

151

參考答案

An Agile mindset prioritizes adaptability, collaboration, customer value, and continuous improvement over rigid planning.

152

參考答案

Scrum often uses automated performance or regression testing to deliver software as fast as possible. What are the tools the candidate prefers? How well have teams worked with these tools?

153

參考答案

Definition of Done (DoD) is a shared understanding of what it means for work to be complete and releasable. It ensures consistent quality across Sprints.

154

參考答案

A Confidence Vote is a quick poll where the team expresses their confidence in achieving the sprint goal. It helps identify potential issues early and ensures the team is aligned and committed to the goal, promoting transparency and proactive problem-solving.

155

參考答案

Risk management is an integral part of every project, and every company or business has a reliable risk management strategy in place that comes into play whenever an emergency occurs. Risk mitigation is not a one-time thing; it is an ever-developing process that requires evaluation. If a specific risk management strategy fails to work, it is immediately identified and taken care of with either a new approach or required modifications. Risk management primarily involves the five phases that we have listed below: - Risk Identification - The first step or stage in the risk management process is risk identification, where the potential risks are identified. Members from the senior management and others in an authoritative position come together to pick out and discuss the identified risks (which can range from legal risks, market risks and regulatory risks, etc.) so that their root causes can be analysed, and eventually a solution can be figured out to address that. - Risk Analysis - The next stage in this is where the nature of the risks is analysed. In this, the magnitude of the identified risks and how they can impact the business is carefully scrutinised. During the analysis, everyone oversees whether this risk is potential enough to affect operations, reduce revenue, stall deliverables and cause inconveniences to the stakeholders and customers. It is only after this analysis that a risk management framework is designed to be followed by the team. - Risk Evaluation - Not every risk is of the same nature. Some risks are low-intensity while others involve priority settlement. So, once the risk is identified, it should be assessed, keeping in mind the impact it can cause. Categorise the risks so that the concerned team can work on them without any external influence or delay in the process. Make sure to address the high-risk areas first before the medium or low-intensity risks are taken care of. - Risk Mitigation - Finding ways and strategies that can help mitigate the risks is important. For this, it is important to discuss the issues that the potential risks can raise with the professionals of the risk management industry or those who are a part of the organisation's risk mitigation team. The meeting conducted for this would involve stakeholders, people from the senior management team, the clients, and those involved in the company's decision-making process. The purpose of this discussion would be to list out the risks, agree on a practical solution and issue a prompt implementation of the same. - Risk Monitoring - To ensure that any form of risk does not disrupt the functioning of the business or hamper the day-to-day deliverables, it is important to constantly keep a tab on them. Since this is not practical to achieve singlehandedly by employees, the risk management teams should have a lookout for this with their risk tracking systems. Every company, more or less, has a well-integrated risk management setup that stays vigilant towards such issues and promptly notifies the organisation regarding any upcoming crisis or emergency.

156

參考答案

The Scrum Team operates based on three pillars: transparency, inspection, and adaptation.

157

參考答案

When discussing your past experiences as a Scrum Master, it's beneficial to use the STAR method (Situation, Task, Action, Result) to structure your responses. This approach can help you present your experiences in a clear and concise manner, making it easier for the interviewer to understand your skills and capabilities.

158

參考答案

Promoting a culture of continuous improvement involves creating an environment that encourages reflection, collaboration, and a commitment to learning. I initiate regular retrospective meetings where the team reflects on their processes, communication, and overall performance. During these meetings, I facilitate open discussions on what went well, areas for improvement, and actionable steps for enhancement. I also encourage the team to experiment with new approaches, tools, or techniques, fostering a mindset of continuous learning. Additionally, I ensure that the team's improvement initiatives are tracked and revisited regularly. By celebrating achievements, learning from challenges, and actively seeking ways to enhance our processes, we instill a culture of continuous improvement that contributes to the Scrum team's overall success.

159

參考答案

The Scrum team is responsible for delivering high-quality product increments during each sprint. This includes managing the sprint backlog, participating in Scrum ceremonies (like sprint planning, daily Scrum, sprint review, and retrospective), and adapting to changes as needed. The team works collaboratively to ensure transparency, inspection, and adaptation.

160

參考答案

Common Agile metrics include: - Velocity - Sprint burndown - Cycle time - Lead time - Predictability ratio - Escaped defects Metrics help measure team health, not just output.

161

參考答案

Sashimi is utilized in Scrum to verify the completion of all functionalities after showcasing a product. It involves various methodologies such as analysis, design, coding, testing, and documentation. By adopting an incremental approach to product design, like user story mapping, developers can use these thin releases to initiate the design and implementation of the essential architecture required to support them. This approach, sashimi, enables the team to focus on functional needs and develop the architecture accordingly.

162

參考答案

Minimum Viable Product (MVP) is the prototype of a product with basic features released in the market so that early customers can use and provide critical feedback on the product. Minimum Marketable Product is the functional software that is ready for monetization. It consists of all the minimum essential features. It is ready to be launched in the market. It saves you the time of building the whole product with all functionalities. You can give the customers what they want.

163

參考答案

To manage risk, there are five essential measures to follow. They are as follows: - Identification of Risk: The first step is to determine the risks that the company faces in its current operational environment. There are numerous forms of risks, including legal risks, environmental risks, market risks, regulatory risks, and so on. It's critical to recognize as many of these risk factors as possible. - Analysis of the Risk: It is necessary to examine a risk once it has been recognized. The risk's scope must be assessed. It's also crucial to comprehend the relationship between risk and other internal components. It is crucial to establish the severity and importance of the risk by looking at how many business operations it affects. - Ranking the Risk: Risks must be prioritized and ranked. Based on the intensity of the risk, most risk management solutions have several risk categories. Risks that can result in serious loss are ranked the highest, while risks that may cause some inconvenience are rated the lowest. - Treating the Risk: Every risk must be minimized or eliminated to the greatest extent practicable. This is accomplished by contacting specialists in the field to which the risk pertains. In a manual situation, this means calling each and every stakeholder and then scheduling up meetings for everyone to talk about and debate the concerns. - Reviewing the Risk: The risk is then reviewed to ensure that the risk has been eliminated completely.

164

參考答案

I ensure the meeting is time-boxed, I use a structured format (like Start/Stop/Continue), I keep the focus on process improvements rather than blaming individuals, and I ensure the meeting ends with concrete, actionable items that the team commits to.

165

參考答案

Absolutely not, and if your organization is doing this, it's a red flag. Velocity is a forecasting tool, not a performance metric. The moment you tie it to appraisals, teams start gaming it inflating story points, reducing DoD standards, avoiding complex work. If a manager asks "why is your velocity low?" in a performance review that's a coaching opportunity for the Scrum Master to redirect the conversation toward outcome metrics instead.

166

參考答案

Time boxing means allotting a fixed unit of time for an activity. So the time is over activity is over – irrespective of the result. This brings in discipline, predictability and creates a situation for inspect and adapt. Every event in Scrum is time boxed which Must not be extended like Sprint, Daily Scrum etc.

167

參考答案

That's not a lot of information to go on, so the first thing for me to do would be to figure out what's going on. The big question here: are they actually delivering value every Sprint? Decreasing velocity may be an indication of a problem, but it might not be. For example, if the team is getting more accustomed to the product, and more confident when working with it, their estimates would tend to go down, which could show decreasing velocity. But there also might be some external dependencies that prevent the team from completing the same amount of work as before. Or even something natural reasons. Like during a flu season where many team members may be getting sick all at the same time. So my approach would be first figure out what's wrong. In addition, I wouldn't be as concerned with velocity itself - this is really just a metric to help the team plan. It doesn't really represent value or team performance. It may be more useful to look at some other metrics like cycle time, number of defects, team health index, and more.

168

參考答案

The DoR is somehow related to DoD. It is a list of what needs to be done to a product backlog item before the team can start executing it in the next sprint. You can view the definition of ready as the "DoD" the Product Owner has to fulfill so that the Development Team accepts the story in the Sprint Planning meeting.

169

參考答案

- Enhances Decision-Making: By incorporating confidence levels, teams can better understand the collective sentiment and potential risks associated with decisions. - Fosters Open Communication: Confidence Voting encourages team members to articulate their thoughts and concerns openly, promoting a culture of trust and collaboration. - Improves Retrospectives: In Agile retrospectives, Confidence Voting helps teams assess the effectiveness of new processes or changes, leading to more targeted improvements. While Confidence Vote is not a part of traditional Scrum practices, it can be a valuable tool for Agile teams looking to enhance their decision-making processes and retrospectives.

170

參考答案

The Product Backlog is owned by the Product Owner and contains all potential work for the product. It is always evolving and never complete, ordered by priority and value. The Sprint Backlog is owned by the Developers and contains work selected for the current sprint only. It is fixed for the duration of the sprint and ordered by how the team will execute the work.

171

參考答案

Utilizing burndown charts, velocity reports, and sprint reports in Jira, I track the team's progress and performance, using these insights to inform future sprint planning and team discussions.

172

參考答案

Scrum is an agile framework for managing complex work. It involves a small team, a Product Owner who prioritizes work, and a Scrum Master who facilitates the process. Work is done in time-boxed iterations called Sprints, with events like Sprint Planning, Daily Stand-ups, Sprint Review, and Retrospective to ensure continuous inspection and adaptation.

173

參考答案

Following are the ways by which a Scrum Master can ensure that the three pillars of Scrum are being implemented by the team: - Daily Scrum: Examine the Team Board and adjust the plan for the next day, making sure that any changes are communicated to the entire team. Examine the Impediments Board and, if necessary, adapt ways to address impediments. - Sprint Planning: Examine the average Team Velocity for the preceding three or four Sprints, verify that the velocities were transparent to the team, and verify that the team adapted the Velocity to be used for Sprint planning. Examine the Product Backlog (PB) to ensure that it is current, transparent to all stakeholders and that the team adjusts the PBI estimations as needed. - Sprint Retrospective: Examine the procedure that was followed and make preparations to adapt it if required, ensuring that any modifications are communicated to all team members. - Sprint Review: Inspect the increment and, if necessary, adjust the Product Backlog, ensuring that any changes are communicated to all stakeholders. Examine the Release Plan and make any required adjustments, ensuring that any changes are communicated to all stakeholders.

174

參考答案

I first have a private conversation to understand the root cause of the struggle, whether it's a skill gap, personal issue, or impediment. I then provide support through mentoring, pair programming, or helping them remove blockers. I focus on enabling them rather than micromanaging.

175

參考答案

The main role of a Scrum master is to overview the project requirements and make sure that the team is meeting the project deadlines. The Scrum Master is also responsible for removing any impediments in the process and ensures that all Scrum practices are followed. They have to boost the overall productivity of the team in the process.

176

參考答案

In project management, scope creep is a situation where the parameters of a project (as discussed initially) change beyond control. These parameters can vary, ranging from the addition of new features to a product, redesign of a gadget, or renovation of a progressing construction site. There could be many more similar examples that define scope creep extensively, and most of us are already familiar with them. But the reason why scope creep is defined as a major issue is that all these alterations to an existing product or project mess up the predetermined budget and resources, and also end up demanding more time. Many people cite improper planning as the sole reason behind it. Also, when things are randomly rushed from the beginning without proper assessment, a workable strategy is absent, core team members get involved at the last minute and share insights for the project, everything gets out of control, and therefore lacks precision, and the project fails to turn out the way originally planned. So, it is important to be ready when it comes to planning for a project and not act haphazardly without evaluating the project carefully.

177

參考答案

Role modeling, coaching conversations, and retrospective techniques.

178

參考答案

During a critical project, our team faced a major roadblock due to conflicting stakeholder requirements. I facilitated a series of focused workshops to align expectations, which resulted in a clear, prioritized backlog and improved team morale.

179

參考答案

I measure success through team feedback, such as satisfaction surveys and retrospectives. I also look at team performance metrics like velocity and quality, but the most important metric is the team's sense of empowerment and ownership. If the team feels supported and self-organized, I consider it a success.

180

參考答案

Product backlog is the single source of all requirements within a scrum.

181

參考答案

I create a culture of trust by giving the team autonomy over their work. I ensure they have the necessary resources and tools. I provide clear expectations and then step back, trusting them to execute. I am also available for support when needed without micromanaging.

182

參考答案

The Agile manifesto in software development is a document with four values and twelve principles. These values and principles describe an iterative approach to handling complex projects. Knowing this manifesto can give the impression that you are aware of the basics of Agile.

183

參考答案

Timeboxing in Scrum refers to setting fixed, limited durations for certain activities or events, such as sprints, meetings, and tasks. The goal is to ensure that work is focused, efficient, and manageable within a specific timeframe.

184

參考答案

A Burndown chart is a visual graph that tracks the amount of work remaining for a development team over time within a sprint or project. It depicts the progress of completing user stories or tasks against the sprint or project duration timeline. Conversely, a BurnUp chart illustrates the cumulative amount of work completed over time compared to the total work planned for the project. It shows how much of the project's scope has been delivered as time progresses, providing a view of both completed work and the total project work.

185

參考答案

I encourage the team to listen actively and thank stakeholders for their input. Feedback is captured by the Product Owner and added to the Product Backlog for consideration. Questions are answered directly by the team members who worked on the features. Unrelated discussions are deferred to follow-up sessions.

186

參考答案

I guide the team to consider various aspects of the work, such as complexity and dependencies, and then collectively decide on the points using a consensus-based approach like Planning Poker.

187

參考答案

Sprint progress is tracked using tools like Burndown/Burnup Charts, the Sprint Backlog, and Daily Stand-ups. This focuses on remaining work (hours/story points) versus ideal progress to visualize if you'll meet goals, identify scope creep, and adjust actions daily.

188

參考答案

Driving agile transformation needs a clear plan, solid leadership, and teamwork across all groups. Help build a culture of continuous improvement by letting people feel confident, offering training, and using feedback from teams. Make changes based on this input, so the way of working matches what the company wants. At the same time, be sure everyone agrees and supports these changes.

189

參考答案

Burn-Up and Burn-Down Charts are used to trace the progress of the project. The burn-up chart illustrates the amount of work completed, while the burn-down chart illustrates the amount of work remaining to complete a project. Remember that the efforts are measured in terms of user stories and not hours.

190

參考答案

DoD stands for Definition of Done. DoD is defined at the start of the project. It is achieved when - The story is development complete - QA complete - The story meets and satisfies the acceptance criteria - Regression around the story is complete - The feature is eligible to be shipped/deployed in production.

191

參考答案

Definition of Done (DoD) is a checklist of items that need to be completed to declare a project or task as ‘Done.' The checklist includes written codes, comments on coding, unit tests, integration testing, design documents, and release notes.

192

參考答案

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.

193

參考答案

I facilitate daily stand-ups to check progress and remove any blockers. I ensure clear communication so the team stays focused on their tasks.

194

參考答案

The Agile Manifesto has four values: - Individuals & interactions over processes & tools. - Working software over comprehensive documentation. - Customer collaboration over contract negotiation. - Responding to change over following a plan. It has 12 principles, emphasizing early and continuous delivery, collaboration, and adaptability.

195

參考答案

Here are a few ways how you can handle the scrum transition from the Waterfall model: - (Content not explicitly listed in the provided text beyond the introductory statement). Following the steps as mentioned earlier will ensure a smooth transition from waterfall to scrum.

196

參考答案

The events are: Sprint (a time-boxed iteration of work), Sprint Planning (to plan what to do and how), Daily Scrum (a 15-minute daily sync), Sprint Review (to inspect the increment and adapt the backlog), and Sprint Retrospective (to inspect the team's process and plan improvements).

197

參考答案

Typical Scrum Master Sprint anti-patterns are below. Any of these behaviors will impede the team's productivity. It is the Scrum Master's obligation to prevent them from manifesting themselves. Some of the Scrum Master anti-patterns are: - Keeping the Scrum team dependent: In this scenario, the Scrum Master pampers the team to a level that keeps the team dependent on his or her services: organizing meetings, purchasing stickies and sharpies, taking notes, updating Jira — you get the idea of this service level. More critical, however, is when the Scrum Master decides to keep the team in the dark about principles and practices to secure his or her job. This behavior is only a small step away from the dark side. - Flow disruption: The Scrum Master allows stakeholders to disrupt the workflow of the Development Team during the Sprint. There are several possibilities on how stakeholders can interrupt the flow of the team during a Sprint: a) The Scrum Master has a laissez-faire policy regarding access to the Development Team. b) The Scrum Master does not object when management invites engineers to random meetings as subject matter experts. c) Lastly, the Scrum Master allows either the stakeholders or managers to turn the daily Scrum into a reporting session. - Lack of support: The Scrum Master does not support team members who need help with a task. Development teams often create tasks an engineer can finish within a day. However, if someone struggles with a task for more than two days without voicing that they need support, the Scrum Master should address the issue. Importantly, this is also the reason for marking tasks on a physical board with red dots each day if they haven't been moved on to the next column. - Turning a blind eye to micromanagement: The Scrum Master does not prevent the Product Owner — or anyone else — from assigning tasks to engineers. The Development Team normally organizes itself without external intervention. And the Scrum Master should act as the shield of the team in this respect. - : The Scrum Master sweeps conflict and problems under the rug by not using Sprint Retrospectives to address those openly. This behavior is often a sign of bowing to politics and instead of using manipulation to meet organizational requirements that are opposing Scrum values and principles. If the organization values its underlings for following the 'rules' instead of speaking the truth why would you run Retrospectives in the first place? A 'Scrum Master' participating in cargo-cult Scrum is again a supervisor than an agile practitioner.

198

參考答案

Tracking sprint progress is essential for ensuring that the Scrum team is on track to meet its goals and deliverables. Here are key methods to effectively track progress during a sprint: - (Content not explicitly listed in the provided text beyond the introductory statement).

199

參考答案

I first understand the urgency behind the request. If it's critical, I facilitate a discussion with the Product Owner to assess trade-offs. The Product Owner decides whether to adjust scope by removing equivalent work or defer the change. I protect the team from disruption while ensuring business priorities are respected.

200

參考答案

Managing remote teams requires strong communication, collaboration, and trust. Key strategies include: Daily Standups: Ensuring team members are aligned and addressing blockers. Asynchronous Communication: Using tools like Slack or Microsoft Teams to keep discussions flowing without delays. Clear Documentation: Maintaining well-structured Confluence pages or Google Docs for clarity. Sprint Planning & Retrospectives: Regularly reviewing what works and improving processes. Time Zone Coordination: Ensuring meeting schedules accommodate team members across different regions.

不想錯過任何事？

100%通過的Cisco、PMP、CISA、CISM、AWS模擬測試現已發售！
立即獲取

考取認證，讓履歷脫穎而出。

不想錯過任何事？

100%通過的Cisco、PMP、CISA、CISM、AWS模擬測試現已發售！ 立即獲取

考取認證，讓履歷脫穎而出。

100%通過的Cisco、PMP、CISA、CISM、AWS模擬測試現已發售！
立即獲取