-
Notifications
You must be signed in to change notification settings - Fork 4
/
secondReleaseReflection.html
597 lines (582 loc) · 24.8 KB
/
secondReleaseReflection.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
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
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
<!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>Bytes | Second Release Reflection</title>
<link rel="icon" href="/assets/common/logo.png" />
<link
rel="stylesheet"
href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.5.0/css/bootstrap.min.css"
/>
<link rel="stylesheet" href="/assets/common/css/teamStyle.css" />
<link
href="https://fonts.googleapis.com/css2?family=Raleway:wght@400;700&display=swap"
rel="stylesheet"
/>
<script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.5.1/jquery.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.5.0/js/bootstrap.min.js"></script>
</head>
<body>
<span id="navbar-placeholder"></span>
<div class="container my-4">
<div class="jumbotron mb-4">
<h1 class="display-4">Second Release Reflection</h1>
<p class="lead">
Here is our work for Deliverable 4.
<span class="d-md-block">
It contains changes to the product backlog, sprint backlogs, project velocity,
difficulties we encountered, use of contingency planning, progression from
D3 to D4, and client interactions.
</span>
</p>
</div>
<div class="card border-dark h-100 mb-4">
<div class="card-header">Product Backlog</div>
<div class="card-body">
<div class="m-0 px-3 h-100">
<p>
The product backlog changed since deliverable 3 to incorporate feedback
that we recieved from our teaching assistant. Additionally, we added user
stories relating to creating expiration dates for restaurant owner bingo
boards. We decided to add this feature so that restaurant owners can
notify customers that they plan to change the bingo board on a certain
date.
</p>
<p>
The product backlog is as follows or as a pdf <a href="/assets/d4/pdf/d4_backlog.pdf"> here</a>:
</p>
<img
src="/assets/d4/img/d4_backlog.png"
class="sprint-plan-img mb2"
/>
<img
src="/assets/d4/img/d4_backlog_completed.png"
class="sprint-plan-img mb2"
/>
</div>
</div>
</div>
<div class="card border-dark h-100 mb-4">
<div class="card-header">Release Plan</div>
<div class="card-body">
<div class="m-0 px-3 h-100">
<div>
<li>
The length of our sprints continue to be one week long.
</li>
<li>
We chose this length because we want to have a larger number of sprints
while still lining up with deadlines.
</li>
<li>
Our releases, including time taken for peer reviews, should fall
exactly on each deliverable’s due date, including the final due date
of the project.
</li>
</div>
</div>
</div>
</div>
<div class="card border-dark h-100 mb-4">
<div class="card-header">Sprint Plans</div>
<div class="card-body">
<div class="m-0 px-3 h-100">
<p> Three sprints were completed and are described in detail below. </p>
<hr>
<strong>Sprint 2: Backlog</strong>
<li>
For each user story in the Sprint Backlog, there are the following details:
</li>
<ul>
<li>
<b>Priorities</b> are labelled at the top of each card.
</li>
<li>
<b>Groupings of user stories</b> are shown through the labels.
</li>
<li>
<b>Story points</b> are shown in brackets in the user story
titles.
</li>
<li>
1 story point = 2 hours
</li>
</ul>
<hr>
<p>
The full sprint backlog is as follows or as a pdf <a href="/assets/d4/pdf/Sprint2_Backlog.pdf"> here</a>:
</p>
<hr />
<img
src="/assets/d4/img/Sprint2_Backlog_Part1.png"
class="sprint-plan-img mb2"
/>
<img
src="/assets/d4/img/Sprint2_Backlog_Part2.png"
class="sprint-plan-img mb2"
/>
<strong>Sprint 2: Intitial</strong>
<p>
The following images contain the initial task board, division of tasks,
and burndown chart for sprint 2, respectively.
</p>
<img
src="/assets/d4/img/d4_sprint2_initial_taskboard.png"
class="sprint-plan-img mb2"
/>
<img
src="/assets/d4/img/Sprint2_Initial_Task_Board.png"
class="sprint-plan-img mb2"
/>
<img
src="/assets/d4/img/Sprint2_Initial_Burndown.png"
class="sprint-plan-img mb2"
/>
<hr/>
<strong>Sprint 2: Final</strong>
<p>
The following images contain the final task board, division of tasks,
and burndown chart for sprint 2, respectively.
</p>
<img
src="/assets/d4/img/d4_sprint2_final_taskboard.png"
class="sprint-plan-img mb2"
/>
<img
src="/assets/d4/img/Sprint2_Final_Task_Board.png"
class="sprint-plan-img mb2"
/>
<img
src="/assets/d4/img/Sprint2_Final_Burndown.png"
class="sprint-plan-img mb2"
/>
<hr/>
<strong>Sprint 3: Backlog</strong>
<li>
For each user story in the Sprint Backlog, there are the following details:
</li>
<ul>
<li>
<b>Priorities</b> are labelled at the top of each card.
</li>
<li>
<b>Groupings of user stories</b> are shown through the labels.
</li>
<li>
<b>Story points</b> are shown in brackets in the user story
titles.
</li>
<li>
1 story point = 2 hours
</li>
</ul>
<hr>
<p>
The full sprint backlog is as follows or as a pdf <a href="/assets/d4/pdf/Sprint3_Backlog.pdf"> here</a>:
</p>
<hr />
<img
src="/assets/d4/img/Sprint3_Backlog_Part1.png"
class="sprint-plan-img mb2"
/>
<img
src="/assets/d4/img/Sprint3_Backlog_Part2.png"
class="sprint-plan-img mb2"
/>
<strong>Sprint 3: Intitial</strong>
<p>
The following images contain the initial task board, division of tasks,
and burndown chart for sprint 3, respectively.
</p>
<img
src="/assets/d4/img/d4_sprint3_initial_taskboard.png"
class="sprint-plan-img mb2"
/>
<img
src="/assets/d4/img/Sprint3_Initial_Task_Board.png"
class="sprint-plan-img mb2"
/>
<img
src="/assets/d4/img/Sprint3_Initial_Burndown.png"
class="sprint-plan-img mb2"
/>
<hr/>
<strong>Sprint 3: Final</strong>
<p>
The following images contain the final task board, division of tasks,
and burndown chart for sprint 3, respectively.
</p>
<img
src="/assets/d4/img/d4_sprint3_final_taskboard.png"
class="sprint-plan-img mb2"
/>
<img
src="/assets/d4/img/Sprint3_Final_Task_Board.png"
class="sprint-plan-img mb2"
/>
<img
src="/assets/d4/img/Sprint3_Final_Burndown.png"
class="sprint-plan-img mb2"
/>
<hr/>
<strong>Sprint 4: Backlog</strong>
<li>
For each user story in the Sprint Backlog, there are the following details:
</li>
<ul>
<li>
<b>Priorities</b> are labelled at the top of each card.
</li>
<li>
<b>Groupings of user stories</b> are shown through the labels.
</li>
<li>
<b>Story points</b> are shown in brackets in the user story
titles.
</li>
<li>
1 story point = 2 hours
</li>
</ul>
<hr>
<p>
The full sprint backlog is as follows or as a pdf <a href="/assets/d4/pdf/Sprint4_Backlog.pdf"> here</a>:
</p>
<hr />
<img
src="/assets/d4/img/Sprint4_Backlog_Part1.png"
class="sprint-plan-img mb2"
/>
<img
src="/assets/d4/img/Sprint4_Backlog_Part2.png"
class="sprint-plan-img mb2"
/>
<strong>Sprint 4: Intitial</strong>
<p>
The following images contain the initial task board, division of tasks,
and burndown chart for sprint 4, respectively.
</p>
<img
src="/assets/d4/img/d4_sprint4_initial_taskboard.png"
class="sprint-plan-img mb2"
/>
<img
src="/assets/d4/img/Sprint4_Initial_Task_Board.png"
class="sprint-plan-img mb2"
/>
<img
src="/assets/d4/img/Sprint4_Initial_Burndown.png"
class="sprint-plan-img mb2"
/>
<hr/>
<strong>Sprint 4: Final</strong>
<p>
The following images contain the final task board, division of tasks,
and burndown chart for sprint 4, respectively.
</p>
<img
src="/assets/d4/img/d4_sprint4_final_taskboard.png"
class="sprint-plan-img mb2"
/>
<img
src="/assets/d4/img/Sprint4_Final_Task_Board.png"
class="sprint-plan-img mb2"
/>
<img
src="/assets/d4/img/Sprint4_Final_Burndown.png"
class="sprint-plan-img mb2"
/>
</div>
</div>
</div>
<div class="card border-dark h-100 mb-4">
<div class="card-header">Estimated and Actual Project Velocities</div>
<div class="card-body">
<div class="m-0 px-3 h-100">
<div>
<strong>Estimated Project Velocities</strong>
<ul>
<li> Sprint 2: 46 story points
<li> Sprint 3: 35 story points
<li> Sprint 4: 25 story points
</ul>
<strong>Actual Project Velocities</strong>
<ul>
<li> Sprint 2: 46 story points
<li> Sprint 3: 35 story points
<li> Sprint 4: 25 story points
</ul>
</div>
</div>
</div>
</div>
<div class="card border-dark h-100 mb-4">
<div class="card-header">Difficulties We Encountered</div>
<div class="card-body">
<div class="m-0 px-3 h-100">
<div>
A difficulty that we encountered was figuring out a way to securely
connect our Java Android application to our Mongo database. We
conducted a lot of our own research, and reached out to our teaching
assistant and our client for support. After following tutorials, we
realized that many features that allowed Android applications to
connect to Mongo databases were no longer supported. Following this,
we tried to connect the application to the Mongo database using APIs;
however, this feature was not easily supported on the Android emulator.
After a conversation with our client, we decided to make our project
web-based so that we focus on the functionality.
</div>
</div>
</div>
</div>
<div class="card border-dark h-100 mb-4">
<div class="card-header">How Our Contingency Plan Was Useful/ How It Varied</div>
<div class="card-body">
<div class="m-0 px-3 h-100">
<div>
<p>
Thankfully, there was no need to utilize our contingency plan for this deliverable.
From the last deliverable, we were able to complete three sprints.
The first sprint we split according to web and application interfaces; however, due to setbacks,
our application became entirely web based. Thankfully, the conversion of application to web was
not difficult and did not set back the overall project. Overall, everyone was able to get their
work done on time.
</p>
<p>
The second sprint we split according to feature, where we would implement both
the frontend, backend and testing. In this sprint, everyone was able to finish their work on time.
In the third sprint there was only one front end and the rest of us implemented the backend features.
In this sprint, our estimated project velocity was low. More so, we were all able to finish the frontend
and backend implementation early in the sprint. Thus, we decided to clean up the appearance of our bingo board,
since in our meeting with the client, that was one of the major things they wanted us to fix. Because of this,
we allotted a new task for creating a mockup of the new interface and the implementation of it.
</p>
</div>
</div>
</div>
</div>
<div class="card border-dark h-100 mb-4">
<div class="card-header">How to Improve the Next Sprint Based on Experience With This Deliverable</div>
<div class="card-body">
<div class="m-0 px-3 h-100">
<div>
<p>
In this deliverable we learned how to properly peer review, so now we can provide better feedback
to our teammates on their code moving forward. We also gained feedback on our user stories,
so in the future, we can write better user stories. In addition, we have a clearer grasp of how
long it may take us to implement features individually, so calculating these may be easier in the future,
and if time permits, we can increase our project velocity for the upcoming sprints. Since we have taken
time to learn the tools needed, we can also work more quickly on these features.
</p>
</div>
</div>
</div>
</div>
<div class="card border-dark h-100 mb-4">
<div class="card-header">Project Progression from Deliverable 3 to 4</div>
<div class="card-body">
<div class="m-0 px-3 h-100">
<div>
At the end of Deliverable 3, our team released a simple bingo board interface
that allowed users to to select goals from a drop down list of predefined goals,
save them to their board, and clear their board to reselect goals. We expanded
upon the restaurant user functionality for Deliverable 4, and began development
for customers who will use the gamified system. In our latest release for
Deliverable 4, restaurant users and customers have dedicated interfaces to sign
up to make an account and login. Restaurant users have a customizable profile,
and can choose to create, view, and remove custom goals on a dedicated interface.
They can edit and save changes to their bingo board with pre-defined and customized
goals, as well as rewards from a pre-defined list. For customers, when they log in
they can view a list of restaurants with visible profiles, and choose to view the
full profile or the restaurant’s bingo board.
</div>
</div>
</div>
</div>
<div class="card border-dark h-100 mb-4">
<div class="card-header">How Deliverable 4 Differed from Deliverable 3</div>
<div class="card-body">
<div class="m-0 px-3 h-100">
<p>
Deliverable 3 and 4 differed for our team in terms of progress and end result.
For Deliverable 3, we allotted lots of time to learn and familiarize ourselves with
new tools such as MongoDB and Python Flask. While lots of progress was being made in
terms of learning and preparation for the project, the end result had very basic
functionality. We also found that having a sprint at the same time as a deliverable
caused us to spend more working time on the course than were actually being documented,
thus the project velocity may be too high for sprints that coincided with deliverables.
For the following sprints, we were able to utilize what we learned during the first
sprint to make significant progress.
</p>
<p>
The second and third sprints remained with high
project velocities because there were no deliverable due dates; we were able to use the
tools we learned in the first sprint to make progress on the project. The fourth sprint
occurred during the same week as Deliverable 4, so our team decided to reduce the velocity
to allot time for the report. As mentioned in the previous section, we added various
functionalities that built on what we produced in Deliverable 3. As a result, the end
result included more implemented features.
</p>
<p>
Our deliverable also differed because of feedback we received from the client. After we
demonstrated our first deliverable, the PickEasy team gave us feedback on our design; they
mentioned they wanted a different way to select goals instead of a dropdown list, and a more
aesthetically pleasing interface. We used this feedback to design the bingo board interface
that eliminated the drop down list in favour of clicking and dragging goals and rewards onto
the game board.
</p>
</div>
</div>
</div>
<div class="card border-dark h-100 mb-4">
<div class="card-header">Client Interactions</div>
<div class="card-body">
<div class="m-0 px-3 h-100">
<div>
<strong>Client Interactions and Questions Asked</strong>
<p>
PickEasy had some inconsistencies with the timing of their Thursday
meetings for a few weeks, so many of our interactions with our client
occurred over email. The following states the date of the email/meeting
and the questions we asked.
</p>
<ul>
<strong>June 19, 2020</strong>
<li>
Do you want there to be a feature where customer users can see all
their past rewards? Or is this an inventive feature?
</li>
<li>
Should there be accounts for restaurant owners?
</li>
<strong>July 4, 2020</strong>
<li>
We are creating an Android app using Android Studio and trying to
use an API to connect to MongoDB; we are having difficulties doing
so and were wondering if you had any experience with this.
</li>
<li>
The app is very large in size due to all the dependencies, and we
were wondering if you have any suggestions about deployment methods.
</li>
<li>
If we are unable to deploy an app because of the above limitations,
would a web-based loyalty program be an acceptable solution?
</li>
<strong>July 8, 2020</strong>
<li>
Should the bingo board be pre-filled with a randomized list of
goals for a restaurant owner?
</li>
<li>
What is your opinion of the bingo editor interface in terms of design?
</li>
<li>
We were thinking about having the goal tracking system be similar
to the coupon redemption system where a customer will present a QR
code and the restaurant owner can scan it to accept a goal, since
we do not have experience with Shopify or Square. Would this be fine?
</li>
<strong>July 10, 2020</strong>
<li>
Should the customer and restaurant user interfaces be completely
separate (with two individual domains) or should there be one main
page that has two options for the two different types of users?
</li>
</ul>
</div>
<hr />
<strong>Demo of First Release: Meeting Minutes</strong>
<p>
On July 8, 2020 at 3:00 p.m., we demonstrated our first release to our
client. The following states the demonstration agenda, questions asked, and
feedback from the client.
</p>
<ul>
<strong>Demonstration Agenda</strong>
<li>
Show login/create account pages
</li>
<li>
Show bingo editor
<ul>
<li>
Explain setup of bingo board; premade goals, goal boxes,
achievement paths, and rewards
</li>
</ul>
</li>
<li>
Show mockups for customer interface
</li>
</ul>
<ul>
<strong>Questions</strong>
<li>
What do you think of our bingo idea?
<ul>
<li>
Any suggestions?
<ul>
<li>
3x3, 4x4 etc.
</li>
</ul>
</li>
<li>
Should it be pre-filled with a randomized list of goals for a
restaurant owner?
</li>
<li>
What’s your opinion of the bingo editor interface in terms of
design?
</li>
</ul>
</li>
<li>
In terms of POS integration, we don’t have any experience with Shopify
or Square, so our group will most likely not be using these to track goals.
<ul>
<li>
Instead, we were thinking about having the goal tracking system
be similar to the coupon redemption system where a customer
will present a QR code and the restaurant owner can scan it
to accept a goal. Would this be fine?
</li>
</ul>
</li>
</ul>
<ul>
<strong>Feedback from Client</strong>
<ul>
<li>
Wants customizable goals by the owner, not pre-populated
</li>
<li>
We can use Qr codes for our coupon system, but prefers if we could
integrate the project with Shopify
</li>
<li>
5x5 game board with the drop down menu is fine
</li>
<li>
Game board set up is not aesthetically pleasing
</li>
<li>
Wants us to focus more on the execution and customer side
<ul>
<li>
How the users would see and interact with the board
</li>
</ul>
</li>
</ul>
</ul>
</div>
</div>
</div>
</div>
<script src="/assets/common/js/main.js"></script>
</body>
</html>