1

参考回答

- Card – The written story. - Conversation – Discussion about details. - Confirmation – Acceptance criteria.

2

参考回答

All meetings are equally important. What we are looking for here is their understanding of the ceremonies. Significant hesitation, not remembering the titles, and/or getting the meetings mixed up are negatives.

3

参考回答

The primary Scrum artefacts include product backlog, sprint backlog, and product increment. Additionally, experts refer to velocity charts and burndown charts as the last two Scrum artefacts, which are not considered as important as the first three. Scrum artefacts can be defined as the core information tools in the Agile Scrum framework that ensure transparency in work, help measure progress and provide product details to the stakeholders as well as the entire scrum team, so that everyone can have a clear understanding of the concept. We have provided a brief explanation of the Scrum artefacts right below: - Product Backlog - The product backlog is a structured list of priority items (or tasks) prepared for the development team to deliver the final product. This list acts as a detailed document that sequentially displays the tasks based on their priority (i.e. as per the timeline defined for it). - Sprint Backlog - The set of tasks that the Scrum team agrees to deliver within a predefined period (which we refer to as a sprint, that lasts for about 3 to 4 weeks) is known as the Sprint Backlog. The sprint backlog is nothing but a dashboard displaying four aspects of the tasks that the team is working on, and shows up as statuses like “To Do”, “Ongoing”, “To Be Reviewed” and “Done”, each of which defines the work update. - Product Increment - In simple terms, product increment is the current model of the product built by the development team, plus whatever new features the team completed in the previous sprint. Effective integration of both the developments and the final evaluation of the designed product is referred to as a product increment. This is an accessible version of the designed product that is released for the audience evaluation. - Velocity Chart - The velocity chart is not considered to be an official Scrum artefact. This is why most resources do not mention it in the list of Scrum artefacts. But to understand what velocity charts are, one has to know that these are popular extended metrics that measure the amount of work done, and additionally assist the scrum teams to keep a check on the work progress and help plan future sprints. - Burndown Chart - The burndown chart is also not officially counted as a Scrum artefact, but it remains a widely used tool and an extended artefact that helps teams to visualise the development the team members have made towards the ultimate sprint goal. Through this chart, one can easily track the pending work, discover concern areas to discuss and etch out a plan to fulfil future tasks.

4

参考回答

The candidate should suggest facilitating retrospectives to identify blockers, breaking action items into smaller tasks, setting clear owners and deadlines, using visual tracking tools, and holding the team accountable through regular check-ins to ensure follow-through and continuous improvement.

5

参考回答

Addressing requests for alterations from external stakeholders beyond the boundaries of the ongoing sprint requires an open and cooperative approach. It is crucial to initiate dialogue and communicate with the stakeholders to understand the urgency and need for requested modifications. The alterations should align with the overarching project objective and not risk the current sprint's aims; collaborate with the product owner to validate the feasibility of their integration. However, if these modifications pose a risk to the sprint's objective or necessitate a significant reprioritization, advise the stakeholders to prioritize their requests for future sprints. Balancing flexibility while maintaining the team's focus on delivering a cohesive increment during each sprint is crucial.

6

参考回答

Yes, the Scrum Team can participate in product discovery by collaborating with the Product Owner to explore user needs, validate ideas, and contribute insights. The team's technical knowledge helps ensure that product discovery aligns with both user needs and technical feasibility.

7

参考回答

The team collectively performs estimation in a Scrum project during the sprint planning meeting, using relative Agile estimation techniques. Estimation techniques commonly used include: [not explicitly listed in the text, but implied from context]

8

参考回答

- Prioritize Issues – Identify key problems from the retrospective. - Define Action Items – Assign responsibility for each improvement. - Track Progress – Monitor changes in subsequent sprints. - Iterate – Adjust based on results in future retrospectives.

9

参考回答

The acronym INVEST stands for Invest, Negotiate, Valuable, Estimable, Small, and Testable. It is a guide to writing good user stories.

10

参考回答

Common challenges I've faced include resistance to change, lack of Agile understanding, and command-and-control leadership styles. I addressed these through continuous coaching, small wins, and by demonstrating tangible improvements in predictability and team morale. Building trust and patience was key to long-term adoption.

11

参考回答

I wouldn't assume the issue is the person's fault right away. My first move is to have a one-on-one conversation in a supportive way—not accusatory. I might say, ‘I've noticed your completed work has been lower than expected the last two sprints. What's getting in the way?' Often, you find out they're being pulled into meetings, they don't have the right tools, or they're unclear about expectations. I also look at team velocity metrics to see if it's just this person or if the whole team is struggling. In one case, I realized a developer was spending 40% of their time in unplanned support requests. We worked with the Product Owner to protect two days per sprint for that, and their sprint commitments immediately became realistic. It's rarely a motivation problem—usually it's a systems problem.

12

参考回答

I facilitate Scrum ceremonies by ensuring they are well-planned and time-boxed, using techniques like setting clear agendas and rotating facilitators to keep the team engaged. I also encourage open communication and active participation to make sure everyone's voice is heard.

13

参考回答

The sprint retrospective is both a time to analyze and change the process and an opportunity to reflect on it. Attendance by the entire Scrum team is required. This includes the Scrum Master, the product owner, and all members of the development team (including everyone who is designing, building, and testing the product). However, other teams may not want to include the product owner since it will obstruct their discussion. If there is a lack of trust between the product owner and the development team, or a lack of safety that prevents the product owner from speaking candidly, the product owner should not attend until the Scrum Master can help teach those engaged in building a safer, more trusting atmosphere. Anyone not on the immediate scrum team, especially team members' managers, should not be invited to participate.

14

参考回答

Product Backlog is the complete list of everything the product needs long term, no deadline attached. Release Backlog is a subset items you've committed to delivering in a specific release or timeframe. Think of Product Backlog as your full wishlist. Release Backlog is what's going into the next shipment. Not all teams use a Release Backlog explicitly, but in larger programs it helps manage stakeholder expectations clearly.

15

参考回答

| Product Backlog | Sprint Backlog | | For completion of product development, we need a list of products | It is a list of items to be completed in each Sprint | | Product owner collects backlog from the customer and assigns it to the team | The backlog is collected from the product owner and set up the time frame | | The specific end goal is there | It is specific to a Sprint | | It is based on customer vision | It is based on customer vision which is defined by the product owner | | It is independent of the sprint backlog | It is dependent on the product backlog | | Till the project completion, the product backlog is maintained | Each new sprint has backlogs added by the teams |

16

参考回答

In my last role, two developers had a fundamental disagreement about whether to refactor technical debt or build new features. The tension was affecting the whole team's energy. I first met with each of them individually to understand their perspective—one was worried we were building on shaky ground, the other wanted to move faster for customers. Then I set up a conversation with both of them together, and I asked them to present their concerns to the product owner and the team without arguing about implementation details. It turned out they weren't actually disagreeing on the end goal; they just had different timelines in mind. We ended up proposing a hybrid approach to the PO: spend one sprint on critical refactoring, then build the next feature on that cleaner foundation. Both developers felt heard, the team got clarity, and we found a path forward.

17

参考回答

To employ a practical approach engaging a team To optimize predictability with skills and expertise acquired by the people To control risk in the work

18

参考回答

The Sprint Review emphasizes the product, whereas the Sprint Retrospective evaluates the process. Sprint Review focuses on enhancing and getting the most out of product value, whereas Sprint Retrospective focuses on addressing people, processes, and tools.

19

参考回答

During a Scrum daily (or stand-up) meeting, Scrum Masters ask team members: - What did you do yesterday? - What do you plan to do today? - What is stopping us from achieving today's goals? Asking and answering these questions is crucial to help the Scrum team focus. Icebreakers questions and ice breakers games can help to energize teams at the start of meetings.

20

参考回答

A storyboard in Scrum ensures transparency throughout the process. It is a visual representation of the progress of a software project, with four columns: “To-do,” “In-progress,” “Test,” and “Done.”

