Please enable JavaScript.

Coggle requires JavaScript to display documents.

Specification (User stories and scenarios) (User scenarios (Context…

- - - - Can easily develop
      - Independent or at least only loosely couple with one another
    - - Details of the stories should also be negotiable
      - User stories leave room for the product owner, stakeholders and team to negotiate the details
      - Expect change in agile
    - - User stories need to be valuabe to a customer, user or both
    - - User stories should be estimatable by the team that will design, built and test
      - The development team can know how much they can get done
    - - User stories worked on in sprints should be small
      - Can be finished within a sprint
    - - User stories should be testable in a binary way - pass/fail
  - - - Must have
      - Should have
      - Could have
      - Would have
- - - - Asking specific questions about them
      - Understand the underlying objectives
  - - - Normal scenario: a course of interaction where everything proceeds as normally expected
      - Abnormal scenario: capture desired interaction sequences under exceptional circumstances that depart from the normal course of interaction