Structure Example - User Stories in Agile Development
Template illustrating how Testpad might be used to plan tests from sprint to sprint as user stories are produced, modified and removed. Descriptions could be copy and pasted verbatim from other documentation, or transcribed into more 'test' sounding statements.
Click on cells in this column to record your results
0001
Sprint 1
0002
User Story 1
0003
aspect A
0004
aspect B
0005
aspect C
0006
additionally verify this
0007
additionally verify that
0008
User Story 2
0009
aspect D
0010
aspect E
0011
aspect F
0012
explore detail 1
0013
explore detail 2
0014
// User Story 3 (removed in sprint 2, say)
0015
Sprint 2
0016
User Story 4
0017
aspect G
0018
Sprint 3
0019
User Story 5
0020
aspect H
0021
aspect I
0022
User Story 6
0023
aspect J
0024
aspect K
0025
Sprint 4
0026
User Story 7
0027
aspect L
0028
aspect M
0029
User Story 8
0030
aspect N
0031
aspect O
0032
User Story 9
0033
aspect P
0034
aspect Q
0035
Sprint 5
0036
User Story 10
0037
aspect R
0038
aspect S
0039
// Where Sprints are more complicated, it often makes sense to use a whole Script or whole Project per Sprint, starting each Sprint with a copy of the previous Script(s) and modifying them inline with the new features