Lecture 6

Question 1

User Story (User Story)

Answer 1

An agile requirement stated as 1-2 sentences of plain English from the user’s point of view, and describes a unit of desired functionality.

• the basis for defining the functions a biz. sys. provides
• captures WHO, WHAT, and WHY. [NOT the how (implementation)]
• Customer/Prod. Owner prioritized
• Before implementation, devs. should meet with the cust. due to story interpretation challenges and/or change in requirements.
• Each User Story MUST have 1+ acceptance tests to determine when the User Story is “done”

Question 2

[User Story] Syntax

Answer 2

“As a , I want , [so that ]”.

[] == optional.
<> == fill in the blank.

Question 3

[User Story] Creation

Answer 3

3 C’s Formula
Card, Conversation, Conformation.

• Card: A physical token giving tangible form to the user story,
• Conversation: Exchange of thoughts, opinions, and feelings over time (when story is estimated, iteration planning meetings, etc). Mostly verbal!
• Confirmation: Story tests (acceptance tests for the product owner). Specified by the P.O who collaborates with the team to make these.

Question 4

[User Story] Characteristics

Answer 4

I.N.V.E.S.T

• I: independent
• N: Negotiable
• V: Valuable
• E: Estimable
• S: Small
• T: Testable (Very similar to the “Verifiable” characteristic of good requirements!)

Question 5

[User Story] Acceptance Criteria

Answer 5

Conditions that product must satisfy to be accepted by the user/customer, or a consuming system.

• clear pass/fail results
• specify both func. and non-func. requirements
• applicable at epic, feature, and story levels
• constitute “doneness”
  Verification and Validation answered by this.

Question 6

[User Story] Acceptance Criteria Syntax

Answer 6

Given
When
Then

Question 7

[User Story] Acceptance Tests

Answer 7

The functional testing of a User Story by an Agile team.

• customer specifies testing scenarios when user story has been correctly implemented
• user stories must have at least 1 acceptance test
• acceptance tests are black box
• sometimes used as regression tests prior to product release
• new acceptance tests must be created for each iteration, or dev. team will report zero progress!

Question 8

[User Story] Acceptance Tests Characteristics

Answer 8

• High level
• intent, not a solution
• Independent of implementation