95

参考回答

Technical debt is the additional work created when teams choose quick or short-term solutions instead of sustainable ones. A Scrum Master helps manage technical debt by creating transparency, encouraging engineering best practices, and ensuring that debt reduction is treated as part of delivering value rather than as optional cleanup work.

96

参考回答

In a previous project, we had a team with varying levels of Scrum experience. I adapted our practices by incorporating additional training sessions and simplifying our Scrum ceremonies, which led to improved team cohesion and project success.

97

参考回答

Some types of risks in Scrum are: - Budget: The risk of exceeding budgets - People (team): Team members need to be of appropriate skill and capability - Sprint (duration and deliverables): Exceeding the duration, addition of the scope of work - Product (user stories, epics): Having ill-defined user stories and epics - Knowledge and capability: Having the appropriate resources Managing risks involves identifying, assessing, analyzing, defining, and implementing risk responses, monitoring, and managing them. These are done on a continual basis right from the starting of the project until completion. It is essential to understand that the impact of the risk is based on the proximity of the actual occurrence of the risk.

98

参考回答

The candidate should share a specific challenge, such as resistance to Scrum adoption, a team conflict, or a major scope change. They should explain how they addressed it—for example, through coaching, facilitation, or escalation—and what lessons they learned, such as the importance of stakeholder buy-in, patience, or adaptive leadership.

99

参考回答

Scrum teams must connect Sprint Goals to measurable business outcomes. I ensure: - Product backlog reflects strategic objectives - OKRs cascade into Sprint Goals - Value delivery metrics are visible - Stakeholders review increments regularly Agile execution without strategic alignment becomes delivery chaos.

100

参考回答

- Clearly defining Acceptance Criteria. - Collaborating with stakeholders. - Using regular backlog grooming sessions.

101

参考回答

Resistance usually stems from: - Fear of losing control - Lack of clarity on ROI - Previous failed transformations I address resistance by: - Sharing measurable pilot results - Using data-driven case studies - Creating leadership coaching sessions Transformation fails without executive buy-in.

102

参考回答

Once a particular sprint session is over, a review session is held where the team members look back on their performance to identify areas that can be improved in the future sprint. In this meeting, everyone in the team comes together to sit and precisely reflect on things, where they discuss the sprint issues, the achievements and the future tasks to work on.

103

参考回答

Velocity measures output. Success requires measuring more than that. Metrics I track alongside velocity include cycle time, throughput, team satisfaction, and quality metrics like defect rates. A healthy team shows improvement across all of these over time, not just velocity.

104

参考回答

My favorite Scrum event is the daily Scrum because it allows the team to communicate openly about progress or pain points and build camaraderie. It ties back to what is important in the Scrum process, such as transparency and collaboration.

105

参考回答

To ensure timely delivery of action items, the Scrum Master plays a pivotal role throughout the Scrum process, not solely in retrospectives. It begins with identifying actionable items during retrospectives and ensuring they are assigned clear ownership. The Scrum Master maintains accountability by overseeing tasks across all Scrum ceremonies and activities. Agile tools like JIRA or Azure DevOps are commonly used to track and prioritize action items, providing visibility and facilitating effective team collaboration. To further ensure quality and efficiency, the Scrum Master can utilize a cloud-based platform to maintain quality and ensure timely delivery. One such platform is TestMu AI, an AI-native test execution platform that lets you run manual and automated cross-browser compatibility and functionality tests at scale across 3000+ browsers and OS combinations. It integrates seamlessly with other CI/CD tools, allowing issues to be caught and fixed early, maintaining high-quality standards, and ensuring timely delivery. By combining bug-tracking tools with comprehensive testing platforms like TestMu AI, the Scrum Master can effectively oversee the process and maintain consistent delivery standards.

106

参考回答

I lead by example, always seeking feedback and looking for ways to improve. I ensure retrospectives are action-oriented and that the team follows through on improvement items. I also celebrate small wins and experiments, encouraging a mindset of learning over perfection.

107

参考回答

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

108

参考回答

This is one of the most subtle yet critical aspects of being a Scrum Master. I define my role as one of a servant leader because my responsibility is to enable the team by removing barriers, fostering dialogue, and helping set the stage for optimal performance. On the other hand, I must be more directive concerning the Scrum process itself. I need to make those adjustments if the team is neglecting aspects of Scrum or reverting back to practices that are not agile. The main point is to control the process while granting the team autonomy in how they carry out their tasks. I have learned that strong professional relationships based on trust make this balance easier—the team understands that I am trying to help them succeed, not impose arbitrary constraints.

109

参考回答

