ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
EpicUser Story TitleStoryAcceptance CriteriaValueEstimate (Story Points)Sprint
2
Prototype Development and Testing
 Build Interactive PrototypesAs a user i want to test your prototype and for it to be functional enough that i have an idea what your final product will be like.1. The prototype should be ready for us and other people to try out. It's not the final product, sure, but it should be functional enough that we can navigate through it and get a feel for how things will work. Think of it like a demo of a video game - it won't have all the levels or features, but it's enough to give us an idea of what to expect.
2. By the end of testing, We should have a pretty good understanding of what the final product will be like. If we are left with too many questions or uncertainties, then the prototype probably needs more work. It should be like watching a trailer for a movie - The testers should be excited and eager to see the whole thing.		$$17Current Sprint
3
Prototype Development and TestingConduct Usability TestsAs the product team we want the users to be able to provide feedback on what they love and hate with the prototype, so that it can be improved.1. We need a way for users to tell us what they think of the prototype. It could be a feedback form, a comment section, or even just an email address where they can send their thoughts. Just like how you'd rate a new song or movie you've just experienced, we need to know what you loved or didn't love about our prototype.
2. After the feedback is in, we should have a clear list of what users loved (so we can do more of it) and what they hated (so we can fix or get rid of it). It's like after watching a movie, you'd discuss what scenes worked and which ones fell flat - that's what we're aiming for, a concrete understanding of what needs improving.
$$20Current Sprint
4
Prototype Development and Testing
Incorporate User FeedbackAs the product team, we want to to incorporate user feedback in the prototype to refine the design and enhance the user experience.1. We need to take the feedback that our users have given us, and use it to make changes to the prototype. It's like getting notes on a draft of a novel; we take what people have said and use it to improve the next version. By the end of this task, the prototype should reflect the feedback we've received.
2. These changes shouldn't just be arbitrary, though. They should lead to a better user experience. So, if users told us that a certain feature was hard to find, we'll move it somewhere more noticeable. Or if they said something was confusing, we'll make it clearer. The end goal is to have a prototype that not only includes user feedback, but is demonstrably better because of it.		$$23Current Sprint
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100