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
  93% (52)
• B
  2% (1)
• C
  4% (2)
• D
  2% (1)

Explanation

In Scrum, a Sprint always ends with a potentially shippable product increment - meaning real, working, tested software. Even the very first Sprint is expected to deliver a small slice of functionality pulled from the Product Backlog, not just plans or paperwork.

• B is wrong because Scrum deliberately avoids big upfront architecture work. Design emerges incrementally across Sprints.
• C is wrong because team formation and role assignment happen before Sprint 1, during project initiation - not as a Sprint output.
• D is wrong because Scrum discourages rigid long-range release plans. The roadmap is refined continuously, not locked in after one Sprint.

Memory tip: Think of every Sprint - including Sprint 1 - as a mini-project that must end with working software. If it doesn't ship something testable, it's not a valid Sprint outcome.

No community discussion yet for this question.