The key difference lies in leadership style, responsibilities and control over the team. The Scrum Master is a servant leader and Agile coach with no direct authority over the team, focusing on Scrum process and team effectiveness. The Project Manager is a planner and controller with authority over team members, focusing on project scope, schedule, and budget.

110

参考回答

The Sprint Retrospective is a meeting that happens at the end of each sprint where the Scrum team reflects on what went well, what didn't, and how to improve. It is a chance for the team to inspect and adapt the process to continuously improve their efficiency and effectiveness.

111

参考回答

The candidate should express concern about including a story without complete designs, as it introduces risk. They would advocate for splitting the story or deferring it until designs are ready, ensuring the team has clear acceptance criteria, and facilitating a discussion with the Product Owner about the impact on sprint commitment and quality.

112

参考回答

Flow efficiency, team happiness, cycle time, lead time, defect rate, value delivered.

113

参考回答

The Scrum Master's responsibilities include the following: - Scrum Master serves the organization in the following ways: (Content not explicitly listed in the provided text beyond the introductory statement).

114

参考回答

As per the process, the Scrum Master is supposed to help the team get the best results. Acting as a facilitator for internal and external workshops can sometimes be challenging. A workshop facilitator must stay impartial while discussing topics and refrain from adding facts or opinions to the discussions. If you have the necessary expertise, you've got all it takes to facilitate most general product development workshops. However, if the workshop is about changing your company's Scrum process, you should not facilitate that session.

115

参考回答

Capacity is determined by considering the team's historical velocity, the number of available working days (accounting for holidays, time off), and the team's focus time. We use this data to forecast how much work the team can realistically commit to for the Sprint.

116

参考回答

Epic: An Epic is a project that requires the definition of a Minimum Viable Product (MVP) and approval by Lean Portfolio Management before implementation. Because they have such large scope, it is necessary to define an MVP for this type of project to ensure its success. Stories: Story or User Story is a tool used in Agile to record the description of a software product from the end-user perspective. These user stories are divided into small phases and then developed in single sprints by Agile teams. Tasks: Tasks refer to partitions of stories that are broken down to ease work. It is the smallest unit in Scrum that is used to denote work.

117

参考回答

- Teams need to be collaborative and committed with the positive outcome - A naïve scrum master can become the cause to collapse the project - Well defined tasks are need of the hour, in case the project has many inaccuracies - It works better for smaller projects and is challenging to scale to larger, more complex projects

118

参考回答

User stories can be written by anyone. Although it is the product owner's job to ensure that an agile user story backlog exists, this does not imply that the product owner is the one who produces them. During the early stages of product development, the team discusses needs and records them as user stories. As long as there is a product backlog, it will never be frozen. As a result, if someone thinks there's a missing requirement or anything that could benefit the client, they can add it to the queue as a user story. There is no rule or guideline indicating that the stories must be written solely by the product owner. Because there is a set format, anyone creating the story should know exactly what it means and how to write it.

119

参考回答

A Scrum Master ensures the development team's productivity by assisting with team decisions and eliminating obstacles. As a servant-leader, the Scrum Master assists the development team in creating functional software and ensuring the delivery of the product increment. The Scrum Master strives to assist the team in performing at their peak level.

120

参考回答

Prior to starting the Scrum sprint, the product owner evaluates and prioritizes a comprehensive list of new features, change requests, enhancements, and bug reports. In the case of a new project, this includes the new features that must be incorporated into the system. This comprehensive list is known as the product backlog. The specific items chosen for the sprint are referred to as the sprint backlog.

121

参考回答

The five Scrum values — commitment, courage, focus, openness and respect — are what drives a Scrum team and the Scrum Master's success. A Scrum Master candidate should be very familiar with these values and have a strong connection to some or all of them. They should also be able to explain why any of these values are important to them. Listen for: How they've applied these five values to their work in the past and how they'll bring them into future roles — namely as your potential Scrum Master.

122

参考回答

Coach stakeholders on risk of burnout, and support team planning discipline.

123

参考回答

I prioritize risk mitigation tasks based on their cost of delay. Not all risks need immediate action; some can be monitored. I work with the Product Owner to allocate a small percentage of the team's capacity each Sprint for risk-reducing activities, ensuring it doesn't derail delivery.

124

参考回答

I handle conflicts by first identifying the root cause and then facilitating open communication between the parties involved. I employ strategies like active listening and mediation to ensure a fair and effective resolution, fostering a collaborative team environment.

125

参考回答

The four Agile values are: - Individuals and interactions over processes and tools - Working software over comprehensive documentation - Customer collaboration over contract negotiation - Responding to change over following a plan These values guide Agile frameworks like Scrum.

126

参考回答

