forked from Yannael/incremental-development
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathuser-stories-case-study.html
75 lines (70 loc) · 3.02 KB
/
user-stories-case-study.html
1
2
3
4
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
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>User Story Case Study</title>
</head>
<body>
<h1 id="user-stories-case-study">User Stories Case Study</h1>
<p>Learning to break a whole application into user stories takes experience.</p>
<p>This is easier to learn by practicing with existing applications instead of ones you dream up.</p>
<hr>
<p>The first step to mastering user stories is to practice asking and answering these questions:</p>
<ol>
<li><strong>What are the different components on the user interface?</strong></li>
<li><strong>What interaction does each component enable a user to have with your website?</strong></li>
<li><strong>How do these stories depend on each other?</strong></li>
<li><strong>What is a logical order for building these stories?</strong></li>
</ol>
<p>Let's see these questions in action with a simple website:</p>
<ul>
<li><a href="https://tomato-timer.com/" target="_blank">tomato timer!</a></li>
</ul>
<p>Here are some possible answers to these questions based on the Tomato Timer</p>
<p>(but not the only answers! there are many ways to split a project):</p>
<hr>
<h3>1. What are the different components on the user
interface?</h3>
<ul>
<li>There is a red button that says "stop"</li>
<li>There is a white button that says "reset"</li>
<li>There are some numbers</li>
<li>There is a green button that says "start"</li>
</ul>
<h3>2. What interaction does each component enable a user to have with your website?</h3>
<ul>
<li>A user can stop the count-down without resetting the time</li>
<li>A user can stop the count-down and set it back to 25:00</li>
<li>A user can see how much time is left</li>
<li>A user can start (or restart!) the count-down</li>
</ul>
<h3>3. How do these stories depend on each other?</h3>
<ul>
<li>You can't stop a count-down unless it is started</li>
<li>It is not practical to be able to reset the count-down every time you want to stop it</li>
<li>You can see how much time is left without being able to start the timer (even if this isn't very useful :)
</li>
<li>There is no point to have a count-down until there is a time to see</li>
</ul>
<h3>4. What is a logical order for building these stories?</h3>
<ol>
<li>A user can see how much time is left</li>
<li>A user can start (or restart!) the count-down</li>
<li>A user can stop the count-down without resetting the time</li>
<li>A user can stop the count-down and set it back to 25:00</li>
</ol>
<hr>
<blockquote>
<p>
<a href="https://github.com/elewa-student/User-Centered-Development" target="_blank">
Another worked example for further practice
</a>
</p>
</blockquote>
<hr>
<hr>
<a href="https://hackyourfuture.be" target="_blank"><img
src="https://user-images.githubusercontent.com/18554853/63941625-4c7c3d00-ca6c-11e9-9a76-8d5e3632fe70.jpg"
width="100" height="100"></a>
</body>
</html>