A. Enough "Ready" Product Backlog to fill the Sprint
B. There are no such pre-conditions
C. A clear but negotiable business objective for the Sprint
D. A clear and non-negotiable Sprint Goal
E. A fully refined Product Backlog
F. Formal budget approval to conduct another Sprint
A. The Scrum Master as he/she is responsible for the Developers' productivity
B. The Product Owner as he/she is responsible for the product's success
C. The development organization (or Scrum Team if none is available from the development organization)
D. The Scrum Team, in a collaborative effort where the result is the common denominator of all members' definitions
A. Time to market.
B. Customer satisfaction.
C. Productivity.
D. Velocity.
E. Budget spent.
A. The executive stakeholders should determine if the Sprint should continue
B. The Product Owner should cancel the Sprint
C. The Scrum Master should cancel the Sprint
A. It may vary depending on the project
B. It becomes more complete over time
C. It is the exit criteria to determine whether a Product Backlog item is complete
D. It is defined by the Scrum Master
A. Never, unless agreed to by the change request
B. Only after a Sprint Review if agreed to by the stakeholders
C. At any time when done by the Product Owner or at the Product Owner's discretion
D. Only during Product Backlog refinement sessions if the Product Owner is present
A. There is no Sprint 0 in Scrum
B. Create a complete Product Backlog
C. Work on team development
D. Define a reference architecture
A. Increase transparency.
B. Guide the Developers on how many Product Backlog items to select for the Sprint.
C. Describe the purpose, objective, and time-box of each Scrum event.
D. Create a shared understanding of when work is complete.
E. Describe the work that must be done before the Sprint is allowed to end.