Scrum facilitates collaboration through events like the Daily Stand-up and Sprint Review, which encourage frequent communication. The Sprint Goal aligns the team on a common objective. The retrospective provides a structured way to improve how the team works together.

127

参考回答

The long-term objective for the Scrum Team.

128

参考回答

The review session meeting that is carried out at the end of the sprint process is known as the Sprint Review. In this meeting, the scrum team and the stakeholders are involved, where the scrum team assesses the completed work (product increment) before presenting it to the stakeholders for review and feedback and additionally prepares the product backlog for upcoming sprints. The objectives of conducting sprint reviews are: - Tracking the list of completed tasks - Identifying problem areas in the last sprint - Reflecting on the feedback gathered during stakeholder meetings - Putting together a plan for the future sprints

129

参考回答

If you don't know where you are going, any road will get you there. Your candidate should understand that an agile transition needs to have an objective and a goal — which means planning ahead. To prepare for kicking off a transition to Scrum is to listen and observe: your candidate should express interest in interviewing as many team members and stakeholders as possible, before jumping into action. These interviews should include everyone, no matter their role — engineers, QA professionals31, UX and UI designers, product managers — in order to identify the patterns underlying current problems, failures, and dysfunction within the organization. Merging those patterns with the most pressing technical and business issues will identify the most likely objectives for the first Scrum Teams. This observation phase, during which a Scrum Master performs their interviews, will typically require between four and twelve weeks depending upon the size and structure of the organization. The training of future team members and stakeholders should commence and run parallel to the interviews. Creating the first Scrum Teams from the existing engineering and product departments is the second step in kicking off a transition to Scrum. Your candidate should be able to sketch the rough plan of a transition and address common issues that might arise during kickoff.

130

参考回答

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

131

参考回答

Sure, Sprints may be cancelled ahead of a timebox (a brief unit of time dedicated to a specific activity) reaching its end.

132

参考回答

I facilitate a collaborative discussion to formulate a concise Sprint goal that reflects the business objective for the Sprint. I then ask the team to restate the goal in their own words and confirm understanding. The goal is prominently displayed and referenced throughout the Sprint.

133

参考回答

During a Retrospective early in my career, a team member told me my facilitation felt controlling and that I was steering conversations toward conclusions I had already reached. That feedback was uncomfortable but accurate. I had been filling silences too quickly rather than letting the team think and respond. I changed my facilitation approach — I started asking more open questions, waiting longer before responding, and explicitly inviting quieter team members to contribute. The quality of Retrospective output improved noticeably over the following sprints. Negative feedback is useful data. My job is to respond to it the same way I ask the team to respond to theirs.

134

参考回答

To effectively address resistance to adopting Scrum practices, fostering a culture of learning and collaboration within the team is essential. Start by openly discussing concerns with team members to gain insights into their reservations. Educate them about the benefits of Scrum, highlighting its ability to strengthen teamwork, foster transparency, and increase project efficiency.

135

参考回答

Adaption - If an inspector or inspector finds out that one or more parts of a process deviate beyond acceptable boundaries, the method or the material being processed must be modified because everything in a workflow should always strive to remain efficient and effective. Any problems should be looked into as soon as possible. That way, you can ensure that the same problem(s) will not occur again since it's crucial when it comes down to getting your workflow and business up and running at peak efficiency.

136

参考回答

Yes, the cancellation is possible, and only the product owner (PO) has the right to do it.

137

参考回答

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.

138

参考回答

Scrum events are structured activities that support planning, inspection and adaptation. They include the Sprint, Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective. These events are time-boxed to maintain focus, avoid unnecessary discussions and ensure regular feedback. Time-boxing creates consistency, improves efficiency and helps teams inspect progress and adapt quickly without wasting time.

139

参考回答

It's called "Sprint"

140

参考回答

User stories are prioritized based on their business value, urgency, and dependencies. The Product Owner works closely with stakeholders to focus on stories that deliver the most value, ensuring the team works on the most important tasks first.

141

参考回答

Scrum is an iterative framework with time-boxed sprints, defined roles, and structured ceremonies like daily stand-ups and sprint reviews. It focuses on delivering small increments within a sprint cycle. On the other hand, Kanban is a continuous flow system that visualizes work using a board with columns representing workflow stages. It limits work in progress (WIP) to maintain efficiency. Teams can mix them (Scrumban) using Scrum's structure while applying Kanban's WIP limits and visual tracking. This hybrid approach helps teams manage unpredictable work while maintaining agility, improving workflow efficiency and adaptability.

142

参考回答

Various techniques to improve collaboration include: Clear Sprint Goals, Effective Scrum Events, Cross-functional Working, Transparency through Visuals, Psychological Safety, and Continuous Feedback.

