Scrum Professional Scrum Master I - PSM-I Exam Practice Test

A. Let the user documentation remain undone and accumulate until after the last development Sprint. It will then be done by any available technical writers.

B. The Developers on the Scrum Team should write the user documentation.

C. Form a separate team of technical writers that will work on an on-demand basis for the various Product Owners. Work order will be first in, first out.

D. Wait until you have a technical writer on your Scrum Team to take care of this.

A. Forecast the Product Backlog items that are most likely to meet the Sprint Goal and create the Sprint Backlog. Conclude Sprint Planning and start the development work. Continue to analyze, decompose, and create additional

B. Continue the Sprint Planning event past its timebox until an adequate number ot Product Backlog items are well enough understood for the Developers to make a complete forecast Then start the Sprint

C. During the next Sprint Retrospective discuss why this happened and what changes will make it less likely to recur.

D. Cancel the Sprint Send the entire team to an advanced Scrum training and then start a new Sprint

A. Developers on the Scrum Team work closely with business analysts, architects, developers, and testers who are not on the team.

B. The Scrum Team includes not only developers but also business analysts, architects, and testers.

C. The Scrum Team is a virtual team drawing from separate teams of business analysts, architects, developers, and testers.

D. The Scrum Team includes skilled individuals who together have all the skills necessary to create value each Sprint.

A. The Sprint Backlog.

B. The release plan.

C. The Sprint Goal

D. Sprint Review minutes.

A. Add security concerns to the definition of "Done".

B. Have the Scrum Team create Product Backlog items for each concern.

C. Postpone the work until a specialist can perform a security audit and create a list of security-related Product Backlog items.

D. Add a Sprint to specifically resolve all security concerns.

E. Delegate the work to the concerned department.

A. At least 7.

B. 9.

C. 7 plus or minus 3.

D. 3 to 9.

A. They are discussed, determined, and documented before the actual feature development Sprints.

B. They are added to the Product Backlog and addressed in early Sprints, while always requiring at least some business functionality, no matter how small.

C. They are addressed along with functional development of the product.

D. They are addressed by a separate team who is responsible for compliance issues.

A. All Sprints must be 1 month or less.

B. Sprint length is determined during Sprint Planning, and should hold the time it will take to code the planned features in the upcoming Sprint, but does not include time for any testing.

C. The length of the Sprint should be proportional to the work that is done in between Sprints.

D. Sprint length is determined during Sprint Planning, and should be long enough to make sure the Development Team can deliver what is to be accomplished in the upcoming Sprint.

E. It is best to have Sprints of consistent length throughout a development effort.

A. How many hours have been worked by each Development Team member.

B. How many Product Backlog items remain.

C. An estimate of the total work remaining for the Sprint.

D. How much effort has gone into a Sprint.

A. To present the Scrum Teams with insights and resources that help them improve.

B. To monitor the productivity of the Developers.

C. To continually monitor staffing levels of the Scrum Team.

D. To identify and remove people that are not working hard enough.

A. The Development Team and Product Owner.

B. The Development Team and Scrum Master.

C. The Scrum Team.

D. The Scrum Master and Product Owner.

E. The Development Team.

A. Maximizing velocity.

B. Meeting original scope projections.

C. Clear definition of requirements.

D. Minimizing dependencies between teams.

E. Making sure there's enough work for everyone on every team.