21

参考回答

I prioritize the backlog with the Product Owner, use labels and filters for organization, and regularly refine user stories to ensure clarity and readiness for upcoming sprints.

22

参考回答

An Increment is the sum of all completed Product Backlog items in a Sprint that meets the Definition of Done and is potentially releasable.

23

参考回答

Daily standup is a brief meeting that takes place daily and lasts for about 15 minutes. The purpose of this discussion is to share daily task updates with the team and stay informed on the work status and the progress made by the team on the previous day or during a specific duration. The agenda behind conducting daily standups is to evaluate the completed tasks, the yet-to-be-completed tasks and resolve any issues stated by the team. There are various ways of conducting daily standups - it can be done over a short break, formally or informally, or even through Zoom meetings or conference calls, if the members are operating from different locations.

24

参考回答

I would first have a conversation with the Product Owner to grasp what is making them want to introduce changes; is it stakeholder influence? Updated information about the competitors? Or is it unclear communication concerning the impacts of making changes mid-sprint? Then, I would explain to them the cost associated with context switching and how changes in the middle of Sprints can affect the team's velocity and morale. I may use data to support this point. For situations that would be considered true emergencies, we would develop a change proposal process, perhaps by immediately substituting a lower priority item of comparable size. For important but non-urgent proposals, we would move these to the top of the Product Backlog for scheduling in the next Sprint. Alongside that, I would work with the team to refine processes around managing stakeholder interactions, such as providing the Product Owner with frequent project demos or progress summaries. Fostering that trust may help relieve some of the pressure to change things in the middle of the Sprint.

25

参考回答

Scrum is an Agile framework that helps teams develop products in short, iterative cycles called sprints. It focuses on collaboration, flexibility, and delivering value quickly. The key roles in Scrum are the Scrum Master, Product Owner, and the Scrum Team. The Scrum process involves regular meetings and reviews to ensure the team stays on track and delivers high-quality work. CSM Training is essential for anyone looking to become a certified Scrum Master and help teams adopt Agile practices effectively.

26

参考回答

Yes, the origin of Scrum as a method was used to facilitate the software development process.

27

参考回答

Not necessarily. While regularity in timing and location reduces logistical complexity, the presence of the Scrum Master and product owner is optional unless they are part of the development team. The Daily Scrum is primarily for the development team, emphasizing accountability and commitment rather than serving as a management reporting mechanism.

28

参考回答

The Definition of Done is a shared agreement that defines what it means for a Product Backlog item to be fully complete. It ensures every increment meets a consistent quality standard before being considered shippable. A weak Definition of Done leads to hidden work, technical debt, and quality issues that compound over time.

29

参考回答

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

30

参考回答

Identifies improvements to be implemented in the next Sprint.

31

参考回答

Our team was getting blocked constantly by another department that owned the API we needed to integrate with. They had a three-month backlog, and our team couldn't move forward. I realized the two teams didn't have visibility into each other's work. I suggested we set up a weekly sync where both teams showed what they were working on and flagged dependencies early. I also worked with both managers to prioritize the API work our team needed. Turns out the other team didn't even realize how much we depended on them—it was just buried in a generic backlog. After we created that visibility and prioritized the dependency, they turned around the work in three weeks instead of three months. The teams actually started collaborating more, and we released the feature without the delay.

32

参考回答

If the team struggles with the workload, I work with the Product Owner to reassess priorities and possibly defer less critical items to ensure the most valuable work is addressed without overwhelming the team.

33

参考回答

Teams implementing the Scrum methodology can benefit significantly. It promotes adaptability, is open to continuous improvement with regular feedback from customers, encourages effective collaboration among the team members, maintains transparency by supporting open communication with team heads, supervisors, as well as subordinates, and promises prompt delivery of products, with minimal scope of flaws.

34

参考回答

The candidate should state that they would not mark the story as done if defects exist. They would discuss options with the team, such as fixing critical defects within the sprint if possible, deferring the story to the next sprint, or negotiating with the Product Owner on the definition of done, emphasizing the importance of quality and transparency.

35

参考回答

The 15 10 5 rule in Scrum is a time-management technique used primarily during daily stand-up meetings. It suggests the following breakdown: - 15 minutes total for the meeting - 10 minutes for team members to update on their progress (what was done yesterday, what will be done today) - 5 minutes to address any impediments or blockers This rule ensures that the meeting remains concise and focused while allowing enough time for critical discussions without dragging on, keeping productivity high and disruption to a minimum.

36

参考回答

A user story in Scrum is a non-technical description of a feature from the end user's perspective. It communicates how the software's features benefit users and initiates stakeholder communication. User stories prioritize people in Agile development, emphasizing the importance of understanding and meeting user needs.

37

参考回答

I have experience using Scrum tools like Jira, Trello, and Asana. These tools help manage the Product Backlog, Sprint Backlog, and other Scrum artifacts. They also enable the team to track progress and ensure transparency throughout the sprint.

38

参考回答

Scope creep describes how a project's requirements tend to grow over time, such as when a single deliverable product gets split into five or when a product with three essential features needs ten essential features or when the customer's needs change midway through a project, prompting a reassessment of the project requirements. Scope creep is frequently caused by changes in project requirements from key stakeholders, as well as internal miscommunication and conflicts. Controlling scope creep through a change control procedure is the key to managing scope creep. This entails: - Keeping track of the project's progress and establishing a baseline scope - Using variance analysis to compare actual work performance metrics to the baseline scope, i.e., "How different is the present project from the initial plan?" - Identifying the source and severity of the observed changes - Choosing whether corrective or preventive action is required in response to change requests - Using the Perform Integrated Change Control procedure, manage all change requests and recommended actions (whether corrective or preventive).

39

参考回答

Burndown charts show how much work is left to do in a sprint or project over time, typically tracking the remaining effort. Burn-up charts, on the other hand, track how much work has been completed, showing the total work done as the project progresses.

40

参考回答

A consensus-based estimation technique where team members assign story points using cards.

41

参考回答

My experience includes implementing practices like Continuous Integration, Refactoring, Small Releases, and Sustainable Pace. These practices help in improving software quality and team productivity.

42

参考回答

Scrum Masters play a veritable role in development and deployment of Software Projects. The need for Scrum Master is soaring high in the market with the evolution of Scrum Framework into much use. The prerequisites and responsibilities of a Scrum Master are very broad. From managing the team and leading them to being an interface between the product owner and development team, the roles of Scrum Master needs to be configured and analysed very carefully. To get yourself recognized as a good and expert Scrum Master one needs to get trained at first. Scrum Framework is a lightweight model but to master the model always remains a tough task to do. And so for the same one needs to get trained under an expert hand who delivers the exact concepts of Scrum Framework into use for the working process. The trainers take you through every insight of how to deploy the principles of Scrum Framework into use. This includes covering all the activities and information needed for the role of Scrum Master with the depth knowledge of every section and stages. And so for the same getting yourself certified is a must need. The certification of Scrum Master gives a detailed view of the structure and working of the Scrum Framework. It helps the Scrum Master to manage the team accordingly and deliver results of high-quality value. Learning every single step under Scrum Certification course helps the Scrum Master to react to the blockages and backlogs very quickly and get this things resolved at an efficient pace. With the growth and success of Scrum Framework into the working environment of Software industry with time, outlook and reach for Scrum Master has grown exponentially with time and demand for Scrum Masters are soaring high with the time.

43

参考回答

The Scrum master, as everyone knows, is responsible for instructing and coaching the Scrum team about Scrum and Agile principles, and is additionally accountable for facilitating Scrum events and ensuring improvements, integrating practices, establishing a collaborative workplace culture and eliminating blockers, so that the team can deliver value in every sprint. To ascertain that the scrum team is properly trained, the scrum masters walk an extra mile to foster a sense of ownership within the team members, so they can proactively participate in the development process, yield effective results, and confidently take things ahead to ensure the continual growth of the company.