143

参考回答

Scrum is a type of iterative model but it is iterative + incremental.

144

参考回答

Situation: Multiple teams faced delays due to overlapping dependencies. Task: My role was to facilitate a resolution to these delays. Action: In the Scrum of Scrums, I led a discussion to re-prioritize tasks and reallocate resources. Result: This proactive approach resolved the bottleneck, realigning the teams' efforts.

145

参考回答

Waterfall Model was the first process model to be introduced. The Waterfall Model is a linear sequential life cycle model which is very easy to understand and use. The key principle on which the waterfall model emphasizes is only after the completion of one phase, the working team are allowed to begin with another phase. The Waterfall model is mostly preferred for small projects and there are no uncertain requirements. Waterfall Model has six different phases for product development. And every phase must be and should be completed before starting with another phase. So, let's dive in and read different stages of Waterfall Model Suggests. Requirement Analysis: The very first phase of the Waterfall model emphasizes on the collection of things which are required for the software development and then documenting it for further use. System Design: This very phase of the waterfall model studies the requirement and with the help of that system design is prepared. This phase also helps to specify the hardware and software parts and helps to plan the overall architecture. Implementation: In the implementation phase of the waterfall model, the system is developed with small programs called units who are later integrated with the further process of software development. Integration and Testing: In this phase of the waterfall model, the units which are developed in the Implementation phase are further Integrated after testing of each individual unit. After all the units are integrated into the system, final testing is done to check if the work processed is up to the expected parameters. Deployment : Once all kind of testing is done and if the results are satisfactory, the system is further deployed in the customer environment for the service and its use. Maintenance: To cope up with the client environment, the maintenance phase is their who provide regular feedback and help to fix the issues and patches which come up with the product and software.

146

参考回答

An Epic contains several User Stories, and each User Story is divided into smaller Tasks. This keeps the work organised and helps teams deliver value step by step.

147

参考回答

Common mistakes include: - Acting like project managers - Shielding teams from accountability - Over-facilitating ceremonies - Ignoring cultural change - Measuring success only by velocity Scrum Master maturity shows in system-level thinking, not ceremony execution.

148

参考回答

It's not ideal; Scrum Master is a full-time accountability to serve the team effectively.

149

参考回答

I integrate Kanban with Agile by using it to visualize the Agile process, employing WIP limits to manage workloads and ensuring continuous delivery aligns with Agile principles.

150

参考回答

I emphasize the importance of collaboration, clear communication, and decision-making in their role. Regular discussions about their responsibilities, challenges, and feedback from the team help in this understanding.

151

参考回答

Situation: In a project with a large, uncertain backlog. Task: We needed a quick, high-level estimation method. Action: I introduced T-shirt sizing to estimate the size of epics and features. Result: This provided a clear, easily understandable overview of the project scope, aiding in initial release planning.

152

参考回答

Based on self-management, delivery consistency, collaboration, and metrics.

153

参考回答

In my previous role, I successfully scaled Scrum across multiple teams using the SAFe framework. This involved coordinating cross-team dependencies and ensuring consistent communication, which led to a 20% increase in overall productivity.

154

参考回答

Technical debt is a reality in all software projects, and managing it effectively is crucial for long-term agility. My approach is to make technical debt visible, prioritize it intentionally, and address it systematically. First, I help the team make technical debt visible by creating specific backlog items for known technical debt or tracking metrics like code coverage over time. Second, I work with the Product Owner to understand the impact of technical debt on business outcomes, showing how neglected technical debt leads to slower delivery and more defects. Third, I encourage the team to incorporate debt reduction into their regular work, such as allocating a fixed percentage of Sprint capacity to reducing debt. I've found the most successful approach is to treat technical debt as a product investment decision. A concrete example: in a previous role, we implemented a 'technical debt radiator' that visualized the state of different parts of the codebase. This helped the Product Owner make informed trade-offs.

155

参考回答

In Scrum, DoD refers to the qualifying criteria (checklist) that must be met to label a product increment (i.e. any given task) as complete. Definition of Done (or DoD) is a formal name given to the status of the increment. And the entire scrum team (consisting of the product owner, scrum master and the developers) is responsible for the preparation of the DoD.

156

参考回答

Inspection - As a scrum user, you have to check things like your project's status and goals on a regular basis and analyze whether or not they are deviating from your expectations. Inspections should be done as often as you feel necessary, but it's important to note that too many will become a burden. The ideal inspection is when an experienced person goes over everything with a fine-tooth comb at the point where it's being done, i.e., the developer during development, the graphic designer at the completion of design, etc.

157

参考回答

