최신 PSM-II 무료덤프 - Scrum Professional Scrum Master level II (PSM II)

A. Ask the Developers and the Product Owner what problem they are going to solve by altering the Definition of Done during the Sprint to remove regression testing. Will this raise transparency or improve quality?

B. Disagree with the decision and tell them that having a stringent Definition of Done is important for the quality of the product, and they need to follow it.

C. Ask the Developers and the Product Owner if removing regression testing from the Definition of Done allows the team to produce useful and valuable Increments at the end of every Sprint?

D. Agree with altering the Definition of Done, if both the Developers and Product Owner agree.

A. It is only a forecast and may change within the Sprint as more is learned.

B. It helps increase focus.

C. The Scrum Team discusses openly about alternative ways to reach it.

D. The Scrum Team commits to it.

E. If it does not seem achievable, the Developers have the courage to tell the Product Owner.

F. The Product Owner respects the opinions of the Developers about whether they can achieve the Sprint Goal.

A. Take the opportunity to create more energy and team spirit and encourage everyone to participate in the applause.

B. Tell the Product Owner your concerns about how his behavior may impact the Developers, and ask him to stop attending the Daily Scrum for some time.

C. Coach the Scrum Team about the purpose of the Daily Scrum.

D. Nothing. The Scrum Master does not attend the Daily Scrum.

A. Coach the Developers on why a daily frequency is important as an opportunity to update the Sprint Plan and how it helps the team organize work toward achieving the Sprint Goal.

B. Acknowledge and support this self-managing team's decision

C. Help the Developers understand that lowering the frequency of communication will only increase the feeling of disconnect between the team members.

D. Have the Developers vote to make sure there is consensus within the team

A. It creates transparency into the state of the Increment when it is inspected at the Sprint Review.

B. It guides the Developers when creating a forecast at the Sprint Planning.

C. It is a checklist to inspect whether the Developers have performed their tasks by the end of a Sprint.

D. It serves to track the percent completeness of a Product Backlog item during the Sprint.

E. It provides a template for the documentation of the product Increment.

F. During the Sprint it helps the Developers identify the work remaining for an Increment to be ready for release by the end of a Sprint.

A. There is one Product Owner for each product (five in total). Each Product Owner may delegate to others for specific value, capabilities, and functionality within their product. The five Product Owners share and align work via Product Backlog.

B. There are as many Product Owners as needed to analyze, document, and explain expectations and requirements with all Scrum Teams.

C. There is one Product Owner for all five products. This person may not delegate work to others for specific value, capabilities, and functionality, given these are all the Product Owner's individual responsibility.

D. There is one Product Owner responsible for all five products. This person may delegate work to others for specific value, capabilities, and functionality within each product to scale their accountability.

A. The Product Owner decides by providing each team with its own Product Backlog.

B. The Scrum Team with the highest velocity pulls items from an overall Product Backlog first

C. They must be selected from one Product Backlog in such a way that each Scrum Team has an equal volume of requirements per Sprint.

D. The Scrum Teams pull in work from a shared Product Backlog in agreement with the Product Owner and the other teams.

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. 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.

C. 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.

D. 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.

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.