44

参考回答

Risks are prioritized based on their probability and potential impact on the project's success. High-impact, high-probability risks are addressed first. I involve the team in this prioritization to ensure we focus on the most critical threats.

45

参考回答

I ensure it by acting as a servant leader and coach rather than an authority figure. I create awareness by explaining the why behind Scrum best practices, facilitate open discussions during events, and guide the team to self-correct when deviations occur. My key is to use coaching, feedback, and retrospectives to help the team understand the value of Scrum and take ownership of following it.

46

参考回答

After a retrospective, I ensure that action items are clear, assigned to the right people, and tracked throughout the sprint. I follow up during daily stand-ups and monitor progress, making sure the team stays accountable and continuously improves on the points discussed.

47

参考回答

A scrum is a group of people, working for achieving the product goal, called the Scrum Team. Though there are no hierarchy or sub-teams, the Scrum Team consists of - One Scrum Master - One Product Owner - Developers

48

参考回答

A Scrum anti-pattern is behavior that undermines Agile principles, such as skipping retrospectives or mid-Sprint scope changes.

49

参考回答

Through disciplined inspection and adaptation: - Strong retrospectives - Action item tracking - Metrics review - Coaching conversations - Safe experimentation

50

参考回答

A scrum master interviewee should describe Scrum as an Agile framework designed to add structure and efficiency to software creation. They would emphasize how Scrum facilitates continuous improvement and collaboration through its prescribed roles and meetings, ensuring that each sprint delivers enhancements that drive business value.

51

参考回答

The candidate should explain that this approach may bypass essential Scrum practices like user story refinement and collaboration. They would recommend involving the team in writing user stories, ensuring they are well-defined with acceptance criteria, and having the Product Owner prioritize based on value rather than directly converting documents into tickets.

52

参考回答

Before we answer this question and explain how Scrum teams handle dependencies, let us first talk about what a “dependency” refers to in a Scrum team. Dependency is a situation in which a team or an individual is dependent on another for an output or action before they can proceed to the next step. Dependencies can be of different types - technical, sequential, external, or resource-based. The reason that makes dependencies a point of concern in Scrum is that they end up causing blockers, obstructions, and obstacles in the process.

53

参考回答

I map out dependencies early in the planning phase and continuously monitor them throughout the release cycle. Effective communication with teams handling dependent tasks is crucial to manage these dependencies proactively.

54

参考回答

I track Sprint progress by using tools like Burn-down charts, which visually show the remaining work versus time. I also monitor team velocity, sprint goals, and any impediments that might arise, ensuring the team stays on track and delivers value by the end of the sprint.

55

参考回答

The amount of work performed by a team during a sprint is measured by velocity. It refers to the number of user stories that have been finished in a sprint. No, having maximum Velocity does not ensure maximum Productivity. A team's attempt to enhance velocity may actually result in the reverse. If pressed for time, a team may forgo unit or acceptance testing, reduce customer collaboration, forgo issue fixes, minimize refactoring, and many other critical benefits of the agile development approach. While there may be a short-term benefit, there will be a long-term detrimental consequence. The goal is to achieve optimal velocity over time, which takes into account a variety of parameters, including the end product's quality.

56

参考回答

The 12 Agile principles support the Agile values and emphasize: - Early and continuous delivery - Welcoming changing requirements - Frequent collaboration - Technical excellence - Simplicity - Self-organizing teams Understanding these principles is critical in Agile Scrum interviews.

57

参考回答

Some pointers to be considered when handling the scope of change when new requirements arise. Handling Scope Changes or Feature Additions During a Sprint: [not explicitly listed in the text, but implied from context]

58

参考回答

Scrum, like any methodology, presents several challenges that teams may encounter: [not explicitly listed in the text, but implied from context]

59

参考回答

- Cross-functional - Self-organizing - Collaborative

60

参考回答

The candidate should describe metrics such as velocity, burndown charts, cumulative flow diagrams, and cycle time, and explain how they use these to monitor sprint progress.

61

参考回答

Situation: The team was demotivated due to a previous project failure. Action: Organized team-building activities and provided positive reinforcement. Result: Boosted morale and regained team confidence, leading to improved performance in subsequent projects.

62

参考回答

When listening to the answers, look for signs of candidates' ability to empathize with others. Good responses will show the candidate's ability to understand others' perspectives, resolve conflicts, and balance team needs with stakeholders' demands.

63

参考回答

I've managed up to three Scrum teams simultaneously. The main challenges include ensuring alignment between teams, managing cross-team dependencies, and maintaining clear communication. I overcame these by organizing Scrum of Scrums meetings and ensuring teams were aligned on goals and priorities.

64

参考回答

As a Scrum Master, you are responsible for facilitating the Scrum process, ensuring the team follows Scrum practices, removing obstacles, and helping the team improve continuously. You act as a shield between the team and external disruptions to ensure the team's focus remains intact. For those in Noida, CSM Training in Noida offers a comprehensive learning experience with practical insights into Scrum processes.

65

参考回答

Any Scrum team member can write the user stories. The team discusses the requirements during the primary stages and translates them into user stories. With the collective contribution of the team members, the requirements are clearly defined.

66

参考回答

Ensuring the Scrum team remains aware of and responsive to industry or market trends involves ongoing communication and a commitment to continuous learning. I establish channels for the team to access relevant industry news, research, and market updates. Additionally, I encourage team members to participate in conferences, webinars, or industry events to stay informed about emerging trends. During retrospective meetings, we discuss how industry changes may impact our product and adjust our strategies accordingly. By fostering a culture of curiosity, continuous learning, and proactive adaptation, we enable the Scrum team to stay ahead of industry developments and align our work with evolving market trends.

67

参考回答

In a past project, during a demo, a stakeholder pointed out that a new feature's user flow was confusing. This feedback led the team to redesign the interface in the next Sprint, resulting in a significant increase in user adoption and satisfaction.

68

参考回答

To ensure the Scrum team remains focused on delivering user value, ongoing alignment with the product vision and priorities is essential. Product owners prioritize user stories based on their business value, ensuring that the most impactful features are addressed first. The team maintains a disciplined approach to delivering value by adhering to the Scrum methodology.

69

参考回答

In simplest terms, Scrum is a type of project management utilized in software development, marketing, and other fields. A team practicing Scrum will chop up a project into smaller components and then attempt to complete those components in short periods, known as "sprints." The Scrum master is tasked with helping the team execute scrum concepts and complete their sprints as effectively as possible.

70

参考回答

Situation: Faced with a critical bug just before a major release. Action: Had to decide between delaying the release or proceeding with known issues. Result: Chose to delay the release to maintain product quality, which was ultimately well-received by the stakeholders.

71

参考回答

Retrospectives are where the team has permission to say ‘things aren't working' and actually fix them. Without them, bad habits just calcify. I make sure retros are psychologically safe—people need to know they won't be punished for saying something didn't go well. I do this by never having managers attend unless the team explicitly asks them to, by asking questions instead of making accusations, and by making sure we actually implement changes. Too many teams have retros where nothing changes, and then they stop caring. I try to keep the format fresh—sometimes it's Start-Stop-Continue, sometimes it's a sailboat activity, sometimes it's just conversation. The variety keeps people engaged. And I always make sure we close the loop in the next retro on what happened with last sprint's action items.

72

参考回答

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.

73

参考回答

No, but they facilitate and coach the team without direct authority.

74

参考回答

The Program Board is updated regularly, often after each Sprint Review. It's a collaborative effort involving Scrum Masters and Product Owners to ensure it accurately reflects current progress and future plans.

75

参考回答

Getting a Scrum Master Certification helps ensure you understand Scrum practices, tools, and techniques. A Certification boosts your credibility and demonstrates your commitment to following Scrum principles.

76

参考回答