I prioritize my workload using the Eisenhower Matrix, focusing on urgent and important tasks first. I also delegate responsibilities to team members when appropriate and regularly review my workload to ensure alignment with team goals.

158

参考回答

This is an open-ended question, but your perspective matters. For starters, you need to do proper research on the company you are being interviewed for. Second, your answer shouldn't be only about the company's growth but also your personal growth within the company. Being transparent about your vision for the company and yourself is the key.

159

参考回答

As a Scrum Master, I act as a shield for the team, protecting them from unnecessary interruptions during a sprint. I work closely with stakeholders to ensure that any external demands or changes are addressed outside of the sprint cycle, allowing the team to remain focused.

160

参考回答

I focus on creating a safe and open environment where team members can reflect on the past Sprint. We discuss what went well, what didn't, and how we can improve, ensuring actionable items are identified.

161

参考回答

Responsibility of the Scrum Team is to work collaboratively towards achieving the Sprint Goal. The Sprint Goal, set during Sprint Planning, represents the overarching objective that the team commits to achieving by the end of the Sprint. It encapsulates the value that the team aims to deliver to stakeholders through the completion of selected Product Backlog items. - Achieving the Sprint Goal requires close collaboration among all members of the Scrum Team. - The Product Owner ensures that the selected Product Backlog items align with the Sprint Goal and convey the highest business value. - The Scrum Master facilitates effective communication and removes any impediments that may hinder the team's progress. - The Development Team collaborates to design, develop, test, and integrate the selected items into a potentially shippable product increment

162

参考回答

Regular and transparent communication is key. I set clear expectations from the start and provide consistent updates on progress, challenges, and changes. Involving stakeholders in planning and review meetings also helps manage their expectations.

163

参考回答

This question is an invitation to the candidate to share lessons learned from the successful application of metrics to help a Scrum Team improve continuously. Suitable agile metrics follow three rules: - The first rule of tracking meaningful metrics is only to track those that apply to the team. Ignore those metrics that measure the individual. - The second rule of tracking metrics is not to measure parameters just because they are easy to follow. This practice often is a consequence of using various agile tools that offer out-of-the-box reports. - The third rule of tracking metrics is to record context as well. For example, data without context, the number of available team members, or the intensity of incidents during a sprint may turn out to be nothing more than noise. Examples of suitable agile metrics are: - Lead time, - Cycle time, - Number of defects escaping to production, or - The ratio of fixing work to creating new value. Good candidates should be aware of the evidence-based management concept.

164

参考回答

Timeboxing in Scrum involves allocating a fixed period for activities. It sets a predefined time limit, such as 15 minutes for Daily Scrum or 8 hours for Sprint Planning. Timeboxing helps teams manage meetings effectively and maintain a steady pace of work.

165

参考回答

I would address it with emotional intelligence, not authority. Steps: - Observe pattern across meetings - Have a 1:1 conversation - Share impact, not accusation - Reinforce psychological safety Then in group settings: - Use round-robin speaking - Use facilitation techniques like silent brainstorming Scrum Masters protect balanced participation.

166

参考回答

Velocity in Scrum shows how much work the team can do in a Sprint. It is found by adding up the story points for all backlog items that are fully finished at the end of the Sprint. This helps teams and Product Owners plan and guess how many Sprints it will take to finish the product backlog. It is useful for release planning. But, velocity should not be used to compare teams. It should not be a measure to track how busy people are. Trying to get higher velocity can lead to poor work or team burnout. Teams should work to have a steady and predictable velocity. This makes it easier to deliver work in a good and healthy way, instead of always working to do more.

167

参考回答

Yes, automated testing is highly recommended in Scrum projects. It ensures consistent, fast testing, catching defects early. Automated tests can be run frequently during each sprint, improving product quality and reducing the time spent on manual testing, which helps maintain velocity.

168

参考回答

Empiricism is a very important term when discussing Scrum. It is defined as work that's based on facts, experiences, evidence, observations, and experimentation. Empiricism is used in Scrum to improve transparency by providing information about what has happened/happening within the team, as well as keeping track of progress and making any changes when require for observation purposes. Instead of relying on gut feeling or guesswork alone, empirical thinking improves with agile practices such as refactoring code in iterations for example.

169

参考回答

Agile is an iterative project management and software development methodology that enables teams to deliver value to clients faster and with fewer difficulties. An agile team provides work in small, consumable pieces rather than putting all on a "big bang" release. Requirements, strategies, and outcomes are all evaluated on a regular basis, giving teams a natural method for adapting to change.

170

参考回答

