The Development Team feels that they are unable to deliver a satisfactory Increment due to the lack of specific user stories. What should the Scrum Team do in response to this situation?<\/p>\n
Prioritize the most critical user stories and focus on delivering value.<\/p>\n<\/li>\n
Review and update the Definition of Done to ensure clarity and completeness.<\/p>\n<\/li>\n
Conduct user research or engage with end-users to gain insights and understand their needs.<\/p>\n<\/li>\n
Collaborate with the Product Owner and stakeholders to refine and add user stories to the Product Backlog.<\/p>\n<\/li>\n<\/ul>\n
In this scenario, the Scrum Team should collaborate with the Product Owner and stakeholders to refine and add user stories to the Product Backlog. They should prioritize the most critical user stories and focus on delivering value. Conducting user research or engaging with end-users can provide valuable insights. Reviewing and updating the Definition of Done ensures clarity and completeness.<\/p>\n
Domain: Scrum<\/p>\n
The Scrum Master identifies a lack of transparency and collaboration among team members. What should the Scrum Master do to address this issue?<\/p>\n
Encourage the use of collaborative tools and techniques to enhance transparency.<\/p>\n<\/li>\n
Facilitate regular team retrospectives to identify areas for improvement.<\/p>\n<\/li>\n
Coach the team on Scrum principles and values, emphasizing the importance of transparency and collaboration.<\/p>\n<\/li>\n
Facilitate team-building activities and promote a culture of trust and open communication.<\/p>\n<\/li>\n<\/ul>\n
In this scenario, the Scrum Master should facilitate team-building activities and promote a culture of trust and open communication. They should encourage the use of collaborative tools and techniques to enhance transparency and coach the team on Scrum principles and values. Regular team retrospectives can also help identify areas for improvement.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
The Development Team raises concerns about the lack of clarity and completeness of the Product Backlog items during the Sprint Planning. What should they do?<\/p>\n
Suggest involving the stakeholders in the Sprint Planning to gather more insights.<\/p>\n<\/li>\n
Note this down and raise this at the Sprint Retrospective.<\/p>\n<\/li>\n
Reject the Product Backlog items and request new ones from the Product Owner.<\/p>\n<\/li>\n
Proceed with the Sprint Planning based on the available information and assumptions.<\/p>\n<\/li>\n<\/ul>\n
In this scenario, the Development Team should ask the Product Owner to clarify the unclear and incomplete Product Backlog items and also raise this a the Sprint Retrospective event to discuss how can such a scenario be avoided in future.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
The Product Owner receives feedback from stakeholders requesting changes to a released product increment. What should the Product Owner do?<\/p>\n
Plan the changes for the next available Sprint.<\/p>\n<\/li>\n
Collaborate with the Development Team to estimate the effort required for implementing the changes.<\/p>\n<\/li>\n
Reject the feedback and proceed with the next Sprint.<\/p>\n<\/li>\n
Evaluate the feedback with stakeholders, prioritize any necessary changes, and add them to the Product Backlog.<\/p>\n<\/li>\n<\/ul>\n
In this scenario, the Product Owner should evaluate the feedback with stakeholders, prioritize any necessary changes, and add them to the Product Backlog for future consideration. They should also collaborate with the Development Team to estimate the effort required for implementing the changes.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
Scrum Master explains Product Backlog Items to the Developers?<\/p>\n
TRUE<\/p>\n<\/li>\n
FALSE<\/p>\n<\/li>\n<\/ul>\n
It is the Product Owner responsible for managing the Product Backlog and explain the items to the Developers.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
True or False: The Product Owner is responsible for coordinating with stakeholders, gathering requirements, and ensuring that the product is delivered on time and within budget.<\/p>\n
TRUE<\/p>\n<\/li>\n
FALSE<\/p>\n<\/li>\n<\/ul>\n
The Product Owner is responsible for coordinating with stakeholders, gathering requirements, and ensuring that the product is delivered on time and within budget. They manage the Product Backlog and collaborate with the Development Team to deliver value incrementally.<\/p>\n
Domain<\/p>\n
Roles<\/p>\n
During the Sprint, a critical dependency is identified that could impact the completion of a Product Backlog item. What should the Development Team do now in this situation?<\/p>\n
Adjust the Sprint Goal to accommodate the dependency and update the Sprint Backlog.<\/p>\n<\/li>\n
Communicate the issue to the Scrum Master and seek assistance in resolving the dependency.<\/p>\n<\/li>\n
Engage with external teams or resources to resolve the dependency.<\/p>\n<\/li>\n
Collaborate with the Product Owner and stakeholders to reassess the priority and explore alternative options.<\/p>\n<\/li>\n<\/ul>\n
In this scenario, the Development Team should collaborate with the Product Owner and stakeholders to reassess the priority of the affected item and explore alternative options. They should also communicate the issue to the Scrum Master, who can assist in resolving the dependency or provide guidance on how to address it effectively.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
The Development Team estimates a Product Backlog item as being too large to complete within a Sprint. What should the Scrum Team do in response to this estimation?<\/p>\n
Collaborate with the Product Owner to break down the item into smaller, manageable pieces.<\/p>\n<\/li>\n
Remove the item from the Sprint Backlog and add it to the Product Backlog for future consideration.<\/p>\n<\/li>\n
Discuss the item in the Sprint Retrospective to identify improvement opportunities.<\/p>\n<\/li>\n
Revisit the item during the next Sprint Planning to refine the estimate.<\/p>\n<\/li>\n<\/ul>\n
In this scenario, the Scrum Team should collaborate with the Product Owner to break down the item into smaller, manageable pieces that can be completed within a Sprint. They can revisit the item during the next Sprint Planning to refine the estimate further. Discussing the item in the Sprint Retrospective can also help identify improvement opportunities.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
True or False: The Daily Scrum is an opportunity for the Scrum Master to provide status updates on behalf of the Development Team.<\/p>\n
FALSE<\/p>\n<\/li>\n
TRUE<\/p>\n<\/li>\n<\/ul>\n
The Daily Scrum is not an opportunity for the Scrum Master to provide status updates on behalf of the Development Team. It is a time-boxed event where the Development Team synchronizes their work, shares progress, and plans the day’s activities. The Scrum Master’s role during the Daily Scrum is to facilitate the event and help remove any impediments.<\/p>\n
Domain<\/p>\n
Events<\/p>\n
True or False: The Scrum Master is responsible for ensuring that the Development Team has a clear understanding of the Definition of Done.<\/p>\n
FALSE<\/p>\n<\/li>\n
TRUE<\/p>\n<\/li>\n<\/ul>\n
The Scrum Master is responsible for facilitating the Development Team’s understanding of the Definition of Done, including its application and alignment with the organization’s quality standards.<\/p>\n
Domain<\/p>\n
Roles<\/p>\n
The Product Owner wants to remove an item from the current Sprint Backlog because it is no longer a priority. What should they do?<\/p>\n
Remove the item from the Sprint Backlog without consulting the Development Team.<\/p>\n<\/li>\n
Seek consensus from the stakeholders before removing the item.<\/p>\n<\/li>\n
Collaborate with the Development Team to assess the impact of removing the item and adjust the Sprint Backlog accordingly.<\/p>\n<\/li>\n
Keep the item in the Sprint Backlog and address it in a future Sprint.<\/p>\n<\/li>\n<\/ul>\n
In this scenario, the Product Owner should collaborate with the Development Team to assess the impact of removing the item from the current Sprint Backlog. They should adjust the Sprint Backlog accordingly based on the team’s assessment and seek consensus from stakeholders if necessary.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
What is the maximum duration for a Sprint in Scrum?<\/p>\n
1 week<\/p>\n<\/li>\n
3 weeks<\/p>\n<\/li>\n
2 weeks<\/p>\n<\/li>\n
4 weeks<\/p>\n<\/li>\n<\/ul>\n
In Scrum, a sprint is a time-boxed event of one to four weeks in which your Scrum team focuses only on a sprint goal.<\/p>\n
Domain<\/p>\n
Sprint<\/p>\n
The Development Team realizes during the Sprint that they won’t be able to complete all the planned Product Backlog items. What should they do?<\/p>\n
Seek assistance from the Scrum Master to remove any obstacles.<\/p>\n<\/li>\n
Inform the stakeholders about the incomplete items and seek their guidance.<\/p>\n<\/li>\n
Continue with the remaining items and deliver what is completed.<\/p>\n<\/li>\n
Collaborate with the Product Owner to reprioritize and adjust the Sprint Backlog.<\/p>\n<\/li>\n<\/ul>\n
In this scenario, the Development Team should collaborate with the Product Owner to reprioritize and adjust the Sprint Backlog based on the remaining capacity and the most valuable items. They should also seek assistance from the Scrum Master to remove any obstacles hindering their progress.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
The Product Owner wants to include a large new feature in the current Sprint. The Development Team determines that it cannot be completed within the Sprint time frame. What should they do?<\/p>\n
Discuss the feature’s complexity and feasibility with the Product Owner and stakeholders.<\/p>\n
Reject the feature request and proceed with the originally planned Sprint Backlog.<\/p>\n
Collaborate with the Product Owner to break down the feature into smaller, deliverable increments.<\/p>\n
Add the feature to the Product Backlog and address it in future Sprints.<\/p>\n
In this scenario, the Development Team should collaborate with the Product Owner to break down the large feature into smaller, deliverable increments. They should also discuss the feature’s complexity and feasibility with the Product Owner and stakeholders to find a suitable solution.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
True or False: The Sprint Backlog is a subset of the Product Backlog that contains the items selected for the current Sprint.<\/p>\n
FALSE<\/p>\n
TRUE<\/p>\n
The Sprint Backlog is a subset of the Product Backlog that contains the items selected for the current Sprint. It represents the Development Team’s plan for delivering the Sprint Goal and creating a potentially releasable Increment.<\/p>\n
Domain<\/p>\n
Artifacts<\/p>\n
True or False: The Product Owner is responsible for ensuring that the Sprint Backlog is visible and transparent to all stakeholders.<\/p>\n
TRUE<\/p>\n
FALSE<\/p>\n
The Development Team is responsible for ensuring that the Sprint Backlog is visible and transparent to all stakeholders. They share their progress and updates during the Sprint Review and communicate the state of the work throughout the Sprint.<\/p>\n
Domain<\/p>\n
Roles<\/p>\n
True or False: The Product Owner can attend the Daily Scrum as an observer, but they should not actively participate in the meeting.<\/p>\n
FALSE<\/p>\n
TRUE<\/p>\n
The Product Owner is encouraged to attend the Daily Scrum as an observer to stay informed about the Development Team’s progress. However, they should not actively participate to avoid turning it into a status meeting or impacting self-organization.<\/p>\n
Domain<\/p>\n
Events<\/p>\n
True or False: The Sprint Backlog can only be modified by the Development Team during the Sprint.<\/p>\n
TRUE<\/p>\n
FALSE<\/p>\n
The Sprint Backlog can be modified throughout the Sprint, but only by the Development Team in collaboration with the Product Owner and under the guidance of the Scrum Master.<\/p>\n
Domain<\/p>\n
Artifacts<\/p>\n
True or False: The Product Owner is responsible for ensuring that the Development Team meets the Sprint Goal.<\/p>\n
TRUE<\/p>\n
FALSE<\/p>\n
The Development Team is responsible for ensuring that the Sprint Goal is met by selecting and delivering the appropriate Product Backlog items. The Product Owner collaborates with the Development Team and provides guidance to align their work with the overall product vision and goals.<\/p>\n
Domain<\/p>\n
Roles<\/p>\n
True or False: The Scrum Master is responsible for facilitating the Daily Scrum and ensuring that it stays within the timebox of 15 minutes.<\/p>\n
FALSE<\/p>\n
TRUE<\/p>\n
The Scrum Master is responsible for facilitating the Daily Scrum and ensuring that it stays within the timebox of 15 minutes. They help keep the event focused, prevent discussions or problem-solving, and follow up on any identified impediments.<\/p>\n
Domain<\/p>\n
Roles<\/p>\n
True or False: The Scrum Team can cancel a Sprint if the Scrum Master believes the Sprint Goal is no longer valid.<\/p>\n
FALSE<\/p>\n
TRUE<\/p>\n
Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Development Team, or the Scrum Master.<\/p>\n
Domain<\/p>\n
Events<\/p>\n
During the Sprint Review, stakeholders provide feedback on a recently delivered Increment. They express concerns about the user interface design and suggest improvements. What should the Scrum Team do with this feedback?<\/p>\n
Assess the feasibility and impact of the suggested improvements.<\/p>\n
Collaborate with the Product Owner to prioritize the feedback and incorporate relevant improvements in the Product Backlog.<\/p>\n
Adapt the Definition of Done to include specific criteria for user interface design.<\/p>\n
Discuss the feedback with the stakeholders to gain a deeper understanding of their concerns.<\/p>\n
In this scenario, the Scrum Team should discuss the feedback with the stakeholders to gain a deeper understanding of their concerns. They should assess the feasibility and impact of the suggested improvements and collaborate with the Product Owner to prioritize and incorporate relevant improvements in the Product Backlog.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
True or False: The Product Owner can assign work to individual Development Team members during the Sprint to ensure efficiency.<\/p>\n
FALSE<\/p>\n
TRUE<\/p>\n
The Development Team is self-organizing and responsible for deciding how to accomplish the work. The Product Owner collaborates with the Development Team, but it is not their role to assign tasks to individual team members during the Sprint.<\/p>\n
Domain<\/p>\n
Roles<\/p>\n
True or False: The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and identify opportunities for improvement.<\/p>\n
FALSE<\/p>\n
TRUE<\/p>\n
The Sprint Retrospective is indeed an opportunity for the Scrum Team to inspect itself and identify opportunities for improvement. It is a time to reflect on the previous Sprint, discuss what went well and what could be done better, and define action items to enhance effectiveness and efficiency.<\/p>\n
Domain<\/p>\n
Events<\/p>\n
A stakeholder requests changes to the Sprint Backlog items during the Sprint. What should the Scrum Team do in response to this request?<\/p>\n
Collaborate with the Product Owner to understand the rationale behind the request and assess its impact on the Sprint Goal.<\/p>\n
Evaluate the changes against the Definition of Done and adjust the Sprint Backlog accordingly.<\/p>\n
Reject the request to maintain the stability of the current Sprint.<\/p>\n
Inform the stakeholder that changes can only be considered in the next Sprint.<\/p>\n
In this scenario, the Scrum Team should collaborate with the Product Owner to understand the rationale behind the stakeholder’s request and assess its impact on the Sprint Goal. They should evaluate the changes against the Definition of Done and adjust the Sprint Backlog accordingly if it aligns with the Sprint Goal.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
True or False: The Product Owner can add new items or modify existing items in the Sprint Backlog during the Sprint to adapt to changing requirements.<\/p>\n
FALSE<\/p>\n
TRUE<\/p>\n
Developers can change the Sprint Backlog. Sprint Backlog is planed by Developers and define the work necessary to create an Increment that meets the Definition of Done. Developers change the Sprint Backlog after consulting with Product Owner.<\/p>\n
Domain<\/p>\n
Artifacts<\/p>\n
True or False: The Product Owner can add new items to the Sprint Backlog during the Sprint if they deem it necessary.<\/p>\n
FALSE<\/p>\n
TRUE<\/p>\n
The Sprint Backlog is a forecast of the work that the Development Team believes it can complete during the Sprint. It should not be changed during the Sprint unless the Development Team and Product Owner collaborate and agree to adjust the scope.<\/p>\n
Domain<\/p>\n
Artifacts<\/p>\n
Who is responsible for ensuring that the Scrum Team understands and adheres to Scrum principles and practices?<\/p>\n
Scrum Master<\/p>\n
Development Team<\/p>\n
Product Owner<\/p>\n
Stakeholders<\/p>\n
The Scrum Master is responsible for ensuring that the Scrum Team understands and adheres to Scrum principles and practices.<\/p>\n
Domain<\/p>\n
Scrum Master Role<\/p>\n
True or False: The Sprint Retrospective is an opportunity for the Scrum Team to inspect its progress, identify improvements, and make adjustments.<\/p>\n
TRUE<\/p>\n
FALSE<\/p>\n
The Sprint Retrospective is a dedicated event where the Scrum Team reflects on the Sprint and identifies opportunities for improvement. It is a chance to inspect their progress, identify what worked well, and make adjustments to enhance their effectiveness and efficiency.<\/p>\n
Domain<\/p>\n
Events<\/p>\n
The Scrum Master observes that the Development Team is struggling with estimation accuracy, leading to frequent scope changes during the Sprint. What should the Scrum Master do to address this issue?<\/p>\n
Increase the time allocated for Sprint Planning to allow for more detailed estimation.<\/p>\n
Conduct training or workshops to enhance the Development Team’s estimation skills.<\/p>\n
Facilitate a discussion to explore alternative estimation techniques and encourage the use of relative sizing.<\/p>\n
Collaborate with the Product Owner to provide clearer requirements and acceptance criteria.<\/p>\n
In this scenario, the Scrum Master should facilitate a discussion with the Development Team to explore alternative estimation techniques, such as relative sizing. They should also collaborate with the Product Owner to provide clearer requirements and acceptance criteria to improve estimation accuracy.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
True or False: The Scrum Master is responsible for removing impediments that the Development Team encounters during a Sprint.<\/p>\n
TRUE<\/p>\n
FALSE<\/p>\n
The statement is true. The Scrum Master is responsible for removing impediments that hinder the progress of the Development Team.<\/p>\n
Domain<\/p>\n
Scrum Master Role<\/p>\n
A Development Team member raises concerns about the clarity and detailed requirements of a Product Backlog item during the Sprint. What should they do?<\/p>\n
Proceed with the implementation based on the current understanding and assumptions.<\/p>\n
Highlight it to the Development team in the Daily Scrum<\/p>\n
Ignore the concerns and focus on completing other items in the Sprint Backlog.<\/p>\n
Collaborate with the Product Owner to gain a better understanding of the item and refine its details.<\/p>\n
In this scenario, the Development Team should collaborate with the Product Owner to gain a better understanding of the unclear Product Backlog item and refine its details. They can seek clarification and work together to ensure a shared understanding of the item’s requirements. Also, the team member should highlight it in the Daily Scrum.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
Who has the authority to cancel a Sprint?<\/p>\n
Product Owner<\/p>\n
Scrum Master<\/p>\n
Development Team<\/p>\n
Stakeholders<\/p>\n
The Product Owner has the authority to cancel a Sprint if the Sprint Goal becomes obsolete or if market conditions change.<\/p>\n
Domain<\/p>\n
Sprint Planning<\/p>\n
True or False: The Sprint Backlog is a forecast of work to be done and may be adjusted throughout the Sprint as more information becomes available.<\/p>\n
FALSE<\/p>\n
TRUE<\/p>\n
The Sprint Backlog is a forecast of work to be done during the Sprint. As the Development Team learns more, new information emerges, or priorities change, they can collaborate with the Product Owner to add, remove, or reorder the items in the Sprint Backlog. Adjustments are expected and can be made to reflect the current understanding and needs.<\/p>\n
Domain<\/p>\n
Artifacts<\/p>\n
True or False: The Scrum Team should only release a potentially shippable product Increment at the end of each Sprint.<\/p>\n
TRUE<\/p>\n
FALSE<\/p>\n
The Scrum Team should strive to create a potentially shippable product Increment at the end of each Sprint, but it is not mandatory. The decision to release the Increment is at the discretion of the Product Owner based on various factors like market conditions and business strategy.<\/p>\n
Domain<\/p>\n
Artifacts<\/p>\n
True or False: The Scrum Master is responsible for removing impediments and ensuring that the Scrum Team has a productive work environment.<\/p>\n
FALSE<\/p>\n
TRUE<\/p>\n
The Scrum Master is indeed responsible for removing impediments that hinder the progress of the Scrum Team. They also foster a productive work environment by enabling collaboration, facilitating events, and coaching the team on self-organization.<\/p>\n
Domain<\/p>\n
Roles<\/p>\n
Definition of Done is optional in Scrum?<\/p>\n
TRUE<\/p>\n
FALSE<\/p>\n
The Definition of Done (DoD) represents the organization’s formal definition of quality for all Product Backlog Items (PBIs). If an organization does not have one, the Scrum team should set its own.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
The Scrum Master observes that some team members dominate the Daily Scrum, while others remain quiet. What should the Scrum Team do to address this imbalance?<\/p>\n
Set guidelines or time limits for each team member’s update to promote fairness.<\/p>\n
Encourage equal participation and ensure that all team members have an opportunity to share their updates.<\/p>\n
Facilitate a discussion during the Sprint Retrospective to address the issue.<\/p>\n
Provide coaching and support to team members who are less vocal or reluctant to speak up.<\/p>\n
In this scenario, the Scrum Team should encourage equal participation and ensure that all team members have an opportunity to share their updates during the Daily Scrum. Setting guidelines or time limits for each team member’s update can promote fairness. Addressing the issue during the Sprint Retrospective and providing coaching and support to less vocal team members can also help create a more balanced and inclusive environment.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
The Product Owner wants to change the Sprint Goal midway through the Sprint due to shifting market conditions. What should the Scrum Team do in response to this request?<\/p>\n
Evaluate the impact of the requested change on the current Sprint Backlog.<\/p>\n
Communicate the potential impact to stakeholders and seek their input.<\/p>\n
Collaborate with the Product Owner to understand the rationale behind the requested change and assess its impact on the Sprint Goal.<\/p>\n
Determine if the change aligns with the Scrum values and principles.<\/p>\n
In this scenario, the Scrum Team should collaborate with the Product Owner to understand the rationale behind the requested change and assess its impact on the Sprint Goal. They should determine if the change aligns with the Scrum values and principles. Communicating the potential impact to stakeholders and seeking their input can help make informed decisions.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
True or False: The Sprint Backlog is a fixed scope and cannot be adjusted during the Sprint.<\/p>\n
FALSE<\/p>\n
TRUE<\/p>\n
The Sprint Backlog is not a fixed scope and can be adjusted throughout the Sprint. As the Development Team learns more, new information emerges, or priorities change, they can collaborate with the Product Owner to add, remove, or reorder the items in the Sprint Backlog.<\/p>\n
Domain<\/p>\n
Artifacts<\/p>\n
The Product Owner is unable to attend the Daily Scrum due to conflicting commitments. What should the Scrum Master and Development Team do?<\/p>\n
Proceed with the Daily Scrum as scheduled as Product Owner is not required to attend the Daily Scrum.<\/p>\n
Assign a proxy Product Owner to attend the Daily Scrum on behalf of the absent Product Owner.<\/p>\n
Cancel the Daily Scrum and reschedule it when the Product Owner is available.<\/p>\n
Adjust the timing of the Daily Scrum to accommodate the Product Owner’s availability.<\/p>\n
In this scenario, the Development Team should proceed with the Daily Scrum as scheduled. The Product Owner is not required to attend the Daily Scrum.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
During Sprint Planning, the Development Team realizes that the selected Product Backlog items cannot be completed within the Sprint timebox. What should the Scrum Team do in response to this realization?<\/p>\n
Cancel the Sprint and start a new one with a revised plan.<\/p>\n
Identify ways to reduce scope or find alternative solutions to meet the Sprint Goal.<\/p>\n
Discuss with the Product Owner the possibility of extending the Sprint timebox.<\/p>\n
Hire external resources and try to complete the work.<\/p>\n
In this scenario, the Scrum Team should cancel the scrum. The sprint can not be extended.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
The Product Owner requests the Development Team to include additional work during the Sprint, which was not part of the original Sprint Backlog. What should the Development Team do?<\/p>\n
Collaborate with the Product Owner to understand the reasons behind the request and negotiate if necessary.<\/p>\n
Evaluate the impact on the Sprint Goal and the team’s capacity before accepting the additional work.<\/p>\n
Inform the Scrum Master about the request and seek guidance on how to proceed.<\/p>\n
Accept the additional work without considering its impact on the Sprint.<\/p>\n
In this scenario, the Development Team should evaluate the impact of the additional work on the Sprint Goal and the team’s capacity before accepting it. They should also collaborate with the Product Owner to understand the reasons behind the request and negotiate if necessary, ensuring a transparent and realistic Sprint commitment.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
True or False: The Sprint Retrospective is an opportunity for the Scrum Team to reflect on their interactions, processes, and tools, and create a plan for improvements in the next Sprint.<\/p>\n
FALSE<\/p>\n
TRUE<\/p>\n
The Sprint Retrospective is a dedicated event where the Scrum Team reflects on their interactions, processes, and tools during the Sprint. They identify areas for improvement and create a plan to implement those improvements in the next Sprint.<\/p>\n
Domain<\/p>\n
Events<\/p>\n
True or False: The Scrum Master is responsible for prioritizing the items in the Product Backlog.<\/p>\n
TRUE<\/p>\n
FALSE<\/p>\n
The Product Owner is responsible for prioritizing the items in the Product Backlog based on value, market conditions, and stakeholder input. The Scrum Master supports the Product Owner in facilitating the backlog refinement process but does not have the authority to prioritize.<\/p>\n
Domain<\/p>\n
Roles<\/p>\n
The Product Owner receives a request from a stakeholder to include a specific feature in the current Sprint. The feature was not previously discussed or prioritized. What should the Product Owner do?<\/p>\n
Evaluate the feature’s alignment with the product vision and priorities before making a decision.<\/p>\n
Include the feature in the current Sprint to address the stakeholder’s request.<\/p>\n
Collaborate with the Development Team to estimate the effort required for implementing the feature.<\/p>\n
Engage in a conversation with the stakeholder to understand the urgency and potential impact of the request.<\/p>\n
In this scenario, the Product Owner should engage in a conversation with the stakeholder to understand the urgency and potential impact of the request. They should then collaborate with the Development Team to estimate the effort required and evaluate the feature’s alignment with the product vision and priorities before making a decision.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
True or False: The Scrum Team should strive to deliver all the items in the Product Backlog by the end of the Sprint.<\/p>\n
FALSE<\/p>\n
TRUE<\/p>\n
The Scrum Team should strive to deliver a potentially releasable Increment of the product by the end of the Sprint, not necessarily all the items in the Product Backlog. The Product Backlog is a dynamic and evolving list that may have items reprioritized or added based on changing requirements and feedback.<\/p>\n
Domain<\/p>\n
Artifacts<\/p>\n
True or False: The Scrum Master is responsible for ensuring that the Development Team has a clear understanding of the work to be done.<\/p>\n
TRUE<\/p>\n
FALSE<\/p>\n
The Product Owner is responsible for ensuring that the Development Team has a clear understanding of the work to be done. The Product Owner collaborates with the Development Team during refinement activities to clarify the requirements and answer any ##### Questions they may have.<\/p>\n
Domain<\/p>\n
Roles<\/p>\n
The Scrum Master notices that the Daily Scrum has become a status report meeting where team members provide lengthy updates. What should the Scrum Master do to address this issue?<\/p>\n
Introduce a time-box and enforce shorter individual updates during the Daily Scrum.<\/p>\n
Cancel the Daily Scrum and rely on asynchronous communication for updates.<\/p>\n
Facilitate the team in understanding the purpose of the Daily Scrum and guide them to focus on the three ##### Questions.<\/p>\n
Encourage team members to share blockers and seek assistance during the Daily Scrum.<\/p>\n
In this scenario, the Scrum Master should facilitate the team in understanding the purpose of the Daily Scrum and guide them to focus on the three ##### Questions: What did I do yesterday? What will I do today? Are there any impediments in my way? They can also introduce a time-box to keep individual updates concise.<\/p>\n
Domain<\/p>\n
Events<\/p>\n
True or False: The Sprint Review is an opportunity for the Scrum Team to inspect the Increment and adapt the Product Backlog if needed.<\/p>\n
FALSE<\/p>\n
TRUE<\/p>\n
The Sprint Review is an opportunity for the Scrum Team to inspect the Increment and gather feedback. Based on the feedback and insights gained during the review, the Product Backlog may be refined and adjusted to reflect new insights or changes in priorities.<\/p>\n
Domain<\/p>\n
Events<\/p>\n
In Scrum, who is responsible for creating and maintaining the Product Backlog?<\/p>\n
Development Team<\/p>\n
Stakeholders<\/p>\n
Scrum Master<\/p>\n
Product Owner<\/p>\n
The Product Owner is responsible for creating and maintaining the Product Backlog as per the Scrum Guide.<\/p>\n
Domain<\/p>\n
Product Backlog<\/p>\n
True or False: The Scrum Master is responsible for creating and maintaining the Product Backlog.<\/p>\n
FALSE<\/p>\n
TRUE<\/p>\n
The Product Owner is responsible for creating and maintaining the Product Backlog, in collaboration with stakeholders and the Development Team. The Scrum Master supports the Product Owner in facilitating the backlog refinement process but is not directly responsible for its creation and maintenance.<\/p>\n
Domain<\/p>\n
Roles<\/p>\n
True or False: The Scrum Master is responsible for documenting meeting minutes and action items during the Daily Scrum.<\/p>\n
FALSE<\/p>\n
TRUE<\/p>\n
The Scrum Master’s primary role during the Daily Scrum is to facilitate the meeting and ensure it stays focused and time-boxed. Documenting meeting minutes and action items is not their primary responsibility.<\/p>\n
Domain<\/p>\n
Roles<\/p>\n
True or False: The Product Owner is responsible for creating and maintaining the Sprint Backlog.<\/p>\n
FALSE<\/p>\n
TRUE<\/p>\n
The Development Team is responsible for creating and maintaining the Sprint Backlog, in collaboration with the Product Owner. The Product Owner provides guidance and ensures the Backlog is aligned with the product vision and priorities.<\/p>\n
Domain<\/p>\n
Roles<\/p>\n
True or False: The Scrum Master is responsible for measuring the velocity of the Development Team.<\/p>\n
FALSE<\/p>\n
TRUE<\/p>\n
The Development Team is responsible for measuring its own velocity, which represents the amount of work it can complete in a Sprint. The Scrum Master may help facilitate the measurement process but is not directly responsible for it.<\/p>\n
Domain<\/p>\n
Roles<\/p>\n
Which Scrum event is designed to inspect the Increment and adapt the Product Backlog if needed?<\/p>\n
Sprint Retrospective<\/p>\n
Daily Scrum<\/p>\n
Sprint Planning<\/p>\n
Sprint Review<\/p>\n
The Sprint Review is the Scrum event that involves inspecting the Increment and adapting the Product Backlog based on feedback.<\/p>\n
Domain<\/p>\n
Sprint Review<\/p>\n
Who is responsible for managing the progress of work during a Sprint?<\/p>\n
Stakeholders<\/p>\n
Development Team<\/p>\n
Scrum Master<\/p>\n
Product Owner<\/p>\n
The Development Team is responsible for managing the progress of work during a Sprint, using the Sprint Backlog and Scrum artifacts.<\/p>\n
Domain<\/p>\n
Roles<\/p>\n
The Scrum Team identifies a process improvement during the Sprint Retrospective. How should they proceed?<\/p>\n
Assign the responsibility to the Scrum Master for implementing the improvement.<\/p>\n
Collaborate to define actionable steps for implementing the process improvement.<\/p>\n
Schedule a separate meeting to discuss the process improvement in detail.<\/p>\n
Update the Product Backlog with the process improvement as a user story.<\/p>\n
In this scenario, the Scrum Team should collaborate to define actionable steps for implementing the process improvement. These steps can be added to the Product Backlog as user stories to ensure they are prioritized and implemented in future Sprints.<\/p>\n
Domain<\/p>\n
Events<\/p>\n
A stakeholder requests to observe the Daily Scrum to better understand the progress of the Development Team. What should the Scrum Team do in response to this request?<\/p>\n
Invite the stakeholder to attend the Daily Scrum as an observer without disrupting the event.<\/p>\n
Discuss the request with the Product Owner and seek their guidance.<\/p>\n
Explain to the stakeholder that the Daily Scrum is an internal event for the Development Team.<\/p>\n
Offer alternative ways for the stakeholder to gain visibility into the team’s progress.<\/p>\n
In this scenario, the Scrum Team should explain to the stakeholder that the Daily Scrum is an internal event for the Development Team. They can offer alternative ways for the stakeholder to gain visibility, such as periodic updates or separate sessions. If the stakeholder’s presence is deemed beneficial, they can be invited as an observer without disrupting the event. Discussing with the Product Owner can provide further guidance.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
The Scrum Master identifies a communication gap between the Development Team and stakeholders, leading to misunderstandings and delays. What should the Scrum Master do to address this issue?<\/p>\n
Facilitate communication and collaboration between the Development Team and stakeholders.<\/p>\n
Organize a workshop to improve the understanding of the Development Team’s work.<\/p>\n
Provide training to the stakeholders on Agile principles and Scrum practices.<\/p>\n
Encourage the Development Team to provide more detailed status reports to stakeholders.<\/p>\n
In this scenario, the Scrum Master should proactively facilitate communication and collaboration between the Development Team and stakeholders to address the communication gap. They can also organize a workshop to improve understanding and provide necessary training to stakeholders on Agile principles and Scrum practices.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
True or False: In Scrum, the Product Owner and the Scrum Master roles can be combined.<\/p>\n
FALSE<\/p>\n
TRUE<\/p>\n
The Scrum Guide does not expressly rule out the possibility of a Scrum Master and Product Owner being the same person on a Scrum Team. However, it is clear that there may be significant conflicts of interest should these different responsibilities be combined in one individual.<\/p>\n
Domain<\/p>\n
Scrum Roles<\/p>\n
The Development Team is unable to complete all the committed Product Backlog items by the end of the Sprint due to unforeseen challenges. What should they do in the Sprint Review?<\/p>\n
Collaborate with the Product Owner to determine the best approach for incomplete items.<\/p>\n
Seek an extension of the Sprint duration to complete the remaining items.<\/p>\n
Present only the completed items and avoid mentioning the unfinished ones.<\/p>\n
Discuss the completed items and the reasons for the unfinished ones, seeking stakeholder input.<\/p>\n
In this scenario, the Development Team should discuss the completed items and openly communicate the reasons for the unfinished ones during the Sprint Review. They should collaborate with the Product Owner to determine the best approach for incomplete items, considering stakeholder input and prioritization.<\/p>\n
Domain<\/p>\n
Events<\/p>\n
True or False: The Scrum Master is responsible for ensuring that the Daily Scrum occurs at the same time every day.<\/p>\n
TRUE<\/p>\n
FALSE<\/p>\n
The Development Team is responsible for determining the best time for the Daily Scrum, based on their availability and needs. The Scrum Master supports the team in establishing a regular and consistent Daily Scrum but does not enforce a specific time.<\/p>\n
Domain<\/p>\n
Roles<\/p>\n
The Sprint Backlog is owned by Developers.<\/p>\n
FALSE<\/p>\n
TRUE<\/p>\n
The Developers own the Sprint Backlog and they are responsible and totally accountable for it.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
During the Daily Scrum, a Development Team member raises an issue that requires immediate attention from the Scrum Master and Product Owner. What should they do?<\/p>\n
Assign a task to the Scrum Master and Product Owner to investigate and resolve the issue.<\/p>\n
Discuss the issue briefly and agree to address it later outside of the Daily Scrum.<\/p>\n
Note the issue and schedule a separate meeting after the Daily Scrum to address it.<\/p>\n
Pause the Daily Scrum and resolve the issue as a team before continuing.<\/p>\n
In this scenario, the team should continue with the Daily Scrum and take it up further after the meeting.<\/p>\n
Domain<\/p>\n
Events<\/p>\n
True or False: The Scrum Team should strive to deliver a potentially releasable Increment of the product at the end of each Sprint.<\/p>\n
FALSE<\/p>\n
TRUE<\/p>\n
The Scrum Team should strive to deliver a potentially releasable Increment of the product at the end of each Sprint. The Increment should meet the Definition of Done and be in a usable condition, even if the Product Owner decides not to release it.<\/p>\n
Domain<\/p>\n
Scrum Principles<\/p>\n
True or False: The Sprint Review is an opportunity for the Scrum Team to inspect the Increment and adapt the Product Backlog accordingly.<\/p>\n
FALSE<\/p>\n
TRUE<\/p>\n
The Sprint Review is a dedicated event where the Scrum Team inspects the Increment and adapts the Product Backlog based on stakeholder feedback, market changes, and new insights gained during the Sprint.<\/p>\n
Domain<\/p>\n
Events<\/p>\n
The Development Team is consistently unable to complete the selected Product Backlog items within the Sprint time frame. What should the Scrum Master do to address this issue?<\/p>\n
Assign additional team members to support the Development Team during the Sprint.<\/p>\n
Review and adjust the Definition of Done to ensure it accurately reflects the team’s expectations.<\/p>\n
Suggest increasing the Sprint duration to provide more time for completing the work.<\/p>\n
Facilitate a retrospective to identify potential causes and collaborate with the team on improvement strategies.<\/p>\n
In this scenario, the Scrum Master should facilitate a retrospective to identify potential causes for incomplete work and collaborate with the team on improvement strategies. They should also review and adjust the Definition of Done to ensure it accurately reflects the team’s expectations.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
What is the recommended maximum size for a Development Team in Scrum?<\/p>\n
There is no specific recommendation.<\/p>\n
10<\/p>\n
5<\/p>\n
15<\/p>\n
There is no specific recommendation for the maximum size of a Development Team in Scrum. It may vary based on the project context.<\/p>\n
Domain<\/p>\n
Development Team<\/p>\n
True or False: The Daily Scrum should be time-boxed to a maximum of 15 minutes, regardless of the number of Development Team members.<\/p>\n
FALSE<\/p>\n
TRUE<\/p>\n
The Daily Scrum should be time-boxed to a maximum of 15 minutes, regardless of the size of the Development Team, to promote concise updates, identify potential obstacles, and facilitate planning for the day.<\/p>\n
Domain<\/p>\n
Events<\/p>\n
In Scrum, how frequently does the Development Team inspect their progress and adapt their plan?<\/p>\n
It depends on the project.<\/p>\n
Daily<\/p>\n
Monthly<\/p>\n
Weekly<\/p>\n
The Development Team inspects their progress and adapts their plan daily during the Daily Scrum.<\/p>\n
Domain<\/p>\n
Daily Scrum<\/p>\n
It is job of the Product Owner to determine the number of PBIs for the Sprint Backlog.<\/p>\n
TRUE<\/p>\n
FALSE<\/p>\n
The Development Team decides on the number of PBIs<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
True or False: The Daily Scrum is an opportunity for the Scrum Master to provide detailed status updates on behalf of the Development Team.<\/p>\n
FALSE<\/p>\n
TRUE<\/p>\n
The Daily Scrum is a time for the Development Team members to synchronize and provide updates on their own progress, not for the Scrum Master to speak on their behalf.<\/p>\n
Domain<\/p>\n
Events<\/p>\n
True or False: The Scrum Master is responsible for ensuring that the Development Team follows the Scrum framework and adheres to its rules.<\/p>\n
TRUE<\/p>\n
FALSE<\/p>\n
The Scrum Master is indeed responsible for ensuring that the Development Team follows the Scrum framework and adheres to its rules. They coach the team, facilitate events, and help remove any impediments that may hinder the application of Scrum practices.<\/p>\n
Domain<\/p>\n
Roles<\/p>\n
The Scrum Master observes that the Development Team is not adhering to the agreed-upon Scrum events and time-boxes. What should the Scrum Master do to address this issue?<\/p>\n
Facilitate a discussion with the Development Team to understand the reasons behind the non-adherence and address any concerns.<\/p>\n
Collaborate with the Product Owner to review and adjust the Scrum events and timeboxes.<\/p>\n
Reinforce the importance of Scrum events and time-boxes, highlighting the benefits they provide.<\/p>\n
Enforce strict rules and penalties for nonadherence to Scrum events and timeboxes.<\/p>\n
In this scenario, the Scrum Master should facilitate a discussion with the Development Team to understand the reasons behind the non-adherence and address any concerns. They should also reinforce the importance of Scrum events and time-boxes, highlighting the benefits they provide.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
Which Scrum event involves the Development Team planning the work needed to deliver the Sprint Goal?<\/p>\n
Sprint Planning<\/p>\n
Daily Scrum<\/p>\n
Sprint Review<\/p>\n
Sprint Retrospective<\/p>\n
The Sprint Planning event involves the Development Team planning the work needed to deliver the Sprint Goal.<\/p>\n
Domain<\/p>\n
Sprint Planning<\/p>\n
The Product Owner is unable to attend the Sprint Planning. What should the Scrum Team do in this situation?<\/p>\n
Postpone the Sprint Planning until the Product Owner is available.<\/p>\n
Schedule another session to include the Product Owner in the Sprint Planning.<\/p>\n
Proceed with the Sprint Planning and make decisions based on the available information.<\/p>\n
Assign a proxy Product Owner to make decisions on behalf of the Product Owner.<\/p>\n
In this scenario, the Scrum Team should proceed with the Sprint Planning and make decisions based on the available information. They can schedule another session to include the Product Owner later if needed. Postponing the Sprint Planning may lead to delays, and assigning a proxy Product Owner should be avoided whenever possible.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
Who decides the structure of the Daily Scrum.<\/p>\n
Human Resources.<\/p>\n
Scrum Master.<\/p>\n
Product Owner<\/p>\n
Developers<\/p>\n
The Developers decides on whatever structure and techniques they want for the Daily Scrum.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
A Development Team member reports feeling overwhelmed and unable to complete their assigned tasks within the Sprint. What should the Scrum Master do?<\/p>\n
Facilitate a discussion with the Development Team to understand the challenges and explore potential solutions.<\/p>\n
Provide coaching and support to the Development Team member to improve their time management skills.<\/p>\n
Collaborate with the Product Owner to adjust the workload and reprioritize the Sprint Backlog.<\/p>\n
Encourage the Development Team member to work longer hours to meet the Sprint commitments.<\/p>\n
In this scenario, the Scrum Master should facilitate a discussion with the Development Team to understand the challenges faced by the overwhelmed team member. They should then explore potential solutions together, which may involve adjusting the workload, reprioritizing the Sprint Backlog, or providing coaching and support to improve time management skills.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n
The Development Team realizes that the Sprint Goal is no longer achievable due to unforeseen technical complexities. What should they do?<\/p>\n
Continue with the original Sprint Goal and accept the potential risk of not meeting it.<\/p>\n
Cancel the current Sprint and start a new one with a revised goal.<\/p>\n
Collaborate with the Product Owner to redefine the Sprint Goal and adjust the Sprint Backlog accordingly.<\/p>\n
Seek assistance from the Scrum Master to address the technical complexities.<\/p>\n
In this scenario, the Development Team should seek Scrum Master help in addressing of technical complexities. They should still aim for moving towards the Sprint Goal until the end of the Sprint.<\/p>\n
Domain<\/p>\n
Scrum<\/p>\n","protected":false},"excerpt":{"rendered":"
Scrum Master Mock Exam Simulator 1 – Results Question 1 The Development Team feels that they are unable to deliver a satisfactory Increment due to the lack of specific user stories. What should the Scrum Team do in response to this situation? Prioritize the most critical user stories and focus on delivering value. Review and […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"class_list":["post-13","post","type-post","status-publish","format-standard","hentry","category-psm-i-exam-list"],"_links":{"self":[{"href":"https:\/\/exam.kimson.us\/index.php?rest_route=\/wp\/v2\/posts\/13","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/exam.kimson.us\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/exam.kimson.us\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/exam.kimson.us\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/exam.kimson.us\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=13"}],"version-history":[{"count":3,"href":"https:\/\/exam.kimson.us\/index.php?rest_route=\/wp\/v2\/posts\/13\/revisions"}],"predecessor-version":[{"id":38,"href":"https:\/\/exam.kimson.us\/index.php?rest_route=\/wp\/v2\/posts\/13\/revisions\/38"}],"wp:attachment":[{"href":"https:\/\/exam.kimson.us\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=13"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/exam.kimson.us\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=13"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/exam.kimson.us\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=13"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}