Expect scrum master candidates to mention how they track progress through user stories, action items, and acceptance criteria. They should discuss conducting retrospective meetings and sprint reviews to evaluate the teamâs performance and set action items for the next sprint. Candidates might also highlight how they balance soft skills and technical expertise to foster an environment aligned with the Agile Manifesto and Scrum guide.

77

参考回答

Risks and dependencies are visually marked on the board. This helps in identifying potential issues early on. Regular reviews of the board allow for timely risk mitigation and dependency resolution strategies.

78

参考回答

The candidate should list frameworks such as Scrum, Kanban, Lean, Extreme Programming (XP), SAFe (Scaled Agile Framework), and possibly others like Crystal or DSDM. They should also demonstrate understanding of the differences and appropriate contexts for each.

79

参考回答

Scrum is a framework designed to help the team work together in an incremental and iterative approach. The entire scrum process is organized into cycles called sprints. It enables the team to work on problems, make improvements, and learn from their experience.

80

参考回答

In Scrum, the Product Owner is responsible for prioritizing tasks based on the value they bring to the business. As a Scrum Master, I ensure that the team focuses on the highest-priority tasks first and that we address any blockers preventing progress. Practicing scrum interview questions can help you demonstrate your problem-solving skills and your ability to lead Scrum teams effectively.

81

参考回答

I document the action items and assign owners during the retrospective. The team reviews these action items at the start of the next retrospective to track progress. I also integrate the improvements into the team's working agreements to ensure they are sustained.

82

参考回答

A sprint is a time-boxed period that spans between 1 to 4 weeks in Agile/Scrum development. Here, teams work to complete a specific set of prioritized tasks, aiming to produce a potentially releasable product increment.

83

参考回答

This is a great opportunity to show you understand the business value of the Scrum Master role. Agile helps businesses satisfy customers with useful software delivered quickly. It continually results in products that work; nurturing close cooperation between a business and the product developers, and helping to encourage self-motivation among teams.

84

参考回答

Common estimation techniques in Scrum projects include: - Estimation by Analogy - T-shirt Estimation - Planning Poker Estimation - Disaggregation Estimation.

85

参考回答

I conduct training sessions on Kanban principles and engage the team in setting up their Kanban board and WIP limits, ensuring they understand and buy into the process for a smoother transition.

86

参考回答

Scope creep refers to gradually expanding a project's requirements beyond its initial boundaries. This can include breaking down deliverables into smaller parts, increasing the required features, or reevaluating project requirements due to shifting user needs mid-project. It often stems from changes in stakeholder requirements, internal miscommunications, or conflicts. To manage scope creep effectively, implement a change control procedure to maintain control over the project's scope. This procedure typically includes the following steps: [not explicitly listed in the text, but implied from context]

87

参考回答

One challenge is ensuring meetings are efficient and focused. I addressed this by setting clear agendas, focusing on discussion points relevant to all teams, and encouraging pre-meeting preparation.

88

参考回答

One of the drawbacks of using scrum is that the daily meeting and frequent reviews require substantial resources and continuous changes.

89

参考回答

The five Scrum events are Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective, and the Sprint itself. These events help teams work together, keep getting better, and make sure they keep moving forward. The events help everyone in the development process to stay focused and in line with their goals.

90

参考回答

The Definition of Done (DoD) is a shared understanding within the team of what it means for a task to be considered complete. This includes criteria like code being written, tested, reviewed, and documented. It ensures that everyone has the same understanding and prevents incomplete work from being considered "done." Certified Scrum Master Training in Gurgaon helps you learn the skills you need to become a great Scrum Master and succeed in Agile projects.

91

参考回答

I avoid blaming individuals and focus on systemic issues. I analyze Sprint data, capacity planning, dependencies, and backlog quality. In retrospectives, I facilitate honest conversations to identify root causes. Often the solution involves better backlog refinement, realistic forecasting, or reducing external interruptions.

92

参考回答

Sprint Planning is a time-boxed event at the start of each sprint. The whole Scrum Team participates. It answers two questions: What can be delivered in the upcoming sprint? and How will the chosen work get done? The output is a Sprint Goal and a Sprint Backlog. The time box is a maximum of eight hours for a one-month sprint, proportionally shorter for shorter sprints.

93

参考回答

I ensure engagement by involving the entire team in estimating and task breakdown. I use techniques like round-robin to get input from quieter members and ask open-ended questions to stimulate discussion. I also make sure the Product Owner is present to clarify requirements.

94

参考回答

User story mapping is a technique for organizing user stories into a visual map that reflects the user journey rather than a flat prioritized list. The map has two dimensions: the horizontal axis represents the steps in the user journey, and the vertical axis represents priority. It helps teams identify which stories are essential for a minimum viable release versus which add value later. It also makes dependencies and gaps in the user journey visible before sprint planning begins.

95

参考回答

A Release Candidate (RC) is a software version nearly ready for production. It has passed internal testing and is considered stable, but final checks or minor adjustments may still be required before public release.

96

参考回答

The biggest challenges often include resistance to change, lack of understanding of Agile principles, and adapting existing processes to Agile. Addressing these requires targeted training, management buy-in, and showcasing the benefits of Agile.

97

参考回答

We document the action items and assign ownership. In subsequent Retrospectives, we review the status of these items to ensure continuous improvement.

98

参考回答

Facilitate backlog refinement, team alignment workshops, and revisit Product Goal.

99

参考回答

Scrum is an Agile framework designed to help teams work together more effectively. It consists of key roles like the Scrum Master, Product Owner, and Development Team, as well as events such as Sprints, Daily Stand-ups, and Retrospectives. These components work in harmony to ensure continuous improvement and delivery of high-quality products.

100

参考回答

You can sum up the definition of Scrum as 'A framework that helps people, teams, and organizations generate value and address adaptive challenges.'

101

参考回答

Planning Poker is a consensus-based estimation technique. Team members use cards with Story Points to estimate items. It's effective because it involves the entire team, encourages discussion, and leads to a shared understanding of the work.

102

参考回答

I use the Sprint Review as the primary vehicle for communicating progress. I also share transparent information radiators like burndown charts and task boards. I ensure that communication is honest, highlighting both successes and challenges.

103

参考回答

Scrum poker is a method to evaluate the relative size of development goals in the software development process.

104

参考回答

Yes, but the Sprint Goal must remain intact.

105

参考回答

Addressing resistance from other departments or stakeholders involves a diplomatic and collaborative approach. I initiate conversations to understand their concerns, providing education on the benefits of Scrum and how it aligns with agile principles. I emphasize the value of collaboration and highlight successful outcomes achieved through Scrum practices. If specific concerns or misconceptions persist, I work collaboratively to find solutions and address their needs while maintaining adherence to Scrum principles. By actively engaging with stakeholders, building understanding, and finding common ground, we create an environment where the Scrum team can work collaboratively with other departments for mutual success.

106

参考回答

Risk management is a sequence of steps that help a software team to understand, analyze, and manage uncertainty. Risk management process consists of - Risks Identification: Risk identification refers to the systematic process of recognizing and evaluating potential threats or hazards that could negatively impact an organization, its operations, or its workforce - Risk Analysis: Risk analysis is the process of evaluating and understanding the potential impact and likelihood of identified risks on an organization - Risks Planning: Risk planning involves developing strategies and actions to manage and mitigate identified risks effectively. - Risk Monitoring: Risk monitoring involves continuously tracking and overseeing identified risks to assess their status, changes, and effectiveness of mitigation strategies. - Risk Review: Risk Review ensures that the risk has been completely removed.

107

参考回答

The Sprint Backlog makes the team's plan for the sprint visible. It contains the selected Product Backlog items and a plan for delivering them. It belongs to the Developers. Only they can change it during the sprint. It is updated daily as work progresses and new information emerges.

108

参考回答

Working with distributed teams, I emphasize over-communication, use collaboration tools effectively, and adapt meeting times to accommodate different time zones, ensuring everyone feels included and informed.

109

参考回答