Maintaining a balance between immediate goals and the overall product vision necessitates constant communication and strategic coordination. Work closely with the Product Owner to ensure that immediate objectives align with the long-term vision of the product. During sprint planning, highlight the relationship between user stories and the overall product roadmap to give the team a better understanding of their tasks. Moreover, encourage conversations on the strategic impact of immediate choices, ensuring that each sprint increment aligns with the developing product vision.

171

参考回答

A Scrum Master is a servant leader who facilitates Scrum events, removes impediments, and ensures the team follows Agile principles. The Scrum Master does not manage the team. Instead, they - enable collaboration - protect the team from distractions - Coach stakeholders on Agile practices - Drive continuous improvement.

172

参考回答

Agile | Scrum | | Agile is a development methodology that follows an incremental and developmental approach | Scrum is one of the frameworks of Agile. It follows an iterative and incremental approach called sprints which lasts 2-3 weeks | | Agile works best for organizations which small but experienced development teams | Scrum is best suited for projects where requirements keep changing | | Leadership plays a key role in Agile | Scrum supplements a self-organizing and cross-functional team | | Lacks flexibility when compared to Scrum | Scrum's flexibility is its biggest strength since it can adapt to changes quickly | | Open communication is the norm in Agile where face to face interactions happen between cross functional teams | Daily stand up meetings are held where Scrum Master, Product Owner, and the team members | | Agile needs a lot of structural and developmental changes before the start | Not many changes are required when applying Scrum | | The client feedback loop should be regular in | The client is asked for feedback after every sprint for review | | In Agile methodology, each phase of the development process like requirements, analysis, and design is tracked regularly | A demo is given to the client after every sprint for feedback | | The Project head oversees the tasks and is the decision-maker | The team has no leader so the entire team resolves issues and tasks | | Design and implementation should be simple | Innovation should drive design and implementation | | Continuous delivery of the working product is the priority in Agile | Empirical process control is followed in scrum | | Functional software is the measure of progress | Functional software is the measure of progress |

173

参考回答

I incorporate feedback from stakeholders into the Product Backlog and future Sprints. Feedback from the team is addressed in retrospectives, where we create action plans for process improvements. I track the implementation of these adjustments to ensure they have the desired effect.

174

参考回答

In Scrum, velocity refers to the measure of the amount of work a Scrum Team can complete in a Sprint, typically expressed in terms of story points or other units of work. It represents the average amount of work completed by the team over several Sprints and is used for planning and forecasting future Sprints. While velocity can provide valuable insights into a team's capacity and productivity, having maximum velocity does not necessarily ensure maximum productivity. Here's why: - Quality Over Quantity: Velocity measures the quantity of work completed but does not account for the quality of the work delivered. Focusing solely on maximizing velocity may lead to sacrificing quality or cutting corners to meet arbitrary targets. - Efficiency vs. Effectiveness: Velocity measures how efficiently a team can complete work but does not necessarily reflect the effectiveness of the work in delivering value to customers. Productivity is about achieving the desired outcomes and delivering value, which may require a balance between efficiency and effectiveness. - Unforeseen Factors: External factors such as dependencies, interruptions, technical debt, and changes in requirements can impact a team's velocity. Maximizing velocity without considering these factors may result in unrealistic expectations and increased risk of failure. - Continuous Improvement: Productivity is not static and requires continuous improvement and adaptation. Focusing solely on maximizing velocity may overlook opportunities for process improvements, innovation, and learning that could enhance overall productivity in the long run.

175

参考回答

A Project Manager plans the work to be done, assigns activities, monitors the work, and manages the results of the work being done. It is more of a directive role because they make decisions on resource allocation, and are generally the focal point in coordinating many things. As a Scrum Master, I coach and facilitate instead of manage. My role does not include providing tasks, as the team organizes itself around the work. Product decisions also fall outside my responsibilities; these are made by the Product Owner. My work revolves around assisting every person to comprehend and put into action Scrum values and practices, aiding in the removal of obstacles on the way, and enabling improvement over time. The Project Manager tends to ask, 'Are we going to hit our deadlines?' while I tend to be more focused on, 'What is stopping us from being more valuable?' or 'How can our workflow be enhanced?'

176

参考回答

I use easy-to-understand visual reports like Burndown or Burnup Charts, along with a high-level overview of achieved milestones and upcoming goals. Regular updates ensure stakeholders are well-informed of the project status.

177

参考回答

There are three scrum artifacts: - Product Backlog: The product backlog includes all the items that will be delivered for the product. This list is constantly evolving. The commitment to the product backlog is the product goal. - Sprint Backlog: Sprint backlog is a list of all items committed to being delivered within a sprint. Once decided, the sprint backlog cannot be changed. The commitment of the sprint backlog is the sprint goal. - Product Increment: Product increment is usually delivered at the end of the sprint, which is a workable increment of the overall product.

