-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathskateboard.html
1211 lines (1144 loc) · 51.2 KB
/
skateboard.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
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!doctype html>
<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
<meta name="description"
content="User Story Mapping is a valuable tool that gives you strategies to view features alongside the problems they solve. It is a powerful approach that allows many people to prioritize features, regardless of technical expertise. Instead of planning our project as a building that we must build with a strong foundation, we begin to plan as a vehicle. This focus delivers the Most Valuable Features to the customer by answering the question, “What’s Your Skateboard?”">
<meta name="author" content="Emily Stamey">
<title>What's Your Skateboard?</title>
<meta name="apple-mobile-web-app-capable" content="yes">
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent">
<link rel="stylesheet" href="css/reveal.css">
<link rel="stylesheet" href="css/theme/white.css">
<link rel="stylesheet" href="css/my-style.css">
<!-- Theme used for syntax highlighting of code -->
<link rel="stylesheet" href="./node_modules/highlight.js/styles/zenburn.css">
<link rel="icon" type="image/x-icon" href="favicon.ico" />
<!--[if lt IE 9]>
<script src="lib/js/html5shiv.js"></script>
<![endif]-->
<!--<link rel="stylesheet" href="plugin/accessibility/helper.css">-->
<!-- Printing and PDF exports -->
<script>
var link = document.createElement( 'link' );
link.rel = 'stylesheet';
link.type = 'text/css';
link.href = window.location.search.match( /print-pdf/gi ) ? 'css/print/pdf.css' : 'css/print/paper.css';
document.getElementsByTagName( 'head' )[0].appendChild( link );
</script>
</head>
<body>
<div class="reveal">
<div class='footer'>
@elstamey <a href="https://joind.in/talk/654ee">https://joind.in/talk/654ee</a>
</div>
<div class="slides">
<section data-background-image="img/skateboard/skateboard_cover.jpg" class="titleblock">
<h3 class="title">What's Your Skateboard?</h3>
<h3>Emily Stamey</h3>
<h5 class="attrib">© photo by <a
href="https://www.flickr.com/photos/kwl/">Kenny Louie</a></h5>
</section>
<section>
<myRowBox>
<article>
<myColBox>
<article>
<!--<h3>Emily</h3>-->
<img src="img/me/developer.png" alt="developer">
</article>
<article>
<p>I'm a PHP developer</p>
<p>I've often worked directly with non-technical product owners and users</p>
<p>I work<u>ED</u> at a University</p>
</article>
</myColBox>
</article>
<article>
<myColBox>
<article>
<img src="img/inquest.svg">
</article>
<article>
<img src="img/wwcode.png">
</article>
<article>
<img src="img/trianglePHP_sm.jpg">
</article>
</myColBox>
</article>
</myRowBox>
<aside class="notes">
<li>I am Emily. I'm a php developer</li>
<li>I love community, so I help to build them at home.</li>
<li>I work at Inquest, a network security company based in Washington, DC. </li>
<li>I have worked a lot of places as a lone technical person, where it was helpful to speak on a non-technical level</li>
<li>I found this strategy very helpful in my recent position at a University</li>
<li>I haven't yet indoctrinated my coworkers at InQuest, so my examples mostly reference my time in the university</li>
</aside>
</section>
<section>
<footer>
<h3>Inspired By</h3>
</footer>
<footer>
<img src="img/skateboard/book.jpg">
</footer>
<aside class="notes">
<li>this book helped me a lot! It's a great read. It tells stories of his projects and gives a lot of helpful information</li>
<li>The illustrations are fantastic and really stick with you and help you change bad habits</li>
<li>Today we're going to cover the broad strokes of how user story maps work and the bigger ideas that can help you transform the way your team works. </li>
</aside>
</section>
<section>
<myTitleBox>
<h3>A Problematic Project Workflow</h3>
</myTitleBox>
<myColBox>
<article>
<ol>
<li>Research</li>
<!--<li>Build a prototype or wireframes</li>-->
<!--<li>Break the project into components or parts for implementation </li>-->
<li>Develop over several months</li>
<li>Deliver something</li>
<li>Learn if the big guess was correct</li>
</ol>
</article>
</myColBox>
<aside class="notes">
<li>Historically, we would have a brief meeting with the customer where we discussed client needs.</li>
<li>Then, we developed for a few months and delivered something that solved a problem, but didn't always solve THEIR problems or fulfill a need.</li>
<li>As we noticed this, we were looking for techniques to improve our communication and effectiveness.</li>
<li>User Story Mapping taught us a lot of things.</li>
</aside>
</section>
<section>
<myTitleBox>
<h3>The Client-Vendor Anti-Pattern</h3>
</myTitleBox>
<myColBox>
<img src="img/skateboard/client-vendor-anti-pattern.png">
</myColBox>
<aside class="notes">
</aside>
</section>
<!--<section>-->
<!--<myTitleBox>-->
<!--<h3>Learning Objectives</h3>-->
<!--</myTitleBox>-->
<!--<myColBox>-->
<!--<article>-->
<!--<ol>-->
<!--<li>What is a story map</li>-->
<!--<li>Why would you want to use it?</li>-->
<!--<li>Sketch a simple narrative flow</li>-->
<!--<li>Critique the example story map</li>-->
<!--</ol>-->
<!--</article>-->
<!--</myColBox>-->
<!--<aside class="notes">-->
<!--<p>Today we're going to cover the broad strokes of how user story maps work and the bigger ideas that can help you transform the way your team works. </p>-->
<!--<p>We're going to use a simple example to learn about building the story of your application. And I will show you a simple map that illustrates a project I'm working on.</p>-->
<!--</aside>-->
<!--</section>-->
<section>
<myTitleBox>
<h3>What's so great about this anyway?</h3>
</myTitleBox>
<myColBox>
<article>
<p>Communicate with non-technical users of the product</p>
<p class="fragment">Removes implementation from the discussion</p>
<p class="fragment">Objective-focused deliverables</p>
</article>
</myColBox>
</section>
<section>
<myTitleBox>
<h3>What is a Story Map?</h3>
</myTitleBox>
<myColBox>
<article>
<p>A diagram of a project that tells the story of the people and systems involved in a process.</p>
<p class="fragment">Detail is added as we learn more about the project</p>
<p class="fragment">The map can be built for an existing application or a new application.</p>
</article>
</myColBox>
<aside class="notes">
<li>A visual representation of the narrative flow of the application and processes that happen inside and outside the application.</li>
<li>(*) We can discover many details about the project </li>
<li>It highlights areas where you need to know more, and allows you to investigate that before you begin writing any code.</li>
<li>(*)This technique works for new and existing projects of any size.</li>
</aside>
</section>
<section>
<!--myTitleBox>
<h3>The Story Map</h3>
</myTitleBox-->
<myColBox>
<article>
<img src="img/skateboard/UserStoryMap.png" alt="Diagram of a User Story Map">
</article>
</myColBox>
<aside class="notes">
<li>Structurally, your map will look a bit like this.</li>
<li>The story flows from left to right</li>
<li>Details and steps are built from the top down.</li>
<li>You can show users of the application or even a background system process</li>
<li>When we get the full story described, we will begin to slice it into objectives. But we'll talk about that soon.</li>
</aside>
</section>
<section>
<myTitleBox>
<h3>Who should Story Map?</h3>
</myTitleBox>
<myColBox>
<article>
<p>Anyone who knows the process ... <span class="fragment">Not Just Developers</span> </p>
<p>At least one knowledgeable person from each group of stakeholders</p>
</article>
<article>
<img src="img/skateboard/who.png">
</article>
</myColBox>
<aside class="notes">
<li>Our apps often automated processes.</li>
<li>You want to bring to your story mapping discussion anyone who knows the processes you're automating.</li>
<li>(*)The room should actually have fewer programmers in the beginning unless they can be mostly silent. </li>
<li>Developers shouldn't fill in the story, but ask questions. </li>
<li>You cannot learn what your application is doing or supposed to be doing from people who don't use it to solve a problem they have.</li>
<li>This doesn't mean to keep them out of the loop of discovery, but their role is quieter here</li>
</aside>
</section>
<section>
<myTitleBox>
<h3>When to Story Map?</h3>
</myTitleBox>
<myColBox>
<article>
<img src="img/skateboard/when.png">
</article>
<article>
<p> </p>
<ul>
<li>When you have questions</li>
<li>Before You begin development</li>
</ul>
</article>
</myColBox>
<aside class="notes">
<li>Any time you are doing work and don't know the business process behind it. </li>
<li>The application can already exist, and you can use this to discover how new features or fixes should be implemented.</li>
</aside>
</section>
<section>
<myTitleBox>
<h3>Why Story Map?</h3>
</myTitleBox>
<myColBox>
<article>
<ul>
<li><em>Build shared understanding</em></li>
<li>Encourage full discovery before prototyping</li>
<li>Prioritize work to be done as a group</li>
</ul>
<p class="fragment"><strong>*Lowers problems with estimates and feature creep</strong></p>
</article>
</myColBox>
<aside class="notes">
<li>Story mapping lets you discover the full project</li>
<li>It highlights question areas, so you can answer them before development begins</li>
<li>enables the whole group to prioritize work and removes technical details from that discussion</li>
<li>(*)Discovery up front is less expensive than discovery in the middle of coding</li>
</aside>
</section>
<section>
<myTitleBox>
<h3>The big picture</h3>
</myTitleBox>
<myColBox>
<article>
<img src="img/skateboard/panorama.jpg" alt="Panorama of mountains, a town, and fields far into the distance">
</article>
</myColBox>
<header>
<h5 class="attrib">© photo by <a
href="https://www.flickr.com/photos/75487768@N04/8852553227/in/photolist-h8HTU3-JSeov4-h8HPQd-h8HWim-e5dUvX-5fR919-aB8Zp5-sbN2aF-n43Zp-nAUXRk-pw3kjL-qrSmhY-jSiBep-pYPm8B-eugDE4-4Tx3Rt-gUegPw-2Ri5uw-s8m2Qd-7j49P5-reXhVH-dCFW2M-eeoR86-8h1TkG-gsrTKm-4Nxays-dpe7UV-eDky7z-5j5d7W-oXXQy1-nY2L7h-mCqdmy-8RGz3D-nfTd25-6syxwQ-8zLvWC-4y5R9z-8gXBot-aATCWo-NvqGx-67vcv1-nxc6qH-bKhCEr-8w9uH9-65wnjj-5UX21y-3eov4o-BBsrb-668yVg-5W63ti">Barnyz</a></h5>
</header>
<aside class="notes">
<li>Discovery is like a large panorama. Many details are in the foreground, but if you look closely
at the countryside here, you can see even more in the landscape</li>
<li>way out there are mountains, and maybe your project is working towards them</li>
<li>You are figuring out which details are important to your application</li>
</aside>
</section>
<section>
<myTitleBox>
<h3>Focus during development</h3>
</myTitleBox>
<myColBox>
<article>
<img src="img/skateboard/narrow_focus.jpg" alt="Focus">
</article>
</myColBox>
<header>
<h5 class="attrib">© photo by <a
href="https://www.flickr.com/photos/theilr/6991409092/in/photolist-bDNNm5-dei4BD-hPt5SL-rhRZNN-8a7A6N-c8F4a1-4hHTYQ-bULsP8-nFZm8R-npMA17-a7MRtV-aksL6R-ojpRNK-JtLhP-d1uCHu-6akRDL-nAPrzR-9LPpCP-dMHo1G-4Tb69M-3fK6eh-kEZkGe-5X9ePa-4UNFbB-TFs2-pg3VkM-qmgY5N-8BEgCx-dkYvQv-oVWE1S-dcfhQG-8Zre24-cNJ6sW-eksvWx-e2Woij-6ARqEj-7NcVUv-oiqrhR-9rfVkW-5W1swG-pzBSHK-EZB1y-6bays9-fyamKk-rhgNfR-bvcx6h-4Gaj4U-6vy3ei-kUcpkp-dCVdy">Theilr</a></h5>
</header>
<aside class="notes">
<li>And when you begin to focus on that part, you let the other sections become blurry</li>
</aside>
</section>
<section>
<myTitleBox>
<h3>Where?</h3>
</myTitleBox>
<myColBox>
<article>
<p>A large, clear wall or whiteboard.</p>
<p>A place central to the team, at least in the beginning.</p>
</article>
</myColBox>
<aside class="notes">
<li>You'll want a large, clear wall or table that you can spread the sticky notes out.</li>
<li>It's ideal if it's a place central to your team</li>
<li>and if you can write on it</li>
<li>Sometimes you can put your map on a large piece of paper if your space to build it is different from a central team space to display it</li>
</aside>
</section>
<section>
<myTitleBox>
<h3>You'll need</h3>
</myTitleBox>
<myColBox>
<article>
<ul>
<li>painter's tape</li>
<li>markers</li>
<li>post-its (many colors & sizes)</li>
</ul>
</article>
<aside class="notes">
<li>painter's tape if you cannot write on the walls</li>
<li>post-its - we liked using regular ones for our story; XL for the objectives; and Tiny ones for the areas of risk</li>
<li></li>
</aside>
</myColBox>
</section>
<section>
<myTitleBox>
<h3>A simple example</h3>
</myTitleBox>
<myColBox>
<article>
<p>Use a familiar process that is <b><u>not</u></b> your project</p>
<p class="fragment">List five tasks you do in order to get to work. Put each one on a post-it provided.</p>
</article>
<article>
<img src="img/skateboard/sun.png" alt="goofy sun wearing sunglasses">
</article>
<aside class="notes">
<li>Let's do a little task flow</li>
<li>This isn't going to be shared with anyone</li>
<li>Think of the things you get yourself to and ready for work</li>
<li>Put each one on a post-it</li>
</aside>
</myColBox>
</section>
<section>
<!--<myTitleBox>-->
<!--<h3>My Morning at Work (first draft)</h3>-->
<!--</myTitleBox>-->
<myColBox>
<article>
<img src="img/skateboard/GotoWork1.png">
</article>
</myColBox>
<aside class="notes">
<li>For my first pass, I considered that I needed to drive to work.</li>
<li>I needed coffee, and I looked at my email and planned my work. </li>
<li>Before I begin work, especially coding, I do a quick meditation to help me remove distractions.</li>
</aside>
</section>
<section>
<myTitleBox>
<h3>Find Variations</h3>
</myTitleBox>
<myColBox>
<article>
<p>Pick 3 things that you did today that are different from your normal work routine.</p>
</article>
<article>
<img src="img/skateboard/sun.png" alt="goofy sun wearing sunglasses">
</article>
</myColBox>
<aside class="notes">
<li>Now some days are different because of scheduling or travel</li>
<li>try to think of 3 things you do on those exceptional days</li>
</aside>
</section>
<section>
<!--<myTitleBox>-->
<!--<h3>My Morning at Work (revised)</h3>-->
<!--</myTitleBox>-->
<myColBox>
<article>
<img src="img/skateboard/GoToWork2.png">
</article>
<!--<article>-->
<!--<p>There are variations between people, days of week, at-home and out-of-town work days</p>-->
<!--</article>-->
</myColBox>
<aside class="notes">
<li>Some days I have meetings, and that reminded me to check my calendar and attend meetings with my team</li>
<li>Some days I walked to get coffee nearby</li>
</aside>
</section>
<section>
<myTitleBox>
<h3>Building the narrative: Users</h3>
</myTitleBox>
<myRowBox>
<article>
<img src="img/skateboard/Users.png">
</article>
<article>
<p>Who are the Actors/Users in your morning routine?</p>
</article>
</myRowBox>
<aside class="notes">
<li>Normally, you'll be building this for a more involved story-line</li>
<li>But you probably have other actors/people in your morning</li>
<li>Maybe you drop your kid off for school one day.</li>
</aside>
</section>
<section>
<myTitleBox>
<article><h3>Building the narrative: Activity Groups</h3></article>
</myTitleBox>
<myRowBox>
<article>
<img src="img/skateboard/GoToWorkGroups.png">
</article>
<!--<article>-->
<!--<p>Sometimes several tasks can be grouped together</p>-->
<!--</article>-->
</myRowBox>
</section>
<section>
<myTitleBox>
<h3>Build The Story</h3>
</myTitleBox>
<myRowBox>
<article>
<img src="img/skateboard/GoToWork3.png" alt="My work story map">
</article>
</myRowBox>
<aside class="notes">
<p>Let's put them together to build a story of your getting to work!</p>
</aside>
</section>
<section>
<myTItleBox>
<h3>Learn More</h3>
</myTItleBox>
<myColbox>
<article>
<ul>
<li>Risk</li>
<li>Assumptions</li>
<li>Uncertainty</li>
</ul>
<p>If you cannot elaborate, mark it and revisit</p>
</article>
</myColbox>
<aside class="notes">
<li>Once you've fleshed out the summary of what you're describing, you need to fill in the detail</li>
<li>There are a lot of ways to add more detail, and figure out what you're missing</li>
<li>You'll look for areas of Risk. It doesn't have to stop planning, but it will help you to prepare</li>
<li>are there parts of your map that you're making assumptions about your application?</li>
<li>Are there things you don't know?</li>
<li>I usually mark assumptions and uncertainty with ? and Risk with a red post-it with an ! on it</li>
</aside>
</section>
<section>
<myTitleBox>
<h3>Clarifying Questions</h3>
</myTitleBox>
<myColBox>
<article>
<ul>
<li>What could we learn to replace <strong>risk</strong> with <strong>REAL</strong> information?</li>
<li>Do we <u>really</u> know what has been mapped, or did we fill in <strong>assumptions</strong>?</li>
<li>Are you sure about the story you're telling?</li>
</ul>
</article>
</myColBox>
<aside class="notes">
<li>To clear these marks off your map, you can ask yourself, your customers/users, etc questions</li>
<li>You want to replace the risk with real information; and where you cannot remove the risk, you plan to do less work at the time you take on that risk</li>
<li>Are the stories and tasks in your map based on REAL information? Or were there assumptions being made?</li>
<li>How certain are you about the story you're telling?</li>
</aside>
</section>
<section>
<myTitleBox>
<h3>Label These</h3>
</myTitleBox>
<myColBox>
<article>
<img src="img/skateboard/UserStoryMap2.png">
</article>
</myColBox>
<aside class="notes">
<li>As you're developing the story, it will begin to look like this</li>
<p>Anatomy of a Story Map</p>
<ul>
<li>Users => actors in the story</li>
<li>Backbone => user activities</li>
<li>Walking Skeleton(blue) => major user tasks</li>
<li>User Stories => add detail to the story</li>
<li>Releases => organize and prioritize stories</li>
<li>Priorities => Lower Priority stories sink to the bottom</li>
</ul>
</aside>
</section>
<section>
<myTitleBOx>
<h3>Thorough Discovery</h3>
</myTitleBOx>
<myRowBox>
<article>
<ul>
<li>Understand the full process
<ul>
<li>Understand "why" steps are needed in the process</li>
<li>Talk about things inside and outside of the app</li>
</ul>
</li>
</ul>
</article>
</myRowBox>
<aside class="notes">
<li>This whole process is investigation, and it should include your customers and users. Remember this isn't implementation</li>
</aside>
</section>
<section>
<myTitleBOx>
<h3>Thorough Discovery</h3>
</myTitleBOx>
<myRowBox>
<article>
<ul>
<li>Simplify and lower risk at implementation
<ul>
<li>Lowers the questions at the phase of implementation</li>
<li>Limits Feature Creep (beginning implementation w/o understanding, new features come in)</li>
<li>Better estimates </li>
</ul>
</li>
</ul>
</article>
</myRowBox>
<aside class="notes">
<li>That understanding and investigation reduces the number of questions when you're implementing the code</li>
<li>It should limit feature creep because when you're writing that code, you can focus only on the section in the current slice.</li>
<li>The more complete your investigation in the beginning, the more time you save at implementation. </li>
<li>And all of this saves you money, too</li>
</aside>
</section>
</section>
</section>
<section>
<myTitleBox>
<h3>More than just adding stories</h3>
</myTitleBox>
<myRowBox>
<article>
<blockquote class="style4">
If the only thing you create while making sense of a big opportunity is more, small stories, <b>you're doing it wrong</b>.
<br>- Jeff Patton
</blockquote>
</article>
</myRowBox>
<aside class="notes">
<li>Jeff Patton makes a really good point later in the book. He's characterizing these details you're fleshing out as opportunities to deliver value on your project</li>
<li>While early exploration may be adding stories, this isn't all that is involved. You aren't just breaking the stories into smaller pieces.</li>
</aside>
</section>
<section>
<myTitleBox>
<h3>Four Steps to Discovery</h3>
</myTitleBox>
<myColBox>
<article>
<ol>
<li>Frame the idea</li>
<li class="fragment">Understand Customers and Users</li>
</ol>
<aside class="notes">
<li>Frame the discussion to set the boundaries of your exploration, keeps you from going off in the weeds. Your team will be better able to stop discussions that don't solve the problem you're focusing on.</li>
<li>(*)Sketch simple personas to build an understanding of your users. Helpful for looking at the application through the eyes of your users when you are not a user of the product</li>
</aside>
</article>
</myColBox>
</section>
<section>
<myTitleBox><h3>Simple Persona</h3></myTitleBox>
<myColBox>
<article>
<img src="img/skateboard/SimplePersona.png">
</article>
</myColBox>
</section>
<section>
<myTitleBox>
<h3>Four Steps to Discovery</h3>
</myTitleBox>
<myColBox>
<article>
<ol>
<li>Frame the idea</li>
<li>Understand Customers and Users</li>
<li>Envision your solution</li>
<li class="fragment">Minimize the plan</li>
</ol>
<aside class="notes">
<li>Visualize your user interface to build shared understanding.</li>
<li>Avoid product arrogance -> the difference between what you THINK the customer needs and what they actually need</li>
<li>(*)Be picky. You aren't helping anyone if you are agreeing to do everything</li>
<li>Trash aggressively the ideas that don't achieve the outcomes you most want.</li>
<li>You and this discovery team have to be specific about what is valuable</li>
</aside>
</article>
</myColBox>
</section>
<section>
<myColBox>
<article>
<img src="img/skateboard/UserStoryMap2.png" alt="Anatomy of a User Story Map">
</article>
</myColBox>
<aside class="notes">
<li>In order to pull these stories down into slices, we need to prioritize them</li>
<li>The book gives many different ways to help you with this.</li>
</aside>
</section>
<section>
<myTitleBox>
<h1>Priorities</h1>
</myTitleBox>
<!--<myRowBox>-->
<!--<article>-->
<!--<ul>-->
<!--<li>Loosely prioritize stories based on everyone's needs</li>-->
<!--<li>Lower priorities sink</li>-->
<!--</ul>-->
<!--</article>-->
<!--</myRowBox>-->
<aside class="notes">
<li>Priorities are important, but they're often dictated by people in "power"</li>
<li>But we have seen that this gets swayed heavily by the person who wants the feature. Politics are heavy at a university.</li>
<li>Loosely prioritize stories based on everyone's needs</li>
<li>Lower priorities sink</li>
</aside>
</section>
<section>
<myTitleBox>
<h3>Prioritizing the Project</h3>
</myTitleBox>
<myRowBox>
<article>
<ul>
<li>Who will use this product?</li>
<li>What steps must they accomplish for success?</li>
<li>Remove/postpone the rest</li>
</ul>
</article>
</myRowBox>
<aside class="notes">
<li>Sometimes these discussions of priorities can become personal. And it is helpful to refocus sometimes</li>
<li>It's helpful to think about the user's needs and the purpose of the app</li>
<li>Any features that aren't delivering recognizable value should be removed or postponed indefinitely</li>
<li>note: This does not mean you deprioritize refactoring or code improvements. making your product stable and reliable can be included</li>
</aside>
</section>
<section>
<myTitleBox>
<h3>Prioritizing Features</h3>
</myTitleBox>
<myRowBox>
<article>
<ul>
<li><strong>Differentiator</strong> - feature sets you apart from competition</li>
<li><strong>Spoiler</strong> - moves in on someone else’s differentiator</li>
<li><strong>Cost reducer</strong> - reduces organizational costs</li>
<li><strong>Table stakes</strong> - feature necessary to compete</li>
</ul>
</article>
</myRowBox>
<aside class="notes">
<li>You're going to be discussing these priorities with customers, users and developers. And sometimes they have competing interests</li>
<li>Jeff Patton recommends a labeling strategy that is really great at specifying what type of priority it is</li>
<li>Some features will help you stand above the competition; those are differentiators</li>
<li>Some will level the playing field if a competitor has a feature you didn't already have</li>
<li>Some features with save time or money and are therefore cost reducers</li>
<li>Finally, table stakes are features that you ABSOLUTELY must have in order to compete in your market</li>
</aside>
</section>
<section>
<myTitleBox>
<h3>Focus on Outcomes</h3>
</myTitleBox>
<myRowBox>
<article>
<ul>
<li>What are you hoping to do with your application?</li>
<li>Prioritize features based on the problem they solve </li>
<li>Implement only what solves the problem or meets the objective</li>
</ul>
</article>
</myRowBox>
<aside class="notes">
<li>It is so much easier to discuss priorities from a goal-oriented perspective of problem-solving</li>
<li>You have the opportunity to focus the features specifically on that goal, and it weeds out a lot of the nice-to-have tasks that slip in from the side</li>
</aside>
</section>
<section>
<myTitleBox>
<h3>Prototyping</h3>
</myTitleBox>
<aside class="notes">
<li>This strategy helped influence the way I plan projects and also how I prototype</li>
</aside>
</section>
<section>
<myTitleBox>
<h3>Prototyping</h3>
</myTitleBox>
<myColBox>
<article>
<ul>
<li>What is the smallest thing you could build to prove/disprove an assumption?</li>
<li>Sketch & prototype to test viability of the solution</li>
<li>Aim for less than minimum, get feedback, and iterate often</li>
<li>When you give prototype to <strong>development partners</strong> you can include metrics to see what they actually do</li>
</ul>
</article>
</myColBox>
<aside class="notes">
<li>When you begin developing for the project, a prototype is a lightweight way to prove you are moving in the right direction.
You may plan to implement a feature with a little extra time for exploration.</li>
<li>{read the questions}</li>
<li>And this leads me to one of my favorite concepts from this book...</li>
</aside>
</section>
<section>
<myTitleBox>
<h3>MVP vs. Most Valuable Features</h3>
</myTitleBox>
<myColBox>
<article>
<p>Focus on releasing valuable features every time.</p>
<p>Sometimes we plan features in a chronological order</p>
<p>Or we divide the project into components</p>
</article>
</myColBox>
</section>
<section>
<myTitleBox>
<h3>When we build in pieces</h3>
</myTitleBox>
<myColBox>
<article>
<img src="img/skateboard/car_in_parts.jpg" alt="Building a car in parts">
</article>
</myColBox>
<aside class="notes">
<li>When we divide it into parts, a lot of times it's like these</li>
<li>These parts are useful to a car, but on their own, they aren't terribly useful</li>
</aside>
</section>
<section>
<myTitleBox>
<h3>When we build in parts</h3>
</myTitleBox>
<myColBox>
<article>
<img src="img/skateboard/painting_in_parts.jpg" alt="Painting in parts">
</article>
</myColBox>
<aside class="notes">
<li>Painters don't build in parts, either</li>
</aside>
</section>
<section>
<myTitleBox>
<h3>Instead we want to <u>iterate</u>!</h3>
</myTitleBox>
<myColBox>
<article>
<img src="img/skateboard/mvp.png" alt="Building a car in parts">
</article>
</myColBox>
<aside class="notes">
<li>when we iterate, choosing features by the problems they solve, we are building applications that can get us from point a to point b</li>
<li>the skateboard won't get you there very quickly, but it's mobile!</li>
<li>And if we aren't trying to build the next huge application, blinding ourselves with millions of features, we can accomplish so much mORE!</li>
</aside>
</section>
<section>
<myColBox>
<article>
<img src="img/skateboard/iterative_mona_lisa.jpg" alt="Painting in layers as the image becomes cleared">
</article>
</myColBox>
<aside class="notes">
<li>This is how a painting is constructed, unless it's one of those paint-by-numbers sets</li>
<li>the artist begins with a sketch and gradually adds more detail</li>
</aside>
</section>
<section>
<myTitleBox>
<h3>Strategies</h3>
</myTitleBox>
<myColBox>
<article>
<img src="img/skateboard/opening_mid_end_game.jpg" alt="Opening Mid and Eng-game Strategies stacked on top of each other">
</article>
</myColBox>
<aside class="notes">
<!--<h4><b>opening game strategy</b></h4>-->
<!--<ul>-->
<!--<li>When the number of features is too large, you can cut a slice across that gives you the minimum end-to-end functionality;</li>-->
<!--<li>It doesn’t solve all user’s stories, but it affects the largest number of stories.</li>-->
<!--<li>With this product, they can have test data, begin testing it for load, and see how it will work</li>-->
<!--</ul>-->
<!--<h4><strong>midgame strategy</strong></h4>-->
<!--<ul>-->
<!--<li>fill in and round out features</li>-->
<!--<li>support optional steps</li>-->
<!--<li>implement tough business rules</li>-->
<!--<li>continue testing the product usability</li>-->
<!--</ul>-->
<!--<h4><strong>endgame strategy</strong></h4>-->
<!--<ul>-->
<!--<li>refine: make it look more polished and efficient </li>-->
<!--<li>it’s here that you’ll apply the feedback from users.</li>-->
<!--</ul>-->
</aside>
</section>
<!--<section>-->
<!--<myColBox>-->
<!--<article>-->
<!--<img src="img/skateboard/MapWithObjectives.png">-->
<!--</article>-->
<!--</myColBox>-->
<!--</section>-->
<!--<section>-->
<!--<myColBox>-->
<!--<article>-->
<!--<img src="img/skateboard/award_money_happy.png">-->
<!--</article>-->
<!--</myColBox>-->
<!--</section>-->
<!--<section>-->
<!--<myColBox>-->
<!--<article>-->
<!--<img src="img/skateboard/award_money_failure.png">-->
<!--</article>-->
<!--</myColBox>-->
<!--</section>-->
<section>
<myTitlebox>
<h3>opening game strategy</h3>
</myTitlebox>
<myColBox>
<article>
<ul>
<li>When the number of features is too large, you can cut a slice across that gives you the minimum end-to-end functionality;</li>
<li>It doesn’t solve all user’s stories, but it affects the largest number of stories.</li>
<li>With this product, they can have test data, begin testing it for load, and see how it will work</li>
</ul>
</article>
</myColBox>
</section>
<section>
<myTitleBox>
<h3>midgame strategy</h3>
</myTitleBox>
<myColBox>
<article>
<ul>
<li>fill in and round out features</li>
<li>support optional steps</li>
<li>implement tough business rules</li>
<li>continue testing the product usability</li>
</ul>
</article>
</myColBox>
</section>
<section>
<myTitleBox>
<h3>endgame strategy</h3>
</myTitleBox>
<myColBox>
<article>
<ul>
<li>refine: make it look more polished and efficient </li>
<li>it’s here that you’ll have feedback from users that can be applied.</li>
</ul>
</article>
</myColBox>
</section>
<section data-background-image="img/boots/scholarship_application.jpg" data-background-size="100%" data-background-position="center">
<aside class="notes">
<li>I'm going to tell you about the Scholarships Project</li>
<li>It organizes requirements for scholarships to be awarded to Students in the COE</li>
</aside>
</section>
<section>
<section data-background-image="img/boots/fall_student.png" data-background-size="60%" data-background-position="center">
<aside class="notes">
<li>The Scholarship cycle went a little like this</li>
<li>Fall, students began applying for the NEXT academic year.</li>
<li>Their application shared details that would help them match for scholarships</li>
</aside>
</section>
<section data-background-image="img/boots/jan_foundation.png" data-background-size="60%" data-background-position="center">
<aside class="notes">
<li>The Engineering Foundation maintains relationships with donors and manages the money</li>
<!--<li>Donors specify the type of student portfolio they want to give the money, based on majors, gpa, and sometimes clubs</li>-->
<!--<li>We call this Scholarship criteria. Some is required and some is optional</li>-->
<li>Spring, Foundation figures out the money that is available for each Scholarship</li>
<li>They let the Selection Committee know how much money is available to be awarded</li>
</aside>
</section>
<section data-background-image="img/boots/mar_selection.png" data-background-size="60%" data-background-position="center">
<aside class="notes">
<li>Selection committee finds candidates to receive that money.</li>
<!--<li>They match against the required criteria and try to evaluate the students who have the greatest financial need</li>-->
</aside>
</section>
<section data-background-image="img/boots/aug_financial_aid.png" data-background-size="60%" data-background-position="center">
<aside class="notes">
<li>Scholarship Coordinator gives the information to Financial Aid. </li>
</aside>
</section>
<section data-background-image="img/boots/fall_money.png" data-background-size="60%" data-background-position="center">
<aside class="notes">
<li>After reporting the awards to Financial Aid, a letter is sent to the students telling them the aid they will receive next year.</li>
<li>At the beginning of the semester, they will receive the money</li>
</aside>
</section>
</section>
<section data-background-image="img/boots/scholarships_diagram.png" data-background-size="60%" data-background-position="center">
<aside class="notes">
</aside>
</section>
</section>
<section data-background="img/skateboard/story_map_overview.jpg">
</section>
<!--<section data-background="img/skateboard/story_map_overview2.jpg">-->
<!--</section>-->
<!--<section data-background="img/skateboard/story_map1.jpg">-->
<!--</section>-->
<section data-background="img/skateboard/story_map2.jpg">
</section>
<section data-background="img/skateboard/story_map3.jpg">
</section>
<section>
<myTitleBox>
<h3>Summary</h3>
</myTitleBox>
<myColBox>
<article>
<ul>
<li>A tool you can use with non-technical subject matter experts, customers, etc</li>
<li>A visual guide for managing your workload</li>
<li>Focus on objectives when you prioritize</li>
<li>Plan to deliver a usable product at each deliverable</li>
</ul>
</article>
</myColBox>
<aside class="notes">
<li>This is a fantastic way to talk to your development partners!</li>
<li>a visual map for your team to reference</li>
<li>you will focus on solving problems and delivering real value!</li>
</aside>
</section>
<!--<section>-->
<!--<h1 id="questions-">Questions?</h1>-->
<!--</section>-->
<!--<section>-->
<!--<h1 id="maybe-slides">maybe slides</h1>-->
<!--</section>-->
<!--<section>-->
<!--<h3 id="user-story">User Story</h3>-->
<!--<p>"A user story is a tool used in Agile software development to capture a-->
<!--description of a software feature from an end-user perspective. The user-->