최신 PSM-I 무료덤프 - Scrum Professional Scrum Master I

A. Identifying high priority process improvements for the next Sprint.

B. How the team collaborates.

C. The order of items in the Product Backlog.

D. Documenting acceptance criteria for items in the next Sprint.

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

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

C. They are built by a separate team through the creation of an architectural runway.

D. They are implemented along with functional development of the product.

A. Make sure the release department understands these requirements, but it is not the

B. Manage them during the Integration Sprint prior to the Release Sprint.

C. Assign them to the lead developers on the team.

D. Ensure every Increment meets them.

A. Develop at least one piece of functionality.

B. Create an increment of potentially releasable software.

C. Analyze, describe, and document the requirements for the subsequent Sprints.

D. Make up a plan for the rest of the project.

E. Define the major product features and release plan architecture

A. When the sales department has an important new opportunity.

B. When it becomes clear that not everything will be finished by the end of the Sprint.

C. When the Development Team feels that the work is too hard.

D. When the Sprint Goal becomes obsolete.

A. Make up a plan tor the rest of the project

B. Analyze, describe, and document the requirements for the subsequent Sprints.

C. Build at least one piece of valuable functionality.

D. Create at least one valuable, useful Increment

E. Define the major product features and a release plan architecture.

A. The Product Owner.

B. The Scrum Master, or the Scrum Master may have the Developers do it.

C. The Scrum Master.

D. The business analyst who represents the Product Owner.

A. It depends.

B. Each Development Team uses its own but must make their definition clear to all other teams so the differences are known.

C. All Development Teams must have a definition of "Done" that makes their combined work potentially releasable.

D. Each Development Team defines and uses its own. The differences are discussed and reconciled during a hardening Sprint.

A. Complete the project within the date and cost as calculated by the Product Owner.

B. Do all of the development work, except for specialized testing that requires additional tools and environments.

C. Turn Product Backlog items into an Increment of potentially releasable product functionality.

A. As much as it can fit into the Sprint. Any remaining work will be transferred to a subsequent Sprint.

B. As much as it has told the Product Owner will be done for every Product Backlog item it selects in conformance with the definition of "Done".

C. A proportional amount of time on analysis, design, programming, testing, and documentation.

D. All development work and at least some testing.

A. As long as needed.

B. 1 day

C. 4 hours and longer as needed.

D. 2 hours for a monthly Sprint.

E. 4 hours for a monthly Sprint.

A. Immediately after the conclusion of the previous Sprint.

B. When the Product Owner is ready.

C. Immediately following the next Sprint Planning.

D. The Monday following the Sprint Review.

A. Sprint Retrospective.

B. Members must be stand up at the Daily Scrum.

C. All of the above.

D. Release planning.

E. Sprint Burndown Chart.

A. What went wrong in the last Sprint and what to do differently this Sprint.

B. What can be done and how to do it.

C. How conditions have changed and how the Product Backlog should evolve.

D. Who is on the team and what team member roles will be.

E. What to do and who will do it.

A. A decomposition of all Product Backlog items into tasks for future Sprint Backlog lists.

B. Additional features in a usable state that complement those delivered in previous iterations.

C. An automated test suite to verify functionality delivered in previous iterations.

D. A new user interface design for functionality delivered in previous iterations.

E. UML diagrams that describe how to deliver functionality in future iterations.