I identify issues by actively listening during daily stand-ups and one-on-ones, and by observing team dynamics. I address them by facilitating open discussions or having private conversations. The goal is to resolve issues quickly before they escalate.

110

参考回答

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.

111

参考回答

Scrum is a framework that allows teams to work on complex projects and deliver high-value products by approaching problems adaptively. It's a simple, straightforward, and easy-to-implement way of project planning. It can pivot and encourage continuous feedback, allowing a project to fulfill a customer's needs more accurately.

112

参考回答

The three pillars of Scrum are: - Transparency: Transparency refers to the visibility of the project's progress, processes, and challenges to all stakeholders. In Scrum, transparency is achieved through open communication, shared understanding, and accessible artifacts such as the Product Backlog, Sprint Backlog, and Increment. Transparency enables stakeholders to make informed decisions, provide feedback, and collaborate effectively with the Scrum Team. - Inspection: Inspection involves regularly reviewing and evaluating the work and progress of the Scrum Team to identify any deviations, issues, or opportunities for improvement. Scrum events such as Sprint Reviews, Daily Standups, and Sprint Retrospectives provide opportunities for inspection, allowing the team to assess their performance, adapt their plans, and make adjustments as needed. Inspection fosters a culture of continuous improvement and ensures that the product increment meets the desired quality standards. - Adaptation: Adaptation refers to the ability of the Scrum Team to adjust and respond to changes, feedback, and new information throughout the project.

113

参考回答

Scrumban is a hybrid framework that blends Scrum and Kanban. It's useful when a team needs the flexibility of Kanban for continuous flow but also the structure of Scrum for managing sprints. It's often used when a team requires more flexibility but still needs to deliver in iterations.

114

参考回答

The whole point of the Daily Scrum is for the Developers to inspect their progress towards the Sprint Goal and plan their day together. Neither the Product Owner, nor the Team Lead are even mandatory participants in the Daily Scrum, unless they are also playing the role of Developers. My main questions would be - what are they doing in a Daily Scrum? There might be the need for them to have their own regular discussion, but it should happen in a different meeting. So my first instinct is to limit the Daily Scrum to the Developers only. If the Product Owner and the Team Lead want to come, they can only observe and are not allowed to speak, even to ask questions. And then I would work with the Developers to help them make their Daily more productive by first explaining its purpose and giving some tips on how to organize it, but letting them figure out how they want to do it.

115

参考回答

The Definition of Done, or DoD, is a simple list of steps that must be finished before a product increment is said to be ready. This helps everyone see what needs to be done and keeps the work to a high standard. It also makes sure the team agrees on what “done” means. With this, people feel responsible, and at the end of each sprint, the software works like it should.

116

参考回答

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

117

参考回答

The candidate should explain that a backlog with 200 tickets is unmanageable and violates Scrum principles of prioritization and focus. They would recommend working with the Product Owner to refine the backlog, prioritize based on value, break down large items, and limit work in progress to ensure the team can deliver incrementally and effectively.

118

参考回答

I encourage the team to be transparent with each other about their challenges. When it comes to external stakeholders, I help the team communicate in a constructive way. I protect them by ensuring they feel safe to be honest without fear of negative consequences.

119

参考回答

They must describe their role in facilitating the product discovery process and ensuring the list of items for the upcoming sprint aligns with strategic goals. They should explain how they organize scrum meetings that foster clear communication between the product manager and the team and how they apply Agile framework principles to ensure efficient progress and high-quality output.

120

参考回答

The customizable boards for Scrum and Kanban, the ability to track user stories and issues, reporting tools, and integration capabilities are the most beneficial features for enhancing Agile project management.

121

参考回答

A sprint is a short and fixed time frame during which a specific set of tasks are meant to be performed”. An Agile project will be broken down into a certain number of sprints, each sprint lasting for a fixed duration of time. Usually, each sprint runs for 2–4 weeks. A Sprint Planning Meeting occurs before the start of every sprint. That meeting defines what set of items could be developed and delivered in the upcoming sprint.

122

参考回答

Agile is a set of principles that guide teams in delivering value through iterative and incremental development. Scrum is one of the frameworks used to implement these principles. Scrum is structured with specific roles, events, and artifacts like the Product Backlog, Sprint Backlog, and Increment, which makes it easier to adopt Agile practices in the team.

123

参考回答

A Scrum Master plays a very key, optimized and conclusive role for the working of Scrum Framework. The task and goal of Scrum Master are very diversified right from as the leader of Scrum teams to being the interface between the product owners and product developers. The position of Scrum Master is exclusive yet its practice and influence is extremely broad in use. So here are the following roles a Scrum Master plays in an organisation for Implementation of Scrum Framework. Responsibilities of an effective Scrum Master: Manage the Project Development and Implement the practices of Scrum Keeping an eye on every track of the work process Implementing Agile Development practices

124

参考回答

The purpose of qualitative metrics is to gain insight into how one or more of an organization's Scrum Teams are progressing with agile. There are several self-assessment tests available that a Scrum Team can regularly run to collect qualitative metrics about their implementation of Scrum — Hendrik Kniberg's Scrum Checklist is a good example. The interval to test via self-assessment is every 4–12 weeks, with teams of lesser fluency running their tests at the lower end of this range. The individual values recorded by these tests are not very important, but the trend over time is. To visualize these trends, a Scrum Master will need to aggregate the results — in the case of Henrik Kniberg's checklist, an agile practice map may be created over time. While self-assessment tests like Henrik Kniberg's checklist are usually team exercises for recording implementation metrics, sentiment metrics are best captured by running anonymous opinion polls to ensure the participation of the more introverted team members. Using opinion polls, typical questions for recording sentiment metrics include: - What value did the team deliver in the last Sprint? - Has the level of technical debt increased or decreased during the last Sprint? - Are you happy working with your teammates? - Would you recommend your employer (or client) to a friend seeking a new job? It's best to run opinion polls after every Sprint; these polls should only require a few seconds to complete. As with the self-assessment tests, the individual values recorded by running anonymous opinion polls are not very important — it's the trend over time that matters. Trends derived from these polls are great points for discussion during a team's Sprint Retrospectives. Concerning metrics in general, your candidate should support the Agile Manifesto and its principle of transparency: all metrics should be available to all members of a Scrum Team, and largely also to those working in the product delivery organization generally.

125

参考回答

I ensure the Sprint goal is visible and referenced during the Sprint. I protect the team from interruptions and scope creep. I also facilitate regular check-ins to remind the team of the goal and adjust their plan if they drift off course.

126

参考回答

Prioritization is primarily done by the Product Owner based on business value, customer needs, and dependencies. During Sprint planning, the team collaborates to understand these priorities and ensures the top items are feasible and ready for selection. Criteria include value, risk, and dependencies.

127

参考回答

Addressing impediments beyond the team's control requires a collaborative and proactive approach. I work closely with the team to identify and understand external impediments, such as organizational constraints or dependencies. If possible, I engage with relevant stakeholders to mitigate or eliminate these impediments. In situations where direct resolution is challenging, I facilitate discussions within the team to explore alternative solutions or workarounds. It's essential to maintain transparency about the challenges and communicate any impact on the sprint goal or overall project timeline. By actively addressing external impediments and collaborating on viable solutions, we minimize their impact on the team's ability to deliver value consistently.

128

参考回答

Effective communication is a big part of how a Scrum team does well. As a scrum master, I help run Scrum events like the daily scrum. These meetings bring the team together and keep things clear for all. I also work to build a space where everyone feels safe to talk and be honest. I make sure that people respect each other and stay helpful in talks. When the team is not in one spot, I help pick the right ways or tools for us to talk. I help people talk to each other in a clear way by doing these things: - Make sure that, after sprint planning, the team has a clear sprint goal and everyone understands the backlog. - Run retrospectives in a way that gives people a safe space. This helps them feel okay to share honest thoughts about how the work and teamwork can be better. - Guide the team as they practice listening to each other and giving helpful feedback.

129

参考回答

