Question # 1
During a Sprint Review, the Product Owner determines that she is going to release the current Increment to production. The stakeholders ask to stop the Sprint to react more quickly to the user feedback that is expected after this release. The Product Owner prefers to continue the Sprint to make progress with the next release. You facilitate a discussion on how to proceed. What are two acceptable results of this discussion? (choose two answers) | A. Continue sprinting but shorten the Sprint length to allow for shorter feedback loops. | B. Stop sprinting and let the Developers work on new customer requests as they arise. | C. Continue sprinting and include the customer feedback in the Product Backlog. | D. Continue sprinting but allow customer feedback to change the Sprint Goal within the Sprint. |
Continue sprinting but shorten the Sprint length to allow for shorter feedback loops. Continue sprinting and include the customer feedback in the Product Backlog.
Explanation:
The Sprint Review is an event that inspects the outcome of the Sprint and determines future adaptations. The Product Owner has the authority to release the Increment to production at any time, but this does not mean that the Sprint has to be stopped or changed. The stakeholders can provide feedback and suggestions for the product, but they cannot interfere with the Sprint Goal or the Sprint Backlog within the Sprint.
The Scrum Team can decide to:
Continue sprinting but shorten the Sprint length to allow for shorter feedback loops (A), which is a valid option if the Scrum Team agrees that this will improve their agility and value delivery. However, this should not be done frequently or arbitrarily, as it may disrupt the rhythm and focus of the team.
Continue sprinting and include the customer feedback in the Product Backlog©, which is the most appropriate option as it respects the empirical nature of Scrum and allows the Product Owner to prioritize and order the Product Backlog based on new insights and stakeholder needs.
Question # 2
You are a Scrum Master entering an organization that wants to "evolve" their product development to Scrum. The organization's teams are organized into component teams. This means that teams address one single application layer only (for example, front end, middle tier, back end, and interfaces).
You introduce the concept of feature teams, where teams have the skills to work on multiple layers throughout a Sprint and deliver working software every Sprint. What are two things you take into consideration when moving away from component teams toward feature teams? (choose two answers) | A. You cannot do Scrum without feature teams. Do not continue adopting Scrum until teams are reorganized in feature teams. | B. Productivity, in terms of lines of code or story points, will probably suffer during the transition, although even then delivery of business value is still likely to Increase. | C. Feature teams will require time to become productive as people from the different layers and components become accustomed to working and delivering unified functionality together, as one Scrum Team. | D. With feature teams, it is easier to calculate and compare the productivity per team. Incentives on productivity are likely to speed up the transition to feature teams, and therefore the adoption of Scrum. |
Productivity, in terms of lines of code or story points, will probably suffer during the transition, although even then delivery of business value is still likely to Increase. Feature teams will require time to become productive as people from the different layers and components become accustomed to working and delivering unified functionality together, as one Scrum Team.
Explanation:
B: Productivity, in terms of lines of code or story points, will probably suffer during the transition, although even then delivery of business value is still likely to increase. This is a realistic expectation, as the teams will need to learn new skills, collaborate more effectively, and adapt to changing requirements. However, the benefit of feature teams is that they can deliver working software that provides value to the customers and stakeholders every Sprint, rather than waiting for the integration of different components.
C: Feature teams will require time to become productive as people from the different layers and components become accustomed to working and delivering unified functionality together, as one Scrum Team. This is a natural consequence of changing the team structure and culture, as the teams will need to overcome some challenges and conflicts, build trust and rapport, and establish a shared vision and goal. The Scrum Master can help the teams with this transition by facilitating communication, coaching, and mentoring.
Question # 3
In an environment where user acceptance testing is required before the Increment can be put into production, a development manager proposes to have user acceptance testing done every third Sprint, because the feedback from the user acceptance tests are disrupting work in Sprints. Is this a good idea? | A. It depends on what is stated in their Definition of Done. | B. No, the Increment will not be transparent and the feedback loop is too long. | C. Yes, the Scrum Team is a self-managing team. | D. Yes, the Scrum Team needs stability in the Sprint. |
No, the Increment will not be transparent and the feedback loop is too long.
User acceptance testing is a process of verifying that the product meets the user's needs and expectations. It is an important feedback mechanism that helps the Scrum Team validate their assumptions, inspect the value and quality of the Increment, and adapt their plans accordingly. Scrum requires that the Increment be transparent, meaning that it is observable and understandable by anyone with a stake in the outcome. Scrum also requires that the feedback loop be short, meaning that the Scrum Team can receive and respond to feedback quickly and frequently.
Therefore, it is not a good idea to have user acceptance testing done every third Sprint, because:
The Increment will not be transparent (B), meaning that the Scrum Team and the stakeholders will not have a clear and shared understanding of what has been done and what remains to be done. This may lead to misalignment, confusion, or conflict over the product vision, scope, and quality.
The feedback loop is too long (B), meaning that the Scrum Team will not be able to inspect and adapt based on the user's feedback in a timely manner. This may lead to wasted effort, missed opportunities, or reduced value delivery.
The other options are not correct because:
It does not depend on what is stated in their Definition of Done (A), which is a formal description of the state of the Increment when it meets the quality standards required for the product. The Definition of Done does not dictate how or when user acceptance testing should be done, but rather what criteria must be met for the Increment to be considered ''Done''.
The Scrum Team is a self-managing team , which means that they have the autonomy and authority to organize and manage their own work within the boundaries of Scrum. However, this does not mean that they can ignore or postpone user feedback, which is essential for delivering value and satisfying customer needs.
The Scrum Team needs stability in the Sprint (D), which means that they need to have a clear and consistent Sprint Goal, Sprint Backlog, and Definition of Done throughout the Sprint. However, this does not mean that they need to avoid or resist user feedback, which is a source of learning and improvement for the product and the process.
Question # 4
You are a Scrum Master employed by the IT department. The IT manager considers adopting Scrum tor a new project He wonders however, what the value is in having all team members attend this meeting called "Daily Scrum" every day. The organization already has its employees attending so many mandatory meetings. What are two outcomes of the Daily Scrum you inform him about, to express the importance of the Daily Scrum? (choose two answers) | A. During the Daily Scrum the Developers will bring up problems that are hindering their progress, and tor which they nave no means to resolve, this provides an opportunity to resolve those impediments. | B. The Daily Scrum serves tor the Developers to report to you, as a Scrum Master, all updates on the tasks to the Sprint, as registered in the Sprint Backlog. You can then use the team's updates to plan their work tor the next day, making sure that every team member is assigned the right tasks. | C. Through the snort, daily alignment of the Daily Scrum the Developers build and improve a shared understanding of the most important work to be undertaken in the next 24 hours, to achieve the best possible progress toward the Sprint Goal. This daily opportunity to inspect and adapt Will enable the Developers to tackle any unforeseen circumstances that might otherwise disrupt the team's progress. | D. During the Daily Scrum, the Developers need to update the Scrum board with their current status and progress, at a task level. This is crucial to ensure that the IT manager can go up to the room at any time and view the team's actual progress. | E. The Developers will produce a status report indicating what each individual has done the past working day, and now much time that has taken. The accumulated reports will support discussing how the Sprint went at the Sprint Review meeting. It will provide detailed insights into the accuracy of estimates versus actual time spent, which can be used to create better estimates at the subsequent Sprint Planning meeting. |
During the Daily Scrum the Developers will bring up problems that are hindering their progress, and tor which they nave no means to resolve, this provides an opportunity to resolve those impediments. Through the snort, daily alignment of the Daily Scrum the Developers build and improve a shared understanding of the most important work to be undertaken in the next 24 hours, to achieve the best possible progress toward the Sprint Goal. This daily opportunity to inspect and adapt Will enable the Developers to tackle any unforeseen circumstances that might otherwise disrupt the team's progress.
Explanation:
The Daily Scrum is a 15-minute event for the Developers of the Scrum Team to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. The Daily Scrum is not a status meeting, but a way for the Developers to collaborate and self-organize around the most important work for the next 24 hours. The Daily Scrum also provides an opportunity for the Developers to identify and communicate any impediments that are hindering their progress, and request help from the Scrum Master or other team members to resolve them.
References:
What is a Daily Scrum?| Scrum.org
What Is the Daily Scrum?| A Guide to the Daily Event - Scrum Alliance
Question # 5
During the Sprint Review the Product Owner introduces the functionality that is likely to be done over the next Sprints. The Chief Security Officer reminds everyone that through the envisioned functionality, sensitive personal user data will be stored. This might be the subject of external security audits. He reminds everyone of important non-functional requirements with regards to security. These were not applicable and not considered previously What are two effective ways the Scrum Team can manage these high-security concerns? (choose two answers) | A. They are discussed, determined, and documented in parallel Sprints to not disturb the actual feature development Once analyzed, they should be applied to the work already done before further feature development can continue. | B. The impact of these security concerns on past and future work needs to be determined before new Sprints can start. A list of security-related Product Backlog items needs to be passed on to the Product Owner before starting the next Sprint. | C. They are added to the Product Backlog and addressed throughout the next Sprints, combined with creating the business functionality in those Sprints, no matter how small that business functionality. | D. During the Sprint Retrospective, the Scrum Team assesses how to add these expectations to the Definition of Done so every future Increment will live up to these requirements. If needed they can work with external specialists to better understand the requirements. | E. They should be managed by a separate specialist team in a parallel Sprint, so they can be specifically resolved through an improved application design without hindering functional development. |
They are added to the Product Backlog and addressed throughout the next Sprints, combined with creating the business functionality in those Sprints, no matter how small that business functionality.
During the Sprint Retrospective, the Scrum Team assesses how to add these expectations to the Definition of Done so every future Increment will live up to these requirements. If needed they can work with external specialists to better understand the requirements.
Scrum PSM-II Dumps - Latest All Questions Access
Exam Code: PSM-II
Exam Name: Professional Scrum Master II
- 90 Days Free Updates
- Scrum Experts Verified Answers
- Printable PDF File Format
- PSM-II Exam Passing Assurance
Get 100% Real PSM-II Exam Dumps With Verified Answers As Seen in the Real Exam. Professional Scrum Master II Exam Questions are Updated Frequently and Reviewed by Industry TOP Experts for Passing Professional Scrum Master Exam Quickly and Hassle Free.
Scrum PSM-II Exam Questions
Struggling with Professional Scrum Master II prep? Get the edge you need!
Our carefully crafted PSM-II dumps give you the confidence to ace the exam. We offer: -
Up-to-date Professional Scrum Master practice questions: Stay current with the latest exam content.
-
PDF and test engine formats: Choose the study tools that work best for you.
-
Realistic Scrum PSM-II practice exams: Simulate the real exam experience and boost your readiness.
Pass your Professional Scrum Master exam with ease. Try our study materials today!
Ace your Professional Scrum Master exam with confidence!
We provide top-quality PSM-II exam prep materials that are:
-
Accurate and up-to-date: Reflect the latest Scrum exam changes and ensure you are studying the right content.
- Comprehensive: Cover all exam topics so you do not need to rely on multiple sources.
- Convenient formats: Choose between PDF files and online Professional Scrum Master II practice tests for easy studying on any device.
Do not waste time on unreliable PSM-II practice exams. Choose our proven Professional Scrum Master study materials and pass with flying colors.
Try Dumps4free Professional Scrum Master II Exam 2024 PDFs today!
Professional Scrum Master II Exams
-
Assurance
Professional Scrum Master II practice exam has been updated to reflect the most recent questions from the Scrum PSM-II Exam.
-
Demo
Try before you buy! Get a free demo of our Professional Scrum Master exam dumps and see the quality for yourself. Need help? Chat with our support team.
-
Validity
Our Scrum PSM-II PDF contains expert-verified questions and answers, ensuring you're studying the most accurate and relevant material.
-
Success
Achieve PSM-II success! Our Professional Scrum Master II exam questions give you the preparation edge.
How to Pass Scrum PSM-II Exam?
-
1 ![](images/registration-ico.webp)
Buy Dumps
Get the most accurate Scrum prep with our exam-focused PSM-II dumps. Real questions and verified answers – the ultimate tool for passing on your first try.
-
2 ![](images/doc-ico.webp)
Preparation
Prep for the Professional Scrum Master exam from the comfort of your home. Download our PSM-II practice questions and start studying today!
-
3 ![](images/get-start-ico.webp)
Success
Don't be surprised on exam day! Our accurate Professional Scrum Master II practice questions match the real exam format. Prepare at home and walk into your exam with ease.
|