Free Cram & Latest Exams Dumps

In theScrum framework, the three defined accountabilities are:
* Product Owner- Responsible for maximizing the value of the product by managing the Product Backlog.
* Scrum Master- Ensures that Scrum is understood and enacted effectively, removes impediments, and serves the Scrum Team and organization.
* Developers- Responsible for delivering a “Done” Increment that meets the Sprint Goal.
There is no role forLead Developer,Project Manager, orBusiness Analystin Scrum. Scrum promotes self- management, cross-functional teams, and does not include traditional hierarchical roles.
Why the other options are incorrect:
* A. Lead Developer:Scrum does not have a Lead Developer role or accountability.
* B. Project Manager:Scrum does not include a Project Manager role as tasks and responsibilities are distributed among the Scrum Team.
* D. Business Analyst:While the Product Owner may perform some business analysis tasks, there is no separate role for a Business Analyst in Scrum.

TheDaily Scrumis a time-boxed event that allows theDevelopersto inspect progress toward the Sprint Goal and adapt their plan as necessary. This daily inspection and adaptation ensure the team stays aligned and on track to meet their objectives.
According to the2020 Scrum Guide:
* The Developers inspect how progress is trending toward completing the work in the Sprint Backlog.
* They adapt their work plan based on challenges, progress, or new information.
Why the other options are incorrect:
* B. Assign tasks:Tasks are not assigned in Scrum. Developers are self-organizing and decide collaboratively how to accomplish their work.
* C. Demo the changes to Stakeholders:Demos occur during the Sprint Review, not the Daily Scrum.
* D. Estimate the pending work:While work may be discussed, the Daily Scrum is not used for estimation purposes.

The Scrum Team must demonstrateCommitmentto achieve the Sprint Goal. Commitment is one of the five Scrum Values, and it reflects the team’s dedication to the Sprint Goal, the work planned in the Sprint Backlog, and to collaborating effectively. Without commitment, the team cannot focus on delivering the Increment or achieving the Sprint Goal.
According to the2020 Scrum Guide, the Scrum Values are:
* Commitment: Dedication to the team’s goals and delivering value.
* Focus: Concentrating on the Sprint Goal and avoiding distractions.
* Openness: Being transparent about challenges and progress.
* Respect: Valuing each team member and their contributions.
* Courage: Facing challenges and making tough decisions.
Why the other options are incorrect:
* A. Completion:This is not a Scrum Value. Commitment drives completion, but “completion” itself is not a value.
* C. Agreement:While agreement is important, Scrum does not define it as a core value.
* D. Alignment:While alignment is critical to achieving goals, it is not one of the five Scrum Values.

Product Backlog refinementis the act of breaking down and further defining Product Backlog items into smaller, clearer, and more actionable items. This process ensures that the Product Backlog is well-organized, understood, and ready for the upcoming Sprint Planning. Refinement helps the Developers and Product Owner collaborate to add detail, order, and estimates to Product Backlog items.
According to the2020 Scrum Guide:
* Product Backlog refinement is an ongoing activity that occurs throughout the Sprint.
* It is not a formal event, and its timing and structure are determined by the Scrum Team.
* Refinement improves clarity and helps the team better understand upcoming work.
Why the other options are incorrect:
* A. a recurring event in the middle of each Sprint:Product Backlog refinement is not a time-boxed event. It occurs continuously, as needed.
* C. an opportunity for the Developers to estimate Product Backlog items:While estimation may occur during refinement, the primary purpose is breaking down and clarifying items, not solely estimation.
* D. a pre-planning meeting to shorten the length of Sprint Planning:Product Backlog refinement is not a pre-planning meeting but an ongoing activity to prepare for future Sprints.

One of the key services aScrum Master provides to the Product Owneris helping them findeffective Product Backlog management techniques. This ensures that the Product Owner can maximize the value of the product and effectively manage the Product Backlog.
According to the2020 Scrum Guide, the Scrum Master serves the Product Owner by:
* Helping the Product Owner find techniques for effective Product Goal definition and Product Backlog management.
* Facilitating stakeholder collaboration when needed.
* Supporting empirical product planning for complex environments.
Why the other options are incorrect:
* A. Assign tasks to the Developers:Tasks are not assigned in Scrum. Developers are self-organizing and responsible for determining how they will complete the work.
* B. Write user stories:Writing user stories is a Product Owner responsibility, not the Scrum Master’s.
* C. Prioritize the backlog:The Product Owner prioritizes the Product Backlog, not the Scrum Master.