178

参考回答

A well-crafted Sprint backlog includes the selected Product Backlog items, a clear Sprint goal, and a plan for delivering them, often broken down into tasks. It is created collaboratively by the team decomposing the work, estimating effort, and identifying dependencies.

179

参考回答

Some of the main artifacts of the Scrum process include product backlog, velocity chart, sprint backlog, burndown chart, and product increment.

180

参考回答

This could be considered something of a trick question, though you should know this if you're interviewing for a Scrum Master role. Scrum is part of the Agile philosophy, which has its own principles and values (as does Scrum). Essentially, Scrum is a framework that helps teams deliver value in a short period. So, while Scrum and Agile differ, they are part of the same methodology.

181

参考回答

The Program Board visualizes the plan for multiple teams over several sprints. It highlights features, milestones, dependencies, and risks, providing a macro-level view to ensure alignment and coordination across teams.

182

参考回答

Waterfall over Scrum is used in the following scenarios: - Well-Defined Requirements: Waterfall is suitable for projects with well-defined and stable requirements from the start. This approach ensures that all stakeholders are clear about what needs to be done and when, reducing the likelihood of changes during the project lifecycle. - Predictability and Control: Waterfall provides a high degree of predictability and control, making it ideal for projects where the scope, timeline, and budget must be tightly managed. This is particularly beneficial in industries like construction, manufacturing, or government projects where costly changes are undesirable. - Sequential Workflow: Projects that naturally follow a linear sequence, such as those with distinct phases that cannot overlap, benefit from Waterfall. Each phase must be completed before moving on to the next, ensuring a structured progression. - Low Flexibility Needs: Waterfall's linear approach can be more efficient if the project does not require frequent changes or adaptations. This is because it minimizes the need for iterative feedback loops and allows for a more straightforward development process. - Large Teams or Established Processes: Waterfall can be advantageous for large teams or when working with an established DevOps stack. It helps manage complexity by maintaining a structured workflow and clear roles, which is beneficial in environments where flexibility is not a priority. - Regulatory or Compliance Projects: In sectors with strict regulatory requirements, such as banking or healthcare, Waterfall's structured approach ensures compliance and reduces the risk of non-compliance due to changes in project scope.

183

参考回答

Success metrics typically include achievement of release goals, customer satisfaction, quality metrics (like defect rates), and business impact (like revenue growth or market penetration).

184

参考回答

I had a senior engineer who thought daily stand-ups were a waste of time. He said, ‘I'm spending 15 minutes a day on a meeting when I could be coding.' Instead of dismissing him, I said, ‘That's a fair concern. Let's try something—let's run the stand-up for two weeks exactly as you'd run it, then let's see if the team prefers it.' Turns out his version was even faster but less connective—people didn't hear about blockers until they were huge problems. I asked him, ‘What if we kept your efficiency but added back the blocker discussion?' We modified it, and he became a stand-up advocate. The point is, I listened to the skepticism, tested it, and we found a compromise. If I'd just told him ‘Agile says we do stand-ups,' I'd have lost him.

185

参考回答

When there is a problem in the scrum team, I act fast to sort it out. This helps to keep everyone happy and working well. As a facilitator, I guide the team to fix the issue on their own. I feel that when handled right, some conflict can help people get creative and feel closer to each other. I start by watching and listening to what is going on so I know what everyone thinks. I ask the people to talk with each other in a calm and open way. If things do not get better, I will set up a meeting and help them find common ground. My conflict resolution process includes: - Meeting with people one-on-one to get their views. - Leading a group talk for a set time that looks at facts and what the group wants to reach. - Making team rules about what to do when they do not agree in the future.

186

参考回答

Any user story is prioritised according to the market value (commercial value), necessity, and dependencies, and they are estimated using user story points. These story points measure the efforts, complexity and uncertainty in a project. Prioritisation of user stories happens when the product owner and stakeholders collaborate to deliver value by working on priority tasks. On the other hand, estimating user stories comes under agile practice, where the developers use a measuring metric like story points to assess efforts, complexity and risks (also known as uncertainties). This helps the team to compare stories easily.

187

参考回答

A well-written user story should follow the INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, and Testable.

188

参考回答

I consider the team's current situation and needs. For example, if the team is facing specific challenges, I might choose the “Fishbone Analysis” to dive deep into root causes.

189

参考回答

There are 3 fundamental roles in Scrum: Product Owner: The product owner is an individual who is responsible for increasing the ROI by determining product features, prioritizing these features into a list, what needs to be focused on the upcoming sprint, and much more. These are constantly re-prioritized and refined. Scrum Master: This individual helps the team in learning to apply Scrum to ensure optimum business value. The scrum master removes impediments, shields the team from distractions, and enables them to adopt agile practices. Scrum Team: They are a collection of individuals who work together to ensure that the requirements of the stakeholders are delivered.