Every day, the team gathers at a designated time and location (in front of the task board) to discuss their progress on tasks and resolved tickets for that day. This meeting focuses on answering three key questions from Scrum: - What tasks or tickets have you finished since the previous meeting? - What tasks or tickets do you aim to complete before the next meeting? - Are there any obstacles or challenges hindering your progress?

130

参考回答

Facilitate open dialogue, identify root causes, and mediate through coaching.

131

参考回答

I promote a positive team environment by encouraging open communication and active listening, ensuring everyone feels heard and valued. Additionally, I organize regular team-building activities to strengthen relationships and address conflicts promptly to maintain harmony.

132

参考回答

According to an early edition of the Scrum Guide, the most committed members of an organization were the pigs. Everyone else was a chicken. That definition typically meant the Scrum master, product owner and developers on the Scrum team were pigs. So too are perhaps a few stakeholders outside the Scrum team whose jobs might ride on the project's success or failure. Everyone else is a chicken; they contribute to the outcome but at less risk. The peculiar allegory is from the chicken-and-pigs parable that says in a ham-and-eggs breakfast, the chicken is involved but the pig is completely committed. The Scrum Guide no longer references this fable. The stewards of the framework felt it was better to address the topic of accountability directly as opposed to through metaphors.

133

参考回答

This is a tricky one. It's a controversial question in that the definition of agile isn't commonly agreed upon. Is it a methodology? Some might say no. They believe it's a framework of approaches and behaviors that encourage iterative development and collaboration between self-organizing teams. Is there a right answer? Yes, the one that conforms to your approach and culture.

134

参考回答

I facilitate team-building activities and encourage social interactions. I ensure that all voices are heard during meetings. I also address disrespectful behavior immediately and hold everyone accountable to the team's working agreements.

135

参考回答

I coordinate between multiple Scrum teams by organizing Scrum of Scrums meeting these regular check-ins help team representatives discuss progress, dependencies, and blockers across teams. This keeps everything aligned, ensuring smooth collaboration and communication throughout the project.

136

参考回答

Everything that is involved in a successful sprint planning session is a well-defined goal, synchronisation and disintegration of priority backlog items from the sprint, development of a realistic project management schedule, and allocation of tasks to the team members (as per individual capacity) and keeping the key stakeholders informed and on loop. Additionally, ensuring to keep track of the overall progress being made by the team. To execute sprint planning successfully, the scrum team must oversee the status of backlog refinement, examine the team members' pace of work, and confirm their availability for the tasks before they brief them about what is to be done over an interactive discussion.

137

参考回答

In a perfect world, the product owner is a dedicated position, not a part-time role for an underutilized project manager or marketing team member. Every Scrum product owner should possess the following characteristics: - A vision for the product being built and an idea of how that vision will roll out over time. - An understanding of how to balance the needs of many stakeholders. - An ability to prioritize the product backlog in a way that maximizes the value of the product that gets built. What takes a product owner from good to great is the trust they've earned among their peers. That means the organization and the stakeholders trust this person to make timely decisions on how the product should be built. It also means the Scrum teams trust the product owner to make fair and final decisions that managers won't overrule. When an individual bearing these qualities is identified, the organization has found an effective product owner.

138

参考回答

The three Scrum artifacts are the product backlog, the sprint backlog, and the product increment. The product backlog is an ordered list of tasks and items needed in a product, typically maintained by the product owner. The sprint backlog is a list of tasks that need to be accomplished in a sprint. The product increment is the deliverable completed in a sprint.

139

参考回答

Agile is a mindset and set of values defined in the Agile Manifesto, while Scrum is a specific framework that applies Agile principles. Agile defines what we believe in, such as adaptability and customer collaboration, whereas Scrum defines how to work using roles, events, and artifacts to deliver value incrementally.

140

参考回答

Scrum ceremonies are structured events that ensure transparency and alignment. The five Scrum events are - Sprint Planning - Daily Scrum - Sprint Review - Sprint Retrospective - The Sprint (container event). Each ceremony supports inspection and adaptation.

141

参考回答

The candidate should explain that Waterfall is suitable for projects with fixed requirements and sequential phases, while Kanban is ideal for continuous delivery and managing work-in-progress limits. Scrum is better for iterative development and complex projects requiring adaptability.

142

参考回答

This breaks Scrum flow. I would: - Understand why management bypassed the process - Re-align through conversation - Reinforce Product Owner accountability - Make the impact visible (context switching and priority disruption) Scrum requires clarity of roles.

143

参考回答

Scrum is a framework used in agile project management, primarily in software development. It is designed to help teams collaborate effectively and adapt to rapidly changing requirements. In Scrum, work is divided into short iterations called “sprints,” usually lasting two to four weeks. Key elements of Scrum include: - Roles: The Scrum team consists of a product owner, who represents the stakeholders and defines the product requirements; a Scrum master, who facilitates and guides the team; and the development team responsible for delivering the product. - Artifacts: Scrum utilizes several artifacts to manage and track work. These include the product backlog, which is a prioritized list of features and tasks, and the sprint backlog, which contains the specific items the team commits to completing during the sprint. - Events: Scrum prescribes specific events to enable effective collaboration and synchronization within the team. These include daily stand-up meetings for status updates, sprint planning to determine what can be accomplished in the upcoming sprint, sprint review to showcase the completed work, and sprint retrospective to evaluate the team's performance and identify areas for improvement. Scrum emphasizes transparency, inspection, and adaptation, allowing teams to continuously deliver high-quality products while accommodating changing requirements.

144

参考回答

Firstly, I'd like to understand the process better. Why does this dependency exist? What causes it? Is it the lack of knowledge or skills on the team? Is it a strict approval process not permitting the team to do that pre-work themselves? Is it just the way it was always done before? To understand that I will most likely need to facilitate a discussion between my team and the other team to create alignment. Based on the reason we can find an appropriate solution. For example, if the team is lacking knowledge or skills, we need to organize some knowledge transfer activities. Maybe there are opportunities for pair programming. Maybe better documentation can help. Maybe a simple training session will suffice. If the issue is the process itself, then we would need to go back to the drawing board with everyone involved in it to identify how we can optimize it to remove dependency. This might include not only my team and the team they are dependent on, but also management, and potentially even other teams who are impacted by that process.

145

参考回答

There are multiple tools like Burn up, burn down but most famous is Burn down charts. Here we check daily the amount of work remaining compared to the planned. Here in below burn down chart the Orange line is ideal burn down rate per day required to finish things on time and gray like is the actual remaining to finish things recorded every day, especially during the Daily Scrums.

146

参考回答

The Daily Scrum is crucial as it allows the team to synchronize their activities, discuss challenges, and plan for the next 24 hours. This daily meeting helps in identifying and addressing impediments promptly.

147

参考回答

A Scrum Master is the facilitator of the Scrum framework. They help the team understand Scrum theory and practice, facilitate Scrum events, remove impediments, and coach team members to improve collaboration and efficiency. They also ensure that Scrum principles are followed throughout the organization.

148

参考回答

The Sprint Backlog is a list of tasks that the team has committed to working on during a particular sprint. It is derived from the Product Backlog, and it defines what work needs to be done to achieve the sprint goal. The team works collaboratively to complete the items in the Sprint Backlog during the sprint.

149

参考回答

150

参考回答

Explain the Sprint Goal and inspect new work for future prioritization.

151

参考回答

Evaluating the success of a Scrum team involves assessing both quantitative and qualitative metrics. Quantitatively, I look at velocity, burndown charts, and sprint progress to ensure the team is consistently delivering value. Qualitatively, I assess team satisfaction, collaboration, and their ability to adapt to change. By combining these metrics, I gain a holistic view of the team's performance and identify areas for continuous improvement. It's essential to strike a balance between quantitative and qualitative measures to foster a high-performing and satisfied team.

152

参考回答