TheScrum Mastershould coach the Developers byexplaining the intent of the Daily Scrum, which is to inspect progress toward the Sprint Goaland adapt the plan as needed. The Daily Scrum is not a status update meeting-it is a collaborative event for the Developers to synchronize their efforts, share progress, and discuss any impediments.
According to the2020 Scrum Guide:
* The Daily Scrum is a15-minute eventwhere the Developers inspect their progress and adapt their plan to achieve the Sprint Goal.
* The event belongs to the Developers, and they decide how to structure it, but its purpose must align with the framework’s guidance.
Why the other options are incorrect:
* B. Cancel the Daily Scrum and have status update meetings instead:Status update meetings go against Scrum principles, which emphasize team ownership and collaboration.
* C. Reduce the occurrence for this meeting to once a week:The Daily Scrum is adailyevent for inspection and adaptation; reducing its frequency would hinder the team’s ability to remain aligned.
* D. Make Daily Scrum an optional meeting for the Developers to attend:The Daily Scrum is mandatory for the Developers to inspect and adapt their plan, and making it optional undermines its importance.

The Product Owner is accountable forcreating and ordering Product Backlog itemsto maximize the value of the product. This includes clearly expressing Product Backlog items, ordering them to maximize value, and ensuring that the Product Backlog is transparent and understood.
According to the2020 Scrum Guide, the Product Owner is accountable for:
* Maximizing the value of the product resulting from the work of the Scrum Team.
* Effectively managing the Product Backlog by ensuring it is prioritized and transparent.
* Creating Product Backlog items in collaboration with stakeholders and the Scrum Team.
Why the other options are incorrect:
* A. Describe the solution:The Product Owner defines the “what” (desired outcomes), not the technical
“solution,” which is determined by the Developers.
* B. Manage the Developers:The Product Owner does not manage the Developers. Developers are self- managing and self-organizing.
* D. Recognize titles:Titles have no significance in Scrum, and this is not a responsibility of any Scrum role.

When a Scrum Team says a Product Backlog item isdone, it means that the item meets theDefinition of Done agreed upon by the Scrum Team. The Definition of Done ensures that the work is complete, usable, and meets quality standards.
According to the2020 Scrum Guide:
* The Definition of Done is a shared understanding of what it means for work to be complete.
* If an Increment or Product Backlog item does not meet the Definition of Done, it cannot be considered part of the usable Increment.
Why the other options are incorrect:
* A. The item has been developed and tested:While development and testing are part of the process,
“done” requires meeting all criteria in the Definition of Done, not just these two aspects.
* B. The item has been deployed to the production environment:Deployment is not a requirement for an item to be considered “done” in Scrum.
* D. The item meets the Definition of Done provided by the Product Owner:The Definition of Done is established by the entire Scrum Team, not the Product Owner alone.

TheScrum Masteris responsible for leading and coaching the organization in its Scrum adoption. They play a critical role in helping the organization understand and implement Scrum practices, fostering an environment of empiricism and continuous improvement.
According to the2020 Scrum Guide, the Scrum Master serves the organization by:
* Leading, training, and coaching the organization in Scrum adoption.
* Helping employees and stakeholders understand and enact an empirical approach to work.
* Removing barriers between stakeholders and Scrum Teams.
Why the other options are incorrect:
* A. Customer:Customers provide requirements and feedback but do not lead or coach the organization in Scrum adoption.
* B. Product Owner:The Product Owner manages the Product Backlog and focuses on delivering value but is not responsible for organizational Scrum adoption.
* C. Developers:Developers are responsible for delivering the Increment and are not accountable for coaching the organization.

TheDaily Scrumis the event where impediments to achieving the Sprint Goal are shared. It is a time-boxed event (15 minutes) held every day during the Sprint. During this event, the Developers inspect their progress toward the Sprint Goal and identify any blockers or impediments that need to be addressed.
According to the2020 Scrum Guide:
* The Developers use the Daily Scrum to inspect progress andadapt their planto achieve the Sprint Goal.
* Impediments are raised and addressed by the Scrum Master if they cannot be resolved by the team.
Why the other options are incorrect:
* B. Sprint Planning:Sprint Planning is focused on creating the Sprint Goal and selecting Product Backlog items for the Sprint, not sharing impediments.
* C. Sprint Retrospective:The Retrospective focuses on process improvements and team dynamics, not day-to-day impediments during the Sprint.
* D. Sprint Review:The Sprint Review is about presenting the Increment and gathering feedback, not resolving impediments.

