What is the expected outcome of the first Sprint on a project?

Question

Options

• AA few working, tested features from the Product Backlog
• BArchitecture and high-level design of the Product
• CAssignment of the team, Product Owner and Scrum Master
• DA well-defined release plan for the Product

• A
  88% (15)
• B
  6% (1)
• C
  6% (1)

Explanation

Scrum defines a Sprint as a time-boxed iteration that must deliver a potentially shippable product increment - meaning real, working, tested functionality pulled from the Product Backlog. That's why A is correct: the whole point of Sprint 1 is to produce something tangible and functional, not just plans or paperwork.

• B is wrong because Scrum explicitly rejects up-front architecture phases ("Big Design Up Front"). Design emerges iteratively across Sprints.
• C is wrong because team formation and role assignment happen before Sprint 1 begins, during project setup - not as an outcome of the Sprint itself.
• D is wrong because a "release plan" is a traditional waterfall artifact. Scrum uses a Product Backlog and Sprint Goals instead; long-range release planning is not a Sprint deliverable.

Memory tip: Think of each Sprint as a mini-product delivery - if you can't demo working software at the end, you didn't complete the Sprint. The word "increment" is key: Scrum Sprints always increment (add to) a working product.

No community discussion yet for this question.