The Scrum Master is a management position, but it isn't a manager position. The Scrum Master only manages the scrum process and not the team. Although the Scrum Master doesn't have manager authority, they would resolve impediments. The Scrum Master facilitates their decisions and eliminates hurdles of the development. Take note, the Scrum Master doesn't manage the development team as they are responsible for their own management. The Scrum Master shields them from extrinsic troubles.

153

参考回答

The primary goal is to inspect the increment and adapt the Product Backlog if needed. It's a collaborative meeting where stakeholders and the team discuss what was done and plan for the next steps.

154

参考回答

I measure the success of a Scrum team using key metrics like velocity and sprint burndown charts, which provide insights into the team's productivity and progress. Additionally, I consider team satisfaction and stakeholder feedback to ensure we are meeting expectations and continuously improving.

155

参考回答

The team defines the Sprint Goal and selects and plans Product Backlog items.

156

参考回答

The candidate should describe responsibilities such as facilitating Scrum ceremonies, coaching the team, removing impediments, and ensuring adherence to Scrum principles, along with specific examples of how they supported the team.

157

参考回答

Popular Scrum tools include Jira, Trello, Asana and ClickUp. These tools help teams manage tasks, track progress, and collaborate easily.

158

参考回答

I promote psychological safety by encouraging open feedback and ensuring no one is punished for speaking up. I advocate for a healthy work-life balance and ensure the physical workspace (or virtual tools) are conducive to collaboration and focus.

159

参考回答

Measuring velocity can be tricky if iteration lengths change, as consistency is key to tracking progress. A fixed iteration length ensures steady rhythm and reliable predictions.

160

参考回答

Helping with the scrum process is an important part of what a scrum master does. A scrum master acts as a leader who serves the team. The main goal is to be sure that the scrum team follows scrum values and works with best practices. A scrum master helps create a space where people feel free to work together. Some of the key jobs in this role are coaching people on agile principles. A scrum master also leads scrum ceremonies, like sprint planning and daily standups. They help manage the product backlog and try to keep out things that might stop the team from working well. When there is a problem or an argument, the scrum master steps in to help fix it. They also help the team choose what tasks or ideas will add the most business value. A big part of the role is getting the team to look for better ways to work, which helps with continuous improvement. This way, the scrum master works to boost team morale and make the whole team more productive.

161

参考回答

I ensure the team maintains a sustainable pace by closely monitoring their workload and making necessary adjustments to prevent burnout. I also encourage regular breaks and promote a healthy work-life balance to keep the team motivated and productive.

162

参考回答

Scrum can be defined as a lightweight framework, where people can resolve complex problems as a team to deliver software products with high value.

163

参考回答

Before starting the scrum sprint, the product owner checks the list of all fresh functions, modification demands, updates, and error reports and decides which ones are of high priority. If the project is fresh, the current framework must introduce additional functionality; this item list is stated as the Product Backlog. The stuff that's held on Sprint is called the Sprint Backlog.

164

参考回答

Success is measured by the team's ability to consistently deliver valuable increments, the predictability of the Sprint (velocity), and the reduction of waste (e.g., building features that are not used). A healthy backlog is one where items are well-refined, prioritized, and transparent to all stakeholders.

165

参考回答

Scaling requires: - Shared backlog alignment - Clear dependency management - Integrated Sprint goals - Regular cross-team sync Frameworks like SAFe or LeSS can support scaling, but coordination discipline matters more than framework choice.

166

参考回答

Yes, Scrum encourages cross-functional collaboration. I involve team members in backlog refinement, Sprint Reviews, and customer feedback sessions. Developers can contribute ideas, technical insights, and feasibility inputs. This shared ownership improves product quality and strengthens alignment between business and technical goals.

167

参考回答

Situation: Led a project with frequent requirement changes from stakeholders. Action: Implemented an Agile approach to accommodate changes while maintaining project momentum. Result: Delivered a flexible and adaptable solution that met evolving stakeholder needs.

168

参考回答

Minimum Viable Product (MVP) is a Lean Startup concept that emphasizes the importance of learning while developing a product. This enables one to test and understand the concept by exposing target consumers and users to the initial version. To accomplish this, one must first gather all pertinent data and then learn from it. The MVP concept is to create a product, provide consumers access to it, and observe how the product is used, perceived, and understood. This will also give you a better idea of what the needs of your clients or users are. Successful products are released into the market in stages over time, with each "significant" deployment referred to as a release. An MMR (Minimum Marketable Release) is a product release with the minimal possible feature set that solves your customers' current new needs. MMRs are used to shorten time-to-market between releases by condensing each release's coherent feature set to the lowest increment that provides new value to customers.

169

参考回答

Yes, this is a very common scenario. The story point given by the development team is, say 3 but the tester gives it 5. In that case, both the developer and tester have to justify their story point, have discussions in the meeting, and collaborate to conclude a common story point.

170

参考回答

To help a struggling scrum team do better, it is good to work on how people talk with each other. Try to see what problems are stopping the team from moving ahead. The team should learn to work together and help each other. Ask everyone to share what they feel in meetings, and do this often. Set goals that the team can reach. Use the main ideas and steps from agile to give the team power to act. If you do these things, you can create a place where there is continuous improvement and everyone works to get better all the time.

171

参考回答

A spike is a time-boxed research activity used to reduce uncertainty or investigate technical complexity.

172

参考回答

My approach to identifying and removing impediments is proactive, transparent, and team-centric. I continuously observe the team's workflow through Daily Scrums, backlog refinement, and direct conversations to surface blockers early. If an impediment is identified, I focus on understanding its root cause, assessing its impact on sprint goals, and deciding whether it can be resolved within the team or requires escalation. I remove impediments by facilitating collaboration, coordinating with external stakeholders, and addressing systemic issues, while ensuring the team remains focused on delivering value.

173

参考回答

The 5 phases of Risk Management in Scrum are Identification, Assessment, Prioritization, Mitigation, and Monitoring. These phases help teams identify potential risks early, assess their impact, prioritize actions, mitigate risks, and continuously monitor to avoid problems later.

174

参考回答

Epic in Scrum can be defined as the ultimate goal or objective that everyone in the team works towards. Generally, Epic is a significant piece of work and therefore accomplishing it requires multiple sprints, which usually extend up to 3-4 weeks or even more than that. The purpose of Epic is to manage smaller, related user stories with planning, alignment and tracking. User Stories form an important part of the Product Backlog. These can be defined as a small requirement or functionality coming from the user's point of view, which helps in establishing communication between the scrum team and the stakeholders. User stories are short enough to be managed in a single sprint. In simple terms, it can be inferred that with a user story, we can define who the user is, what and why they want it. Lastly, tasks are actionable steps taken by the developers to address workable items required to complete a user story. These also do not last longer, and can easily be taken care of within a sprint. Examples of Scrum tasks include ‘create page layout', 'design the 'Add to Cart' button. Key features of tasks in Scrum are that they are actionable, assignable, detailed (specified) and trackable.

175

参考回答

I have regular one-on-ones to discuss their career goals and aspirations. I provide opportunities for them to learn new skills, such as attending training or working on different parts of the product. I also offer constructive feedback and coaching to help them improve.

176

参考回答

The candidate should acknowledge the challenge and express interest in such situations, citing experience with complex projects. They would describe how they handle delays by re-prioritizing, managing dependencies through communication, and incrementally modernizing technology while maintaining team morale and stakeholder alignment.

177

参考回答

I use various techniques to encourage participation, such as silent brainstorming, dot voting, and round-robin sharing. I create a safe environment by emphasizing that all feedback is constructive and by using anonymous tools if needed to ensure everyone's voice is heard.

178

参考回答

MVP (Minimum Viable Product): A basic version with just enough features to be usable. MMP (Minimum Marketable Product): A more refined version that is ready for market release.

179

参考回答

Trust is built through consistency and genuine interest in the team's success. My approach when joining a new team involves being reliable, transparent, and showing genuine interest in the team's success. Trust is not declared. It is earned through repeated, reliable behavior over time.

180

参考回答

