-
Notifications
You must be signed in to change notification settings - Fork 15
Expand file tree
/
Copy pathdaily-announcements-fall-2014.html
More file actions
1796 lines (1530 loc) · 105 KB
/
Copy pathdaily-announcements-fall-2014.html
File metadata and controls
1796 lines (1530 loc) · 105 KB
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 lang="en">
<head>
<meta charset="utf-8">
<title>CS 4970: daily-announcements slide set</title>
<meta name="description" content="A set of slides for a course on Program and Data Representation">
<meta name="author" content="Aaron Bloomfield">
<meta name="apple-mobile-web-app-capable" content="yes" />
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
<link rel="stylesheet" href="../../slides/reveal.js/css/reveal.min.css">
<link rel="stylesheet" href="../../slides/reveal.js/css/theme/default.css" id="theme">
<link rel="stylesheet" href="../../slides/css/slp.css">
<link rel="stylesheet" href="../../slides/reveal.js/lib/css/zenburn.css"><!-- For syntax highlighting -->
<script><!-- If the query includes 'print-pdf', include the PDF print sheet -->
if( window.location.search.match( /print-pdf/gi ) ) {
var link = document.createElement( 'link' );
link.rel = 'stylesheet';
link.type = 'text/css';
link.href = '../../slides/reveal.js/css/print/pdf.css';
document.getElementsByTagName( 'head' )[0].appendChild( link );
}
</script>
<!--[if lt IE 9]>
<script src="../../slides/reveal.js/lib/js/html5shiv.js"></script>
<![endif]-->
<style>
.reveal li {
font-size:80%;
line-height:120%;
}
</style>
</head>
<body>
<div id="dhtmlwindowholder"><span style="display:none"></span></div>
<div class="reveal">
<!-- Any section element inside of this container is displayed as a slide -->
<div class="slides">
<section data-markdown><script type="text/template">
# CS 4970
### Capstone Practicum I
### Fall 2014
<center><small>[Aaron Bloomfield](http://www.cs.virginia.edu/~asb) / [aaron@virginia.edu](mailto:aaron@virginia.edu) / [@bloomfieldaaron](http://twitter.com/bloomfieldaaron)</small></center>
<center><small>Repository: [github.com/aaronbloomfield/slp](http://github.com/aaronbloomfield/slp) / [↑](../../slides/index.html) / <a href="daily-announcements.html?print-pdf"><img class="print" width="20" src="../../slides/images/print-icon.png"></a></small></center>

## Daily Announcements
</script></section>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<section>
<section>
<h2>Wednesday, December 3rd, 2014</h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/trolley_problem.png" title="For $5 I promise not to orchestrate this situation, and for $25 I promise not to take further advantage of this ability to create incentives." alt="Trolley Problem">
<p class="center"><a href="http://xkcd.com/1455/">xkcd # 1455</a></p>
</section>
<section data-markdown><script type="text/template">
## Wednesday, December 3rd, 2014
- We are at the start of iteration 6
- Customer meetings in 1 line: reports (1 sentence) but not w/Jamie; name tags
- Everybody got their TPS reports submitted!
- Everybody can view the submitted reports through the [reporting system](https://libra.cs.virginia.edu/slp/)
- Details can be found in the [course introduction slide set](../../slides/fall/01-intro.html), specifically [here](../../slides/fall/01-intro.html#tpsreport)
- If your system requires authentication (as most will, eventually), you need to create accounts (of all user levels) for Jamie and myself
- Don't forget to report your hours!!! This is a course requirement!
- Iteration evaluations out through iteration 4
- Please read it over, as many received poor progress ratings because I couldn't log in or find the work that was done
- Once that is fixed, come see me (for iteration 2) or Jamie (for the other iteraitons) during office hours or the meeting, and we will re-do the evaluation
- We expect iteration 5 evaluations to be out next Monday
- Iteration 6 will be slightly different, as there will be an end of the semester evaluation in lieu of iteration 6's evaluation
- It is *very bad* of your CI testing does not work
- Today is a group work day, and our last class meeting until January 12th
</script></section>
<section data-markdown><script type="text/template">
## Final Projects: Tutorials
- The project is to write a tutorial on *something* that you had to work through this semester
- Something that, if you had had a tutorial ahead of time, would have saved you time or effort
- It must be something that there does not exist a tutorial already online
- They are due at the end of the normal final exam period (Mon, Dec 15 @ noon)
- Everybody will have to one (individually) or convert two (from an older format)
- Note that conversion means making sure that it still works!
- The format will be [Markdown](https://help.github.com/articles/markdown-basics/)
- There is a repo that everybody will fork: [uva-slp/tutorials](https://github.com/uva-slp/tutorials)
- You may want to unwatch it to avoid receiving all the notifications...
- The [README.md](https://github.com/uva-slp/tutorials/blob/master/README.md) contains instructions for topic reservation and how to complete the tutorial (which is dine via a [pull request](https://help.github.com/articles/creating-a-pull-request/))
- This is meant to take about 3 hours, which is the time a final exam would take
- This will count in lieu of your final exam, which will be a non-insignificant part of your final grade
- In an effort to keep this sane for us, will are going to insist that you please follow the directions laid out in that tutorial
</script></section>
<section data-markdown><script type="text/template">
## Upcoming Iteration Goals
- Future iterations this semester will have fewer explicit goals
- For all iterations, you should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
- Some specific iteration goals follow:
- Iteration 3: show the wireframe to the customer, get their feedback, iterate on the design
- Iteration 4: implement continuous integration testing
- See the details in the [Continuous Integration Testing](../../slides/fall/11-ci-testing.html) slide set
- Iteration 5: get a preliminary system that implements the minimum requirements working
- This means that most (if not all) of your minimum requirements should be implemented!
- Iteration 6: get a final system that implements the minimum requirements working
- Keep in mind that iteration 6's goal is what you are working toward this entire semester!
</script></section>
<section data-markdown><script type="text/template">
## Updated things to be completed this semester
- Finish development through iteration 6
- This means that your CI testing had better be green!
- Everybody should continue to report your hours
- Leads: submit your weekly and TPS reports on the next two Mondays
- Email your customer to start using the system
- More info on this from me soon; you will also have to CC me on that
- Complete your tutorial(s) and submit via a pull request
- Complete the last end-of-phase survey (released on Sun, Dec 14)
- Have your final group meeting/presentation with Jamie (details to follow)
- Upload your STS prospectus (if you are using SLP for your technical project)
- Last night I emailed all those who have not yet done so
Note that you will receive an incomplete if any of these things are not done when I submit the final grades!
</script></section>
<section data-markdown><script type="text/template">
## Github Story Points<br>Hall of Shame
Remember that *all* issues (even closed ones) must have a story points tag. The following do not:
- Alzheimers: issue #103
- Hope's Legacy: issue #291
You can give a tag of "story-points-none" if the task is not worth any story points
</script></section>
<section data-markdown><script type="text/template">
## Holiday Break
- I will do my best not to bother you until we return. But...
- If something goes wrong with the system, or the customer can't use it, then I'll start sending emails
- The customer may (or may not) email you
- In the directions for the "hand-off", I'll suggest a way to phrase it so that they give you all of their comments once you return
- My hope is that I don't have to contact anybody (I want a break from course work too...)
</script></section>
<section data-markdown><script type="text/template">
## Preview of next semester
- There will be 8 iterations instead of 6
- The first 5 will be development; the last 3 deployment
- 6 and 7 person groups will have a different phase schedule as a result
- Desired requirements are due by March 23rd, 2015 (the end of iteration 11)
- Iterations will have specific deliverables
- Deployment plan, test plan, transition plan, etc.
- Some documentation during the last 3 iterations
- Technical report, user manual, installation instructions, programming reference
- I will guide you through all of these
- And, of course, lots of progress on your projects!
</script></section>
</section>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<section>
<section>
<h2>Monday, December 1st, 2014</h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/done.png" title="I'm sorry, but the author of this Facebook comment clearly believes you were." alt="Done">
<p class="center"><a href="http://xkcd.com/1454/">xkcd # 1454</a></p>
</section>
<section data-markdown><script type="text/template">
## Monday, December 1st, 2014
- We are at the end of iteration 5
- Customer meetings in 1 line: reports (1 sentence) but not w/Jamie; name tags
- Leads: your TPS reports are due by noon tomorrow
- Everybody can view the submitted reports through the [reporting system](https://libra.cs.virginia.edu/slp/)
- Details can be found in the [course introduction slide set](../../slides/fall/01-intro.html), specifically [here](../../slides/fall/01-intro.html#tpsreport)
- If your system requires authentication (as most will, eventually), you need to create accounts (of all user levels) for Jamie and myself
- Don't forget to report your hours!!! This is a course requirement!
- Iteration evaluations out through iteration 4
- Please read it over, as many received poor progress ratings because I couldn't log in or find the work that was done
- Once that is fixed, come see me (for iteration 2) or Jamie (for the other iteraitons) during office hours or the meeting, and we will re-do the evaluation
- It is *very bad* of your CI testing does not work
- Today is a group work day; it will also be a group work day on Wednesday
</script></section>
<section data-markdown><script type="text/template">
## Final Projects: Tutorials
- The project is to write a tutorial on *something* that you had to work through this semester
- Something that, if you had had a tutorial ahead of time, would have saved you time or effort
- It must be something that there does not exist a tutorial already online
- They are due at the end of the normal final exam period (Mon, Dec 15 @ noon)
- Everybody will have to one (individually) or convert two (from an older format)
- Note that conversion means making sure that it still works!
- The format will be [Markdown](https://help.github.com/articles/markdown-basics/)
- There is a repo that everybody will fork: [uva-slp/tutorials](https://github.com/uva-slp/tutorials)
- You may want to unwatch it to avoid receiving all the notifications...
- The [README.md](https://github.com/uva-slp/tutorials/blob/master/README.md) contains instructions for topic reservation and how to complete the tutorial (which is dine via a [pull request](https://help.github.com/articles/creating-a-pull-request/))
- This is meant to take about 3 hours, which is the time a final exam would take
- This will count in lieu of your final exam, which will be a non-insignificant part of your final grade
- In an effort to keep this sane for us, will are going to insist that you please follow the directions laid out in that tutorial
</script></section>
<section data-markdown><script type="text/template">
## Wait, you already had tutorials???
- Well, yes, technically
- But they were either:
- For a different API version (CakePHP's tutorials were all prior to the 3.0 API; Rails' tutorials were for a different version also)
- Not for the desired language (no Django tutorials)
- Mostly for things in Ruby that were either covered by the intro tutorial or things people have not yet gotten to
- And they are in all different formats, and most are outdated
- That's why they haven't been released until now...
</script></section>
<section data-markdown><script type="text/template">
## Upcoming Iteration Goals
- Future iterations this semester will have fewer explicit goals
- For all iterations, you should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
- Some specific iteration goals follow:
- Iteration 3: show the wireframe to the customer, get their feedback, iterate on the design
- Iteration 4: implement continuous integration testing
- See the details in the [Continuous Integration Testing](../../slides/fall/11-ci-testing.html) slide set
- Iteration 5: get a preliminary system that implements the minimum requirements working
- This means that most (if not all) of your minimum requirements should be implemented!
- Iteration 6: get a final system that implements the minimum requirements working
- Keep in mind that iteration 6's goal is what you are working toward this entire semester!
</script></section>
<section data-markdown><script type="text/template">
## Things to be completed this semester
- Finish development through iteration 6
- This means that your CI testing had better be green!
- Email your customer to start using the system
- More info on this soon
- You also have to CC me
- Complete your tutorial(s) and submit via a pull request
- Complete the last end-of-phase survey
- Have your final group meeting/presentation with Jamie
- Upload your STS prospectus (if you are using SLP for your technical project)
Note that you will receive an incomplete if any of these things are not done when I submit the final grades!
</script></section>
<section data-markdown><script type="text/template">
## Github Story Points<br>Hall of Shame
Remember that *all* issues (even closed ones) must have a story points tag. The following do not:
- WTJU: issue #78
You can give a tag of "story-points-none" if the task is not worth any story points
</script></section>
</section>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<section>
<section>
<h2>Monday, November 24th, 2014</h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/background_screens.png" title="No way, we gotta rewind and cross-reference this map with the list of coordinates we saw on the other screen. This Greenland thing could be big." alt="Background Screens">
<p class="center"><a href="http://xkcd.com/1451/">xkcd # 1451</a></p>
</section>
<section data-markdown><script type="text/template">
## Monday, November 24th, 2014
- We are half-way through iteration 5
- Last week was a phase change, and an end-of-phase survey to complete
- Customer meetings in 1 line: reports (1 sentence) but not w/Jamie; name tags
- Leads: your weekly reports are due by noon tomorrow
- Everybody can view the submitted reports through the [reporting system](https://libra.cs.virginia.edu/slp/)
- Details can be found in the [course introduction slide set](../../slides/fall/01-intro.html), specifically [here](../../slides/fall/01-intro.html#weeklyreport)
- If your system requires authentication (as most will, eventually), you need to create accounts (of all user levels) for Jamie and myself
- Don't forget to report your hours!!! This is a course requirement!
- Iteration evaluations out through iteration 4 (just released)
- Please read it over, as many received poor progress ratings because I couldn't log in or find the work that was done
- Once that is fixed, come see me (for iteration 2) or Jamie (for the other iteraitons) during office hours or the meeting, and we will re-do the evaluation
- Today is a group work day; there is no class on Wednesday
</script></section>
<section data-markdown><script type="text/template">
## Final Projects and Presentations
- Final projects
- The project is to write a tutorial on *something* that you had to work through this semester
- Something that, if you had had a tutorial ahead of time, would have saved you time or effort
- It must be something that there does not exist a tutorial already online
- There will be a topic reservation system; details to follow
- Everybody will have to one (individually) or convert two (from an older format)
- Note that conversion means making sure that it still works!
- The format will be [Markdown](https://help.github.com/articles/markdown-basics/)
- There will be a single repo that everybody will fork: [uva-slp/tutorials](https://github.com/uva-slp/tutorials)
- The [README.md](https://github.com/uva-slp/tutorials/blob/master/README.md) will contain the instructions for how to complete the tutorial; it is submitted via a [pull request](https://help.github.com/articles/creating-a-pull-request/)
- This is meant to take about 3 hours, which is the time a final exam would take
- This will count for 82954% of your final grade
- More details after Thanksgiving -- you'll receive a notification that you were added to the [uva-slp/tutorials](https://github.com/uva-slp/tutorials) repo
- Final presentations: still working out the details (they may not happen)...
</script></section>
<section data-markdown><script type="text/template">
## Wait, you already had tutorials???
- Well, yes, technically
- But they were either:
- For a different API version (CakePHP's tutorials were all prior to the 3.0 API; Rails' tutorials were for a different version also)
- Not for the desired language (no Django tutorials)
- Mostly for things in Ruby that were either covered by the intro tutorial or things people have not yet gotten to
- And they are in all different formats, and most are outdated
- That's why they haven't been released until now...
</script></section>
<section data-markdown><script type="text/template">
## Upcoming Iteration Goals
- Future iterations this semester will have fewer explicit goals
- For all iterations, you should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
- Some specific iteration goals follow:
- Iteration 3: show the wireframe to the customer, get their feedback, iterate on the design
- Iteration 4: implement continuous integration testing
- See the details in the [Continuous Integration Testing](../../slides/fall/11-ci-testing.html) slide set
- Iteration 5: get a preliminary system that implements the minimum requirements working
- This means that most (if not all) of your minimum requirements should be implemented!
- Iteration 6: get a final system that implements the minimum requirements working
- Keep in mind that iteration 6's goal is what you are working toward this entire semester!
</script></section>
<section data-markdown><script type="text/template">
## Github Story Points<br>Hall of Shame
Remember that *all* issues (even closed ones) must have a story points tag. The following do not:
- Band: issue #39
- JAUNT: issue #93
You can give a tag of "story-points-none" if the task is not worth any story points
</script></section>
</section>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<section>
<section>
<h2>Monday, November 17th, 2014</h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/question.png" title="The universe long dead, IsaAC surveyed the formless chaos. At last, he had arrived at an answer. 'I like you,' he declared to the void, 'but I don't LIKE like you.'" alt="Question" />
<p class="center"><a href="http://xkcd.com/1448/">xkcd # 1448</a></p>
</section>
<section data-markdown><script type="text/template">
## Monday, November 17th, 2014
- We at the end of iteration 4; iteration 5 starts tomorrow
- This means a phase change: new leads and new secretaries
- And an end-of-phase survey, which I will release later today
- Customer meetings: don't forget to submit the meeting report when you have met with them! And wear those nifty name tags.
- Leads: your TPS reports are due by noon tomorrow
- Everybody can view the submitted reports through the [reporting system](https://libra.cs.virginia.edu/slp/)
- Details can be found in the [course introduction slide set](../../slides/fall/01-intro.html), specifically [here](../../slides/fall/01-intro.html#tpsreport)
- The (customer) meeting reports should only be 1 sentence! And no need to mention meetings with Jamie
- If your system requires authentication (as most will, eventually), you need to create accounts (of all user levels) for Jamie and myself
- Don't forget to report your hours!!! This is a course requirement!
- Iteration evaluations out through iteration 3 (released last week)
- Please read it over, as many received poor progress ratings because I couldn't log in or find the work that was done
- Once that is fixed, come see me (for iteration 2) or Jamie (for iteraitons 1 and 3) during office hours or the meeting, and we will re-do the evaluation
- Today is a group work day
</script></section>
<section data-markdown><script type="text/template">
## Wednesday's lecture
- John Feminella, a local software engineer, will be giving a guest talk
- LinkedIn: http://linkedin.com/in/johnxf
- Stack Overflow: http://stackoverflow.com/users/75170/
- Github: http://github.com/fj
- Twitter: [@jxxf](https://twitter.com/jxxf)
- As per your requests, it will be on "software engineering in the real world" with a heavy focus on (1) what working
in a startup is like, (2) what kinds of tools we use in our workflow, and (3) his professional experience
- Don't be late! I will get VERY cranky if you all show up late!
</script></section>
<section data-markdown><script type="text/template">
## Upcoming Iteration Goals
- Future iterations this semester will have fewer explicit goals
- For all iterations, you should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
- Some specific iteration goals follow:
- Iteration 3: show the wireframe to the customer, get their feedback, iterate on the design
- Iteration 4: implement continuous integration testing
- See the details in the [Continuous Integration Testing](../../slides/fall/11-ci-testing.html) slide set
- Iteration 5: get a preliminary system that implements the minimum requirements working
- This means that most (if not all) of your minimum requirements should be implemented!
- Iteration 6: get a final system that implements the minimum requirements working
- Keep in mind that iteration 6's goal is what you are working toward this entire semester!
</script></section>
<section data-markdown><script type="text/template">
## Github Story Points<br>Hall of Shame
Remember that *all* issues (even closed ones) must have a story points tag. The following do not:
- Hope's Legacy: issue #239
You can give a tag of "story-points-none" if the task is not worth any story points
</script></section>
</section>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<section>
<section>
<h2>Wednesday, November 12th, 2014</h2>
<p>Today's comic, focusing on the comet landing, is best viewed directly on <a href="http://xkcd.com/1446/">xkcd.org</a></p>
<p class="center"><a href="http://xkcd.com/1446/">xkcd # 1446</a></p>
</section>
<section data-markdown><script type="text/template">
## Wednesday, November 12th, 2014
- We are one week into iteration 4
- Customer meetings: don't forget to submit the meeting report when you have met with them! And wear those nifty name tags.
- Leads: your weekly reports were due yesterday by noon
- Everybody got them in!
- Everybody can view the submitted reports through the [reporting system](https://libra.cs.virginia.edu/slp/)
- Details can be found in the [course introduction slide set](../../slides/fall/01-intro.html), specifically [here](../../slides/fall/01-intro.html#weeklyreport)
- The meeting reports should only be 1 sentence! And no need to mention meetings with Jamie
- If your system requires authentication (as most will, eventually), you need to create accounts (of all user levels) for Jamie and myself
- Don't forget to report your hours!!! This is a course requirement!
- Iteration evaluations out through iteration 3 (which was just released)
- Please read it over, as many received poor progress ratings because I couldn't log in or find the work that was done
- Once that is fixed, come see me (for iteration 2) or Jamie (for iteraitons 1 and 3) during office hours or the meeting, and we will re-do the evaluation
- Thinking about grad school? Attend the CS grad school session on Thu @ 7 p.m. in OLS 005
- Today will be a CI testing work day
</script></section>
<section data-markdown><script type="text/template">
## Upcoming Iteration Goals
- Future iterations this semester will have fewer explicit goals
- For all iterations, you should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
- Some specific iteration goals follow:
- Iteration 3: show the wireframe to the customer, get their feedback, iterate on the design
- Iteration 4: implement continuous integration testing
- See the details in the [Continuous Integration Testing](../../slides/fall/11-ci-testing.html) slide set
- Iteration 5: get a preliminary system that implements the minimum requirements working
- Iteration 6: get a final system that implements the minimum requirements working
- Keep in mind that iteration 6's goal is what you are working toward this entire semester!
</script></section>
<section data-markdown><script type="text/template">
## Github Story Points<br>Hall of Shame
Remember that *all* issues (even closed ones) must have a story points tag. The following do not:
- JAUNT: issues 60 and 63
You can give a tag of "story-points-none" if the task is not worth any story points
</script></section>
<section data-markdown id="citestingworkday"><script type="text/template">
## Today's task
- Today we will be working on the CI testing setup
- Only one group is fully there yet (which is fine, since it's due at the end of the iteration)
- 7 groups have passing builds, but only one of those seven have all the unit tests configured
- Recall that each *person* must contribute at least 5 valid test cases (and one fixture per person)
- To do today:
- Get Travis or Circle configured for your project; see the [CI testing](../../slides/fall/11-ci-testing.html) slide set for details
- Contribute the desired number of unit tests (at least 5 per person)
- At the end of today, all the build status badges should be green!
</script></section>
<section id="cistatus">
<h2>CI Testing Status</h2>
<ul>
<li>Alzheimer's Association: <a href="https://circleci.com/gh/uva-slp/alzheimers"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://circleci.com/gh/uva-slp/alzheimers.png?style=shield&circle-token="></a></li>
<li>The Arbor: <a href="https://magnum.travis-ci.com/uva-slp/arbor"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://magnum.travis-ci.com/uva-slp/arbor.svg?token="></a></li>
<li>CARS: <a href="https://magnum.travis-ci.com/uva-slp/cars"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://magnum.travis-ci.com/uva-slp/cars.svg?token="></a></li>
<li>Band: <a href="https://magnum.travis-ci.com/uva-slp/band"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://magnum.travis-ci.com/uva-slp/band.svg?token="></a></li>
<li>Hope's Legacy: <a href="https://magnum.travis-ci.com/uva-slp/hopeslegacy"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://magnum.travis-ci.com/uva-slp/hopeslegacy.svg?token="></a></li>
<li>Innisfree Village: <a href="https://circleci.com/gh/uva-slp/innisfree"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://circleci.com/gh/uva-slp/innisfree.png?style=shield&circle-token="></a></li>
<li>JAUNT: <a href="https://circleci.com/gh/uva-slp/jaunt"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://circleci.com/gh/uva-slp/jaunt.png?style=shield&circle-token="></a></li>
<li>Loaves and Fishes: <a href="https://circleci.com/gh/uva-slp/loaves"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://circleci.com/gh/uva-slp/loaves.png?style=shield&circle-token="></a></li>
<li>Madison House: <a href="https://circleci.com/gh/uva-slp/madisonhouse"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://circleci.com/gh/uva-slp/madisonhouse.png?style=shield&circle-token="></a></li>
<li>Service Dogs: <a href="https://magnum.travis-ci.com/uva-slp/servicedogs"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://magnum.travis-ci.com/uva-slp/servicedogs.svg?token="></a></li>
<li>The Haven: <a href="https://magnum.travis-ci.com/uva-slp/haven"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://magnum.travis-ci.com/uva-slp/haven.svg?token="></a></li>
<li>Shelter for Help in Emergency: <a href="https://circleci.com/gh/uva-slp/shelter"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://circleci.com/gh/uva-slp/shelter.png?style=shield&circle-token="></a></li>
<li>TJACE: <a href="https://magnum.travis-ci.com/uva-slp/tjace"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://magnum.travis-ci.com/uva-slp/tjace.svg?token="></a></li>
<li>Wintergreen Adaptive Sports: <a href="https://circleci.com/gh/uva-slp/was"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://circleci.com/gh/uva-slp/was.png?style=shield&circle-token="></a></li>
<li>WTJU 91.1 FM: <a href="https://magnum.travis-ci.com/uva-slp/wtju"><img style="display:inline;margin:0px 0px 0px 10px" alt="Build Status" src="https://magnum.travis-ci.com/uva-slp/wtju.svg?token="></a></li>
</ul>
<p> </p>
<p>This page refreshes every 30 seconds</p>
</section>
</section>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<section>
<section>
<h2>Monday, November 10th, 2014</h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/efficiency.png" title="I need an extension for my research project because I spent all month trying to figure out whether learning Dvorak would help me type it faster." alt="Efficiency">
<p class="center"><a href="http://xkcd.com/1445/">xkcd # 1445</a></p>
</section>
<section data-markdown><script type="text/template">
## Monday, November 10th, 2014
- We are one week into iteration 4
- Customer meetings: don't forget to submit the meeting report when you have met with them! And wear those nifty name tags.
- Leads: your weekly reports are due tomorrow by noon
- Everybody can view the submitted reports through the [reporting system](https://libra.cs.virginia.edu/slp/)
- Details can be found in the [course introduction slide set](../../slides/fall/01-intro.html), specifically [here](../../slides/fall/01-intro.html#weeklyreport)
- The meeting reports should only be 1 sentence! And no need to mention meetings with Jamie
- If your system requires authentication (as most will, eventually), you need to create accounts (of all user levels) for Jamie and myself
- Don't forget to report your hours!!! This is a course requirement!
- Iteration evaluations out through iteration 3 (which was just released last night)
- Please read it over, as many received poor progress ratings because I couldn't log in or find the work that was done
- Once that is fixed, come see me (for iteration 2) or Jamie (for iteraitons 1 and 3) during office hours or the meeting, and we will re-do the evaluation
- Today is a group meeting day
</script></section>
<section data-markdown><script type="text/template">
## Upcoming Iteration Goals
- Future iterations this semester will have fewer explicit goals
- For all iterations, you should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
- Some specific iteration goals follow:
- Iteration 3: show the wireframe to the customer, get their feedback, iterate on the design
- Iteration 4: implement continuous integration testing
- See the details in the [Continuous Integration Testing](../../slides/fall/11-ci-testing.html) slide set
- Iteration 5: get a preliminary system that implements the minimum requirements working
- Iteration 6: get a final system that implements the minimum requirements working
- Keep in mind that iteration 6's goal is what you are working toward this entire semester!
</script></section>
<section data-markdown id="jxf"><script type="text/template">
## Guest talk
- Next week we will have a guest lecturer: John Feminella
- LinkedIn: http://linkedin.com/in/johnxf
- Stack Overflow: http://stackoverflow.com/users/75170/
- Github: http://github.com/fj
- Twitter: [@jxxf](https://twitter.com/jxxf)
- He has a lot of experience with Rails, start-ups, open source, etc.
- He wanted to know what topics you all would like him to cover
- Please fill out the survey at http://tinyurl.com/lqucens
- That's a lower-case "L" in the url, not the number one
</script></section>
<section data-markdown><script type="text/template">
## Github Story Points<br>Hall of Shame
Remember that *all* issues (even closed ones) must have a story points tag. The following do not:
- jaunt: issues 60 and 63
- haven: issues 9, 13, 22, 31, and 47
- shelter: issues 26, 29, 36, 38, 41, and 47
You can give a tag of "story-points-none" if the task is not worth any story points
</script></section>
</section>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<section>
<section>
<h2>Wednesday, November 5th, 2014</h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/language_nerd.png" title="Not to go all sentence fragment on you." alt="Language Nerd">
<p class="center"><a href="http://xkcd.com/1443/">xkcd # 1443</a></p>
</section>
<section data-markdown><script type="text/template">
## Wednesday, November 5th, 2014
- We are starting iteration 4
- Customer meetings: don't forget to submit the meeting report when you have met with them! And wear those nifty name tags.
- Leads: your TPS reports were due yesterday by noon
- One group didn't get it in...
- Everybody can view the submitted reports through the [reporting system](https://libra.cs.virginia.edu/slp/)
- Details can be found in the [course introduction slide set](../../slides/fall/01-intro.html), specifically [here](../../slides/fall/01-intro.html#tpsreport)
- The meeting reports should only be 1 sentence! And no need to mention meetings with Jamie
- If your system requires authentication (as most will, eventually), you need to create accounts (of all user levels) for Jamie and myself
- Don't forget to report your hours!!! This is a course requirement!
- Iteration evaluations out for iteration 1 and 2; iteration 3 is coming later this week
- Please read it over, as many received poor progress ratings because I couldn't log in or find the work that was done
- Once that is fixed, come see me (during office hours), and I will re-do the evaluation
- Today we'll talk about [Continuous Integration Testing](../../slides/fall/11-ci-testing.html)
</script></section>
<section data-markdown><script type="text/template">
## Upcoming Iteration Goals
- Future iterations this semester will have fewer explicit goals
- For all iterations, you should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
- Some specific iteration goals follow:
- Iteration 3: show the wireframe to the customer, get their feedback, iterate on the design
- Iteration 4: implement continuous integration testing
- See the details in the [Continuous Integration Testing](../../slides/fall/11-ci-testing.html) slide set
- Iteration 5: get a preliminary system that implements the minimum requirements working
- Iteration 6: get a final system that implements the minimum requirements working
- Keep in mind that iteration 6's goal is what you are working toward this entire semester!
</script></section>
<section data-markdown><script type="text/template">
## Github Story Points<br>Hall of Shame
Remember that *all* issues (even closed ones) must have a story points tag. The following do not:
- band: issue #33
You can give a tag of "story-points-none" if the task is not worth any story points
</script></section>
</section>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<section>
<section>
<h2>Monday, November 3rd, 2014</h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/chemistry.png" title="These are all sans-serif compounds. Serif compounds are dramatically different and usually much more reactive." alt="Chemistry">
<p class="center"><a href="http://xkcd.com/1442/">xkcd # 1442</a></p>
</section>
<section data-markdown><script type="text/template">
## Monday, November 3rd, 2014
- We are at the end of iteration 3
- Customer meetings: don't forget to submit the meeting report when you have met with them! And wear those nifty name tags.
- Leads: your TPS reports are due tomorrow by noon
- Everybody can view the submitted reports through the [reporting system](https://libra.cs.virginia.edu/slp/)
- Details can be found in the [course introduction slide set](../../slides/fall/01-intro.html), specifically [here](../../slides/fall/01-intro.html#tpsreport)
- The meeting reports should only be 1 sentence! And no need to mention meetings with Jamie
- If your system requires authentication (as most will, eventually), you need to create accounts (of all user levels) for Jamie and myself
- I have it from exactly two groups...
- Don't forget to report your hours!!! This is a course requirement!
- Iteration evaluations out for iteration 1; iteration 2 and 3 coming this week
- I realize we are a bit late with the first two...
- Continuous integration services: any preferences? We'll be using two: Travis CI and Circle CI
- You can view a graph of your github issue data in the course reporting tool (under 'project details')
- This is purely for informative purposes -- there is no "right" or "wrong" look to the graph, and thus no grade penalty (or bonus) depending on it's look
</script></section>
<section data-markdown><script type="text/template">
## Upcoming Iteration Goals
- Future iterations this semester will have fewer explicit goals
- For all iterations, you should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
- Some specific iteration goals follow:
- Iteration 3: show the wireframe to the customer, get their feedback, iterate on the design
- Iteration 4: implement continuous integration testing
- This will be described in detail in the [continuous integration testing](../../slides/fall/11-ci-testing.html) slide set discussed on Wednesday
- Iteration 5: get a preliminary system that implements the minimum requirements working
- Iteration 6: get a final system that implements the minimum requirements working
- Keep in mind that iteration 6's goal is what you are working toward this entire semester!
</script></section>
<section data-markdown><script type="text/template">
## Github Story Points<br>Hall of Shame
Remember that *all* issues (even closed ones) must have a story points tag. The following do not:
- arbor: issue 59
You can give a tag of "story-points-none" if the task is not worth any story points
</script></section>
</section>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<section>
<section>
<h2>Wednesday, October 29th, 2014</h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/geese.png" title="Anyway, that's a common misconception. Geese live for a long time; all the ones we can see will probably keep flying around for billions of years before they explode." alt="Geese">
<p class="center"><a href="http://xkcd.com/1440/">xkcd # 1440</a></p>
</section>
<section data-markdown><script type="text/template">
## Wednesday, October 29th, 2014
- We are one week into iteration 3
- Customer meetings: don't forget to submit the meeting report when you have met with them! And wear those nifty name tags.
- Leads: your first weekly reports were due yesterday by noon (and everybody got them in!)
- Everybody can view the submitted reports through the [reporting system](https://libra.cs.virginia.edu/slp/)
- Details can be found in the [course introduction slide set](../../slides/fall/01-intro.html), specifically [here](../../slides/fall/01-intro.html#weeklyreport)
- A note about the meeting reports: they should only be 1 sentence!
- And no need to mention a meeting with Jamie
- If your system requires authentication (as most will, eventually), you need to create accounts (of all user levels) for Jamie and myself
- I have it from exactly two groups...
- Don't forget to report your hours!!! This is a course requirement!
- Iteration evaluations coming soon!
- Continuous integration services: any preferences? We'll be using two...
- You can view a graph of your github issue data in the course reporting tool (under 'project details')
- This is purely for informative purposes -- there is no "right" or "wrong" look to the graph, and thus no grade penalty (or bonus) depending on it's look
</script></section>
<section data-markdown><script type="text/template">
## Upcoming Iteration Goals
- Future iterations this semester will have fewer explicit goals
- For all iterations, you should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
- Some specific iteration goals follow:
- Iteration 3: show the wireframe to the customer, get their feedback, iterate on the design
- Iteration 4: implement continuous integration testing (more on this in a future lecture)
- Iteration 5: get a preliminary system that implements the minimum requirements working
- Iteration 6: get a final system that implements the minimum requirements working
- Keep in mind that iteration 6's goal is what you are working toward this entire semester!
</script></section>
<section data-markdown><script type="text/template">
## Github Story Points<br>Hall of Shame
Remember that *all* issues (even closed ones) must have a story points tag. The following do not:
- nobody! w00t!
You can give a tag of "story-points-none" if the task is not worth any story points
</script></section>
<section data-markdown id="pivotal"><script type="text/template">
## Today's Task
- Today we are going to investigate whether an online tool, [Pivotal Tracker](https://www.pivotaltracker.com) (https://www.pivotaltracker.com) would be worth using for our projects
- Before having all of you to use it, I want your opinion as to whether it would be useful or not
- What I want to know at the end of today: disregarding the learning curve, would a tool such as Pivotal Tracker help your group's productivity?
- Your task:
- Turn of Facebook, Twitter, and other social media
- Split into your project groups, as you will be collaborating on this
- Create an account on [Pivotal Tracker](https://www.pivotaltracker.com); it's free
- Create a sample project (*not* a blank project!)
- Fool around with the interface to get an idea of what it can do
- Add stories, modify stuff, understand the UI features, display options, etc.
- Talk with each other about how this would be used
- Understand how this integrates with github (just google for "pivotal tracker github integration")
- You should be spending ~30-40 minutes on all of this -- the idea is for you to really understand how it works!
- You should be experts at this tool by the end of today's lecture!
- Fill out the survey at https://libra.cs.virginia.edu/ptsurvey (it's all of 4 questions)
- This is where you tell me how useful it would be
- This is also today's attendance, so be sure to fill it out!
</script></section>
</section>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<section>
<section>
<h2>Monday, October 27th, 2014</h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/rack_unit.png" title="There's also nothing in the TOSes that says you can't let a dog play baseball in the server room!" alt="Rack Unit">
<p class="center"><a href="http://xkcd.com/1439/">xkcd # 1439</a></p>
</section>
<section data-markdown><script type="text/template">
## Monday, October 27th, 2014
- We are one week into iteration 3
- Everybody filled out the end-of-phase survey!
- Customer meetings: don't forget to submit the meeting report when you have met with them! And wear those nifty name tags.
- Leads: your first weekly reports are due tomorrow by noon
- Everybody can view the submitted reports through the [reporting system](https://libra.cs.virginia.edu/slp/)
- Details can be found in the [course introduction slide set](../../slides/fall/01-intro.html), specifically [here](../../slides/fall/01-intro.html#weeklyreport)
- A note about the meeting reports: they should only be 1 sentence!
- If your system requires authentication (as most will, eventually), you need to create accounts (of all user levels) for Jamie and myself
- Don't forget to report your hours!!! This is a course requirement!
- You can view a graph of your github issue data in the course reporting tool (under 'project details')
- This is purely for informative purposes -- there is no "right" or "wrong" look to the graph, and thus no grade penalty (or bonus) depending on it's look
</script></section>
<section data-markdown><script type="text/template">
## Upcoming Iteration Goals
- Future iterations this semester will have fewer explicit goals
- For all iterations, you should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
- Some specific iteration goals follow:
- Iteration 3: show the wireframe to the customer, get their feedback, iterate on the design
- Iteration 4: implement continuous integration testing (more on this in a future lecture)
- Iteration 5: get a preliminary system that implements the minimum requirements working
- Iteration 6: get a final system that implements the minimum requirements working
- Keep in mind that iteration 6's goal is what you are working toward this entire semester!
</script></section>
<section data-markdown><script type="text/template">
## Github Story Points<br>Hall of Shame
Remember that *all* issues (even closed ones) must have a story points tag. The following do not:
- Alzheimers: issue 65
- WTJU: issues 38, 39, and 41
You can give a tag of "story-points-none" if the task is not worth any story points
</script></section>
</section>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<section>
<section>
<h2>Wednesday, October 22nd, 2014</h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/higgs_boson.png" title="'Can't you just use the LHC you already built to find it again?' 'We MAY have disassembled it to build a death ray.' 'Just one, though.' 'Nothing you should worry about.' 'The death isn't even very serious.'" alt="Higgs Boson">
<p class="center"><a href="http://xkcd.com/1437/">xkcd # 1437</a></p>
</section>
<section data-markdown><script type="text/template">
## Wednesday, October 22nd, 2014
- We are in the first day of iteration 3
- We had a phase change with the start of iteration 3
- New lead and new secretary
- Everybody has to fill out the end-of-phase survey
- See [here](#/endofphase) for details on the end of phase and the survey
- Customer meetings: don't forget to submit the meeting report when you have met with them!
- And don't forget to wear your name tags!
- (Old) leads: your TPS reports were due yesterday by noon
- Two groups didn't get them in...
- Everybody can view the submitted reports through the [reporting system](https://libra.cs.virginia.edu/slp/)
- Details can be found in the [course introduction slide set](../../slides/fall/01-intro.html), specifically [here](../../slides/fall/01-intro.html#tpsreport)
- If your system requires authentication (as most will, eventually), you need to create accounts (of all user levels) for Jamie and myself
- Don't forget to report your hours!!! This is a course requirement!
- Today is a lecture on [documentation](../../slides/fall/10-documentation.html)
</script></section>
<section data-markdown><script type="text/template">
## Upcoming Iteration Goals
- Future iterations this semester will have fewer explicit goals
- For all iterations, you should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
- Some specific iteration goals follow:
- Iteration 3: show the wireframe to the customer, get their feedback, iterate on the design
- Iteration 4: implement continuous integration testing (more on this in a future lecture)
- Iteration 5: get a preliminary system that implements the minimum requirements working
- Iteration 6: get a final system that implements the minimum requirements working
- Keep in mind that iteration 6's goal is what you are working toward this entire semester!
</script></section>
<section data-markdown><script type="text/template">
## Issues missing story points
Remember that *all* issues must have a story points tag
- Arbor: issues 39-45
- Band: issue 8
- Jaunt: issue 39
- Madison house: issue 24
- Service dogs: issues 90 and 91
- WTJU: issues 38-41
You can give a tag of "story-points-none" if the task is not worth any story points
</script></section>
</section>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<section>
<section>
<h2>Monday, October 20th, 2014</h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/orb_hammer.png" title="Ok, but make sure to get lots of pieces of rock, because later we'll decide to stay in a room on our regular orb and watch hammers hold themselves and hit rocks for us, and they won't bring us very many rocks." alt="Orb Hammer">
<p class="center"><a href="http://xkcd.com/1436/">xkcd # 1436</a></p>
</section>
<section data-markdown><script type="text/template">
## Monday, October 20th, 2014
- We are at the end of iteration 2
- Customer meetings: don't forget to submit the meeting report when you have met with them!
- And don't forget to wear your name tags!
- Leads: your TPS reports are due tomorrow by noon
- Everybody can view the submitted reports through the [reporting system](https://libra.cs.virginia.edu/slp/)
- Details can be found in the [course introduction slide set](../../slides/fall/01-intro.html), specifically [here](../../slides/fall/01-intro.html#tpsreport)
- If your system requires authentication (as most will, eventually), you need to create accounts (of all user levels) for Jamie and myself
- Don't forget to report your hours!!!
- This is a course requirement -- not completing them will result in a failure for the course
- Grades for the first three homeworks have been returned
- You can submit regrades (through the end of this week) via the course management system
when they were returned (Sep 29)
- If you are fine with your git hw grade, ***PLEASE DELETE YOUR GIT HW REPOS***
- Or you can remove myself and Jamie as collaborators
- Or you will not get any credit for the assignment
- Today is a group meeting day; Wednesday will be lecture, likely on documentation
</script></section>
<section data-markdown><script type="text/template">
## Iteration 2 Goals
- You should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
- Your regular iteration meeting with the customer and Jamie should happen
- Specific goals:
- Generate wireframes (see the [wireframing lecture](../../slides/fall/09-wireframing.html) and consider using [jetstrap](http://jetstrap.com))
- Set up everybody's development environment (see the [development environment setup](../../docs/dev-env-setup.html) ([md](../../docs/dev-env-setup.md)) page)
- Enable easy deployment via automatic logins or ssh keys
- Enable easy downloading of the database
- Ensure that *everybody* in the development group can develop on his/her own machine
- Requirements document
- Your requrements document will be iterated on throughout the year
- What format you keep it in is up to you, but I need to be able to view it
- Having the original source (in the [uva-slp/projects repo](https://github.com/uva-slp/projects) repo) in a `docs` directory in your repo is quite reasonable
</script></section>
<section data-markdown id="endofphase"><script type="text/template">
## Phase Change
- All groups will have a *phase change* at the end of iteration 2
- This means a new lead and new secretary take over
- The new lead should indicate that they are such to the customer (either by email or at your next meeting)
- I'll be sending the new leads info on their lead-ness
- And there is an "end-of-phase" survey to complete
- Completing this survey is a course requirement
- All info that you put down is confidential -- no other students in this class will see your results
- I may release *averages* and such, as long as it preserves anonyminity
- I will not be basing your grades on your responses, so please be honest and frank! And verbose.
- The invitation to complete the survey will be mailed to you shortly
</script></section>
<section data-markdown><script type="text/template">
## Upcoming Iteration Goals
- Future iterations this semester will have fewer explicit goals
- For all iterations, you should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
- Some specific iteration goals follow:
- Iteration 3: show the wireframe to the customer, get their feedback, iterate on the design
- Iteration 4: implement continuous integration testing (more on this in a future lecture)
- Iteration 5: get a preliminary system that implements the minimum requirements working
- Iteration 6: get a final system that implements the minimum requirements working
- Keep in mind that *this* is the goal you are working toward this entire semester!
</script></section>
</section>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<section>
<section>
<h2>Wednesday, October 15th, 2014</h2>
<img class="stretch" src="http://imgs.xkcd.com/comics/lightsaber.png" title="A long time in the future, in a galaxy far, far, away, astronomers in the year 2008 sight an unusual gamma-ray burst originating from somewhere far across the universe." alt="Lightsaber">
<p class="center"><a href="http://xkcd.com/1433/">xkcd # 1433</a></p>
</section>
<section data-markdown><script type="text/template">
## Wednesday, October 15th, 2014
- We are in the second week of iteration 2
- I won't have office hours today unless someobdy lets me know they will be there...
- Customer meetings: don't forget to submit the meeting report when you have met with them!
- And don't forget to wear your name tags!
- Leads: your weekly reports were due yesterday by noon
- Everybody got them in, albeit some were late
- Everybody can view the submitted reports through the [reporting system](https://libra.cs.virginia.edu/slp/)
- Details can be found in the [course introduction slide set](../../slides/fall/01-intro.html), specifically [here](../../slides/fall/01-intro.html#weeklyreport)
- Don't forget to report your hours!!!
- This is a course requirement -- not completing them will result in a failure for the course
- Grades for the first three homeworks have been returned
- You can submit regrades (through the end of this week) via the course management system
when they were returned (Sep 29)
- If you are fine with your git hw grade, ***PLEASE DELETE YOUR GIT HW REPOS***
- They are all showing up in my listings...
- Or you can remove myself and Jamie as collaborators
- One of these two options will be needed to get credit!
- As there was no group meeting day on Monday, we'll have one today
- ACM game night this Thursday at 8 p.m. in Rice 436!
</script></section>
<section data-markdown><script type="text/template">
## Iteration 2
- You should pick 24 or 28 story points worth of "stuff" to do; pick the highest priority stuff!
- Your regular iteration meeting with the customer and Jamie should happen
- Specific goals: