A. The result of an exhaustive architectural planning effort

B. A fundamental architectural problem found in an existing application

C. A decision made by a systems architect to settle disagreement amongst the developers

D. A small development activity to learn about technical elements of a proposed solution

A. Important, recurring non-functional requirements can be added to the definition of done

B. Before the release, they should be tested and validated in a hardening sprint

C. Scrum is for functional, frontend development only

D. Handle them during a risk mitigation phase before development

E. Specific expectations can be used as acceptance criteria to specific product backlog items

F. Include them in the Product Backlog

A. Definition of done

B. Sprint planning outcome

C. Product goal

D. Sprint goal

A. The Developers may forecast less overall work in Sprint 8.

B. The Scrum Master adds additional Developers for Sprint 8.

C. There is nothing wrong. The Developers will present all Product Backlog items selected for Sprint 7 at the end of the Sprint.

D. The Developers put incomplete Product Backlog items back into the Product Backlog for re-ordering.The Product Owner may ask the Developers to complete the unfinished Product Backlog items from Sprint 7 in Sprint 8.

E. The Developers carry over incomplete Sprint Backlog items from Sprint 7 to Sprint 8 and monitor the Sprint 8 burn-down chart. As soon as deviation from trends is detected, the Developers work with the Product Owner to negotiate remaining work.

F. Stakeholders will encourage the Scrum Team to estimate better during the Sprint 8 Planning Meeting.

A. False

B. True

A. All of these

B. Sprint planning

C. Sprint

D. Daily Scrum

E. Sprint review

F. Sprint retrospective

A. Each team should have its own automated build

B. Each team's automated build is integrated toward the end of the sprint

C. Developers should perform a combination of local and private builds

D. There is one automated build for all teams

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

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

C. A decomposition of all product backlog items into tasks for future sprint backlog lists

D. Additions features in a usable state that complement those delivered in previous iterations

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

A. False

B. True

A. Code review is done

B. Regression tests pass

C. Code coverage 90%

D. Acceptance tests pass

E. The product is released at the end of every sprint

A. Developers that have to pay college debt

B. A term representing the eventual consequences of poor technical choices

C. The money an organization owes to tool and hardware vendors

D. Code that hasn't been documented

A. Code that has been peer reviewed

B. Code with minimal duplication

C. Code that has not been peer reviewed (yet)

D. Code with low cyclomatic complexity

A. commitment, empiricism, focus, respect

B. commitment, focus, openness, respect and courage

C. transparency, inspection, adaptations

D. commitment, focus, respect, transparency and courage

A. As much as needed without endangering the Sprint goal

B. 25% of the sprint capacity

C. 10% of the senior developers

A. The Developers.

B. The Product Owner.

C. The Scrum Team.

D. The Scrum Master.