Scrum artifacts are tangible documents or items that provide transparency and insight into the work being done and the progress of the project within the Scrum framework. These artifacts serve as essential tools for communication, collaboration, and decision-making within the Scrum Team and with stakeholders. The three primary Scrum artifacts are: - Product Backlog: The Product Backlog is a dynamic, prioritized list of all the features, enhancements, bug fixes, and other work items that need to be addressed in the product. Managed by the Product Owner, the Product Backlog serves as the single source of truth for all requirements and serves as the input for Sprint Planning. - Sprint Backlog: The Sprint Backlog is a subset of the Product Backlog selected by the Development Team for implementation during a specific Sprint. It consists of the user stories, tasks, and other work items that the team commits to completing within the Sprint. - Increment: The Increment is the sum of all the completed and "Done" Product Backlog items at the end of a Sprint. It represents the tangible outcome of the team's work during the Sprint and is potentially shippable. Each Increment must meet the Definition of Done, which defines the quality criteria that must be satisfied for an item to be considered complete.

181

参考回答

- Scrumban is a hybrid Agile methodology that combines principles from Scrum and Kanban. It blends the structured approach of Scrum with the flexibility and continuous flow of work characteristic of Kanban. - In Scrumban, teams typically use a Kanban board to visualize their workflow, with columns representing different stages of work (e.g., To Do, In Progress, Done). They still adhere to time-boxed iterations (Sprints) like in Scrum, but they may have more flexibility in terms of the length of Sprints or when new work can be introduced into the Sprint.

182

参考回答

By actively listening, acknowledging the feedback, and using it as an opportunity for improvement without taking it personally. Applying feedback in the next sprint ensures continuous growth.

183

参考回答

No, a Scrum Master is not a traditional management position. Instead, the Scrum Master acts as a facilitator and coach, helping the team follow Scrum practices, remove obstacles, and improve collaboration. They guide the team but don't manage the team in the traditional sense.

184

参考回答

The team must create action items so that the retrospective is successful. To start this process, a simple way is to simply list everyone's ideas. While listing, you can also tag anyone who is responsible for either tackling one of these tasks or figuring out what to do with them further. You should immediately move on from action item creation to discuss how each person's idea can be used for product development and improvement.

185

参考回答

I dedicate time for learning, such as 'Innovation Sprints' or 'Hackathons.' I encourage the team to experiment with new practices and reflect on the results. I also lead by example, sharing what I learn and seeking feedback.

186

参考回答

Foster trust, clarify roles, encourage ownership and coach continuous improvement.

187

参考回答

The work to be done in a sprint is defined by the velocity, which defines how many items the team can deliver. To measure progress within a sprint, a sprint burndown chart is used. A burndown chart will show progress during a sprint in terms of how many user stories are pending and the number of hours left.

188

参考回答

Addressing challenges with cross-functional collaboration involves creating an environment that fosters open communication and mutual understanding. I facilitate team-building activities and workshops to strengthen interpersonal relationships and build trust. Additionally, I encourage cross-functional training to broaden team members' skill sets and enhance their understanding of each other's roles. If collaboration challenges persist, I conduct one-on-one discussions to understand individual perspectives and concerns, working towards solutions that promote a more collaborative and cohesive team. By actively promoting cross-functional collaboration and addressing challenges proactively, we create a work environment that maximizes the collective strengths of the team.

189

参考回答

In a Daily Stand-Up session, team members discuss their progress and identify any obstacles. The term 'stand-up' emphasizes brevity, as participants usually stand during the meeting, which typically lasts about 15 minutes. Each day, at a designated time, the team convenes to share updates on what they accomplished the previous day, their plans for the current day, and any challenges they encounter.

190

参考回答

- Scrum-ban is a practice with a combination of Scrum and Kanban. Scrum-ban can reduce encounters with the needs of the team, and reduce the batching of work, and implement a pull-based system. - It creatively includes the structure of Scrum and gives a visualization of Kanban.

191

参考回答

Scrum protects the sprint from unplanned changes to allow the team to focus and deliver. However, it does recognize that circumstances change. The standard approach is that the Product Owner can cancel a sprint if the Sprint Goal becomes obsolete. The Scrum Master's role is to protect the team from mid-sprint scope additions while helping stakeholders understand why that protection exists.

192

参考回答

When asked to change the definition of done during a sprint, the initial reaction is to converse with the team to understand the reasons for the suggested alteration. Although Scrum emphasizes adaptability, we focus on upholding the integrity of the sprint goal. If the suggested alteration aligns with the sprint goals and does not impact quality, we might be open to modifying the definition of done. Yet, if the alteration brings dangers to the sprint objective or increases needless complications, we assist the team in evaluating potential consequences and reaching a well-informed choice together.

193

参考回答

I listen to their concerns to understand the reason for resistance. I involve them in the change process, giving them a voice in how it is implemented. I also start with small experiments to demonstrate the value of the change, making it less daunting.

194

参考回答

Yes, but organizations typically prefer candidates with some project exposure. Freshers can strengthen their profile by: - Getting Scrum certifications - Participating in Agile internships - Understanding real-world Scrum scenarios

195

参考回答

The popular tools used in Scrum projects are-

196

参考回答

When teams follow rituals without purpose, agility disappears. I continuously ask: - Why are we doing this ceremony? - What outcome does it drive? - Is this adding value? Agile requires intent, not repetition.

197

参考回答

An MVP is set of minimum requirements or features with which it looks like the product if shipped can be used by the users well and they feel the major value is delivered. However MMP is the minimal set of a requirement that is ready to be shipped to market and can be marketed that guarantees the usefulness to the customer. MMP is fully realized version however MVP may the one which is not fully ready for market but estimated to be valuable if completed and released. Example MMP: www.redbus.com released the first version without capability of billing and disbursal of tickets. The caveat here is you must validate that this minimum feature product solves few major problems for the users and they feel it's good for us. So with Red bus even without payment capability, the users were able to see the buses details and send info about with bus they want to book and bus operators used to call them and reserve seats. SO the major problem of travel and communication hassle was solved. MVP: Imagine Red bus is ready with the code and can be released however they do not have the real Bus data that can be used by users for booking then they have an MVP but not MMP.

198

参考回答

The candidate should discuss strategies such as recognizing achievements, providing support, fostering open communication, and adjusting workload to maintain morale.

199

参考回答

If retros are becoming talk-heavy and action-light, I'd first check if we're actually prioritizing the action items. I've seen teams generate ideas but then never implement them because they're not tied to someone or added to the backlog. So I'd change the format slightly—instead of brainstorming everything, I'd introduce a ‘Start-Stop-Continue' format where we're forced to be more decisive about what we actually change. I'd also make sure we only commit to two or three action items max, assign owners to each one, and put them in the sprint backlog so they get visibility. In my last role, we were spending an hour in retros and walking out with nothing concrete. Once we started treating action items like sprint stories and tracking them week to week, the team saw actual improvements and got more engaged in the process.

200

参考回答

Agile is a project management approach that emphasises the completion of goals in small increments. Therefore, in Agile, any project is accomplished through a series of small tasks, which are to be continuously delivered in short durations. It is because of this that adapting to new developments and adjusting to new priorities becomes easier. Agile focuses on individuals and interactions. Scrum can be defined as an agile methodology, or a framework that implements Agile principles through the use of roles, events and rules, for developing products in a volatile environment. It focuses on the framework for implementing the Scrum values.

すべての情報を見逃したくないですか？

100％合格！Cisco、PMP、CISA、CISM、AWS 模擬試験セール中！
今すぐ入手

認定資格を取得して、履歴書を際立たせましょう。

すべての情報を見逃したくないですか？

100％合格！Cisco、PMP、CISA、CISM、AWS 模擬試験セール中！ 今すぐ入手

認定資格を取得して、履歴書を際立たせましょう。

100％合格！Cisco、PMP、CISA、CISM、AWS 模擬試験セール中！
今すぐ入手