190

参考回答

Addressing technical debt is a continuous process. I advocate for allocating time in each Sprint to refactor code, update documentation, and improve existing features. This ensures technical debt is managed proactively.

191

参考回答

- Product Backlog: It is a list that comprises of latest features, variations to features, bug fixes, conversions to the infrastructure, and other activities to guarantee a particular output to achieve. - Sprint Backlog: It is a division of the product backlog that covers tasks engrossed on by the team to fulfill the sprint goal. Teams primarily identify the tasks to be finalized from the product backlog. These are then further added to the sprint backlog. - Product Increment: It is a blend of all product backlog items accomplished in a sprint and the value of earlier sprints increments. The output must be in a functional state, even if the product owner doesn't issue it.

192

参考回答

With this Scrum Master interview question, you're testing your candidates' knowledge of Scrum events. It also gives you a subtle insight into their style as a Scrum Master. Listen for: One of four different events that take place during the Scrum process. It can be sprint planning, daily scrum, sprint review or sprint retrospectives. Your candidate should be able to elaborate on which event they prefer and why.

193

参考回答

We have heard of the Scrum team as a dedicated team of experts, where people performing distinct tasks come together and aim towards delivering a consumer-friendly product. They manage work in short sprints (which are brief iterations), where a team accomplishes a set of designated tasks. But, mainly, there are three roles in Scrum, including that of a - - Product Owner - The product owner is the one who conveys customer requirements to the scrum team after careful evaluation. He is the one responsible for communicating the customers' voice to the developer so they can curate a suitable product for their needs. The product owner interprets the value of the product and the company's vision to ensure the team delivers maximum product value by fulfilling the product backlog items. - Scrum Master - The role of a scrum master is to guide the scrum team towards the accomplishment of goals. They oversee everything happening within the team, right from the day-to-day tasks handled by the team members and ensure there are no obstacles along the way. Precisely, a scrum master leads the scrum team. He is responsible for upholding the Scrum values, principles, and protocols within and outside the team to ensure an in-depth understanding of Scrum concepts. - Developers - The developers or the development team are the ones responsible for the design, buildout, and delivery of the product. Then there are quality analysts who conduct final checks on the curated products before they are released to the audience. This is the core team behind the entire development process of the product, and also the one that ensures successful product delivery. The key members of this cross-functional development team are many, from design architects to developers, DevOps engineers to UI/UX designers, etc.

194

参考回答

The ideal candidate should understand the company's mission, values, and objectives, aligning their skills and experiences accordingly. They should offer specific examples demonstrating how their background and expertise complement the company's needs and contribute to its success. Additionally, a good fit entails enthusiasm for the company's culture and a genuine interest in its industry, ensuring long-term commitment and collaboration toward shared goals.

195

参考回答

Use data, storytelling, and stakeholder empathy to align Agile with business outcomes.

196

参考回答

These tools ensure transparency, streamline processes, and enhance productivity in Scrum projects, helping teams stay aligned and deliver high-quality results efficiently. - Jira and Trello help with backlog management and sprint planning. - Azure DevOps and ClickUp offer integrated tracking for development teams. - Slack and Microsoft Teams enhance communication. - Confluence is used for documentation and knowledge sharing. - Miro and MURAL support virtual brainstorming and Sprint Retrospectives. - VersionOne and Targetprocess are enterprise-level Agile tools. - GitHub and GitLab assist in code collaboration.

197

参考回答

I facilitate a discussion among the stakeholders to understand their perspectives and priorities. The aim is to find a compromise or a solution that aligns with the project's goals and delivers the most value.

198

参考回答

Ensuring a focus on quality assurance and testing involves embedding these practices throughout the development process. I work closely with the team to establish clear acceptance criteria for user stories during sprint planning. Continuous collaboration with the Quality Assurance (QA) team ensures that testing activities are integrated seamlessly into the development workflow. Additionally, I advocate for automated testing and provide resources or training to team members to enhance their testing skills. By emphasizing the importance of quality assurance from the inception of a user story to its delivery, we create a culture that prioritizes testing and consistently delivers high-quality increments.

199

参考回答

There are three main artifacts in SCRUM: - Product Backlog - Sprint Backlog - Product Increment

200

参考回答

Pros: Improves team communication and transparency, helps identify blockers early, fosters accountability, and aligns the team on daily goals. Cons: Can become a status report rather than a planning session, may be too rigid for remote teams, and can waste time if not facilitated properly or if the team is large.