ScrumArtifactsrepresent work or value, providing transparency and opportunities for inspection and adaptation. TheSprint Backlogis one of the three primary Scrum Artifacts defined in the2020 Scrum Guide:
* Product Backlog: The ordered list of everything that is needed in the product.
* Sprint Backlog: The plan for the Sprint, including the Sprint Goal, selected Product Backlog items, and the work plan for delivering the Increment.
* Increment: The sum of all work completed during a Sprint that meets the Definition of Done.
Why the other options are incorrect:
* A. Definition of Done:While critical to ensuring quality, the Definition of Done is not an Artifact but rather a standard that applies to the Increment.
* C. Sprint Goal:The Sprint Goal is part of the Sprint Backlog but is not a standalone Artifact.
* D. Sprint Burndown Chart:This is a complementary tool used for tracking progress but is not an official Artifact in Scrum.

Scrum teams plan workone Sprint at a time, using theSprint Planning eventto adapt the Sprint Backlog based on what was learned in previous Sprints. This approach aligns with Scrum’sempirical process control, which relies on inspection and adaptation to plan effectively.
According to the2020 Scrum Guide:
* Sprint Planning creates aSprint Backlog, which includes the Sprint Goal, selected Product Backlog items, and the plan to deliver them.
* Teams adjust their plans Sprint by Sprint, responding to new information, feedback, and changing circumstances.
Why the other options are incorrect:
* A. One release at a time, adjusting the number of Sprints to the prior releases’ average velocity:
Scrum does not prescribe release-driven planning or adjusting Sprint duration based on velocity.
* C. One project at a time, adjusting each Sprint Backlog Item to meet the release date negotiated at inception:Scrum encourages iterative planning within Sprints, not fixed plans tied to predetermined release dates.
* D. One Sprint at a time in the Product Backlog Refinement meeting with participation of stakeholders:Product Backlog Refinement is an ongoing activity, not a Sprint planning process.
Stakeholders typically participate in Sprint Reviews, not in backlog refinement.

The Scrum Master is aservant leader, focused on enabling the Scrum Team to work effectively. By taking action to resolve the Developer’s impediment (lack of hardware), the Scrum Masterdemonstratesleadershipby facilitating the team’s progress and ensuring they can meet the Sprint Goal.
According to the2020 Scrum Guide, the Scrum Master serves the Scrum Team by:
* Removing Impediments: Resolving obstacles that block the team’s progress is a key responsibility of the Scrum Master.
* Supporting Team Effectiveness: By addressing issues outside the team’s control, the Scrum Master ensures that the Developers can focus on their work.
Why the other options are incorrect:
* A. Disciplinarian:A Scrum Master does not enforce rules or discipline team members. They lead by fostering collaboration and resolving issues, not by control.
* B. Project Manager:Scrum Masters do not perform traditional project management tasks like resource allocation or task assignment. Their role is to serve and support the team rather than manage it.
* C. Authoritarian:The Scrum Master is not an authoritarian leader. Their approach is grounded in servant leadership, enabling and empowering the team rather than commanding it.

One of the primary services a Scrum Master provides to the Scrum Team isremoving impedimentsto the team’s progress. By doing so, the Scrum Master ensures that the team can work without unnecessary disruptions and remain focused on achieving the Sprint Goal.
According to the2020 Scrum Guide, the Scrum Master serves the Scrum Team in several ways, including:
* Coaching the team in self-management and cross-functionality.
* Helping the team focus on creating high-value Increments.
* Removing impediments to the team’s progress.
Why the other options are incorrect:
* A. Prioritize the Sprint Backlog:This is the Product Owner’s responsibility as part of Product Backlog management.
* B. Develop a release plan:Scrum does not require a release plan, and if it is needed, the Product Owner leads this activity with input from the Developers.
* C. Manage the Product Backlog:Managing the Product Backlog is the Product Owner’s accountability, not the Scrum Master’s.

TheDaily Scrumis a short, time-boxed event (15 minutes) where Developers inspect progress toward the Sprint Goal and adapt their plan for the day. It is not intended to solve problems or deep-dive into discussions.
If a major technical issue is identified during the Daily Scrum, the team should note it and arrange to discuss and solve itoutside of the Daily Scrum.
According to the2020 Scrum Guide:
* The Daily Scrum is focused on progress toward the Sprint Goal, and issues that require detailed discussion or resolution should be handled separately.
* The Scrum Master may help facilitate these follow-up discussions if needed.
Why the other options are incorrect:
* B. Interrupt the Daily Scrum and solve the problem immediately:The Daily Scrum is not a problem- solving session. Interrupting it for detailed discussions disrupts its purpose and timebox.
* C. Escalate it to the Product Owner:Technical issues are typically handled by the Developers, not the Product Owner, who is responsible for managing the Product Backlog and ensuring value delivery.
* D. Discuss it during the Sprint Review:Waiting until the Sprint Review to discuss atechnical issue would delay resolution and risk jeopardizing the Sprint Goal.