slp/uva/old/course-introduction-spring-2017.html at master · aaronbloomfield/slp · GitHub

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
<!doctype html>
<html lang="en">
  <head>
    <meta charset="utf-8">
    <title>CS 4971: course-introduction-spring slide set</title>
    <meta name="description" content="A set of slides for UVa's Service Learning Practicum course">
    <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, minimal-ui">
    <link rel="stylesheet" href="../../slides/reveal.js/css/reveal.css">
    <link rel="stylesheet" href="../../slides/reveal.js/css/theme/black.css" id="theme">
    <link rel="stylesheet" href="../../slides/css/slp.css">
    <!-- Code syntax highlighting -->
    <link rel="stylesheet" href="../../slides/reveal.js/lib/css/zenburn.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 ) ? '../../slides/reveal.js/css/print/pdf.css' : '../../slides/reveal.js/css/print/paper.css';
      document.getElementsByTagName( 'head' )[0].appendChild( link );
    </script>
    <!--[if lt IE 9]>
	<script src="../../slides/reveal.js/lib/js/html5shiv.js"></script>
	<![endif]-->
    <script type="text/javascript" src="../../slides/js/dhtmlwindow.js"></script>
    <script type="text/javascript" src="../../slides/js/canvas.js"></script>
    <link rel="stylesheet" href="../../slides/css/dhtmlwindow.css" type="text/css">
  </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 4971
&nbsp;
### Capstone Practicum II
### Spring 2017
&nbsp;
<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) / [&uarr;](../../slides/index.html) / <a href="course-introduction-spring.html?print-pdf"><img class="print" width="20" src="../../slides/images/print-icon.png"></a></small></center>
&nbsp;
&nbsp;
## Course Introduction
	</script></section>

	<section data-markdown><script type="text/template">
## Compressed course introduction
- Pretty much everything is the same as last semester, expect for the few things mentioned herein
  - See last semester's [course introduction slide set](course-introduction-fall.html#/), and the [course syllabus](syllabus.html) ([md](syllabus.md)), for details
	</script></section>

	<section data-markdown><script type="text/template">
## Iteration plan
- There will be 8 two-week iterations this semester (numbered 7-14); iteration 7 started yesterday
  - We have new leads and secretaries
- The system must be *feature-complete* by the end of iteration 11 (March 27th)
  - Missing this deadline will result in <strong class="red">failure for the course</strong>!
  - Recall that we have a [bunch of tutorials](http://github.com/uva-slp/tutorials) about how to implement various things
- That leaves iterations 12-14 for transition: bug fixes, tweaks, testing, deployment, documentation, maintenance, etc.
	</script></section>

	<section data-markdown><script type="text/template">
## Wait? documentation, you say???
- Yes, documentation:
  - Transition plan (consists of the deployment plan, test plan(s), etc.)
  - User manual
  - Installation instructions
  - Programming reference
  - Updated requirements document
  - STS technical report
- I'm looking for complete documentation, not necessarily long-winded documentation
- I will provide detailed instructions as to what goes into each
  - It's in the [deliverables](../../slides/11-deliverables.html#/) slide set, which will be gone over in lecture
	</script></section>

	<section data-markdown><script type="text/template">
## Making progress
- As there is no additional semester after this one to complete the project, you will be held to your various requirements:
  - The original requirements document
  - Updated versions of this requirements document
  - Issues entered into github
- Not completing these requirements means that you did not complete the project!
- Among other things, this means:
  - You have to make more actual progress!
  - Last semester some groups didn't make 'actual progress' until the end of the semester...
  - And you will need to keep your github issues updated
	</script></section>

	<section data-markdown><script type="text/template">
## Course meetings
- The weekly schedule will be the same as last semester:
  - Mondays: group meeting day
  - Wednesday: lecture or group work day
  - Friday: no class, unless otherwise notified
- As the semester goes on, we will have less lectures are more group work days
  - This is intentional
- I'm going to get cranky if people are always coming in late to Monday and Wednesday's classes...
	</script></section>

	<section data-markdown><script type="text/template">
## STS 4600
- Most of you are using this course as the STS 4600 technical project
  - You must let me know when the STS 4600 due dates come up, as I have no other way of finding out
- The *entire* group will work on the technical report (not just the STS 4600 students)
  - It will be an article about 6 pages in length; I will make a template available as we approach that date
	</script></section>

	<section data-markdown id="phases"><script type="text/template">
## Semester Phases
- For the 6 person groups, there will be 3 phases:
  - Phase 4: iterations 7-9 (3 iterations)
  - Phase 5: iterations 10-11 (2 iterations)
  - Phase 6: iterations 12-14 (3 iterations)
- For the 7 person group, there will be 4 phases:
  - Phase 4: iterations 7-8 (2 iterations)
  - Phase 5: iterations 9-10 (2 iterations)
  - Phase 6: iterations 11-12 (2 iterations)
  - Phase 7: iterations 13-14 (2 iterations)
- If there are groups of other sizes, we will chat individually about how to handle this
- Full schedule can be found [here](index.html) ([md](index.md)), at the bottom
	  </script></section>

	<section data-markdown><script type="text/template">
## Project Status
- Your customer should have used the system over break
- You should thus have feedback from him or her
  - (you may have to email them to remind them to send you that feedback)
- That, plus existing github issues, should provide you some idea of what to work on in the current iteration
	</script></section>

	<section data-markdown><script type="text/template">
## Meetings
- You do not have to have your bi-weekly meeting with the customer this iteration, **AS LONG AS** you get email feedback instead
  - Although you are welcome to do so
- The bi-weekly meetings with the customer and also graduate TA will start next iteration
  - We'll have a scheduling session during next Monday's group meeting lecture
	</script></section>

	<section data-markdown><script type="text/template">
## Deployment Plan
- The deliverable for iteration 7 is the **Deployment Plan**
  - We are going to go over it in detail next Wednesday
  - It will require input from the customer (via email is fine)
- If you are going to have a customer meeting **BEFORE** next Wednesday's lecture, you must speak to me in class today or on Monday, and I'll fill you in on what you need to ask
  - You can see a preview [here](../../slides/11-deliverables.html#/deployment-plan), but that slide set is not yet complete
  - Much of this was done last semester, so it should be relatively easy
	</script></section>

	<section data-markdown id="grades"><script type="text/template">
## Grades reminder
From the [first lecture in the fall](course-introduction-fall.html#/) (specifically, [here](course-introduction-fall.html#/grades)):

- Not completing time sheets or surveys will penalize your grade
  - Likewise with reports
- ***EVERYBODY*** is expected to contribute to the project
  - This means, among other things, that there should be (real) git commits from everybody (and likely for each iteration)
- We can re-do the spring iteration evaluations, for example if we could not find something, as long as it is brought to our attention within a reasonable time frame (2 weeks from when they are released)
- Attendance is still required
	</script></section>

	<section data-markdown><script type="text/template">
## Course size issues
- About 5% of last semester's class will not be in this spring's class
  - No, they were not all due to failures
- Registration is currently at 87, and I expect it to hit 92
- This means some group sizes will be changing
- If your team size changed, then every team will have to fill out a new [SLP Project Start Information Sheet](../../uva/project-start-info-sheet-2015.pdf)
  - Or chat with me as I walk around today
	</script></section>

	<section data-markdown><script type="text/template">
## Today's agenda: group meeting
- It's the beginning of iteration 7:
  - New leads and secretaries (and possibly re-doing the [SLP Project Start Information Sheet](../../uva/project-start-info-sheet-2015.pdf))
  - Is your CI build green?
  - Did you get feedback from the customer?
  - What issues will be worked on during this iteration?
  - How will you get all of your features completed by the end of iteration 11?
  - Update the github issues and story point counts, as they are not looking like much of a burndown chart...
	</script></section>

	<section data-markdown><script type="text/template">
## Schedule for the first month
- Wed, Jan 18th (today): course introduction, group meetings
- Mon, Jan 23th: group meetings
- Wed, Jan 25th: [deliverables](11-deliverables.html#/) lecture
- Mon, Jan 30th: group meetings
- Wed, Feb 1st: the rest of the [deliverables](11-deliverables.html#/) lecture
- Mon, Feb 6th: group meetings
- Wed, Feb 8th: [testing](12-testing.html#/) lecture
- Mon, Feb 13th: group meetings
- Wed, Feb 15th: the rest of the [testing](12-testing.html#/) lecture
- Mon, Feb 20th: group meetings
	</script></section>

	<section data-markdown><script type="text/template">
## Iteration start-up
- Iteration 7 started yesterday
- The leads and secretaries are listed in the course management tool
  - I'll be emailing all the leads later today
  - The first deliverable by the (new) lead is the report, and I'll remind you about that on Monday
	</script></section>

	  <section data-markdown id="it7goals"><script type="text/template">
## Goals for Iteration 7
- Complete 4 story points worth of work per group member
- Update the requirements document with the work to be done for this semester
  - Since the minimum requirements were done last semester, this should all be under desired requirements
  - But this may need to be adjusted depending on last semester's progress, customer feedback, etc.
- Write the [deployment plan](../../slides/11-deliverables.html#/deployment-plan)
  - Enter that as a docs/deployment-plan.md file in the repo
  - This is the document deliverable for this iteration
- Get feedback from the customer about the system, either in person or by email
  - This will be used to edit the requirements document and the github issues
- Edit the github issues to make them as reasonably accurate as you can at this point
- Plan out what to do in the next iteration (include that in the TPS report)
	  </script></section>

	<section data-markdown><script type="text/template">
## And now to the group meetings!
	</script></section>

      </div>

    </div>

    <script src="../../slides/reveal.js/lib/js/head.min.js"></script>
    <script src="../../slides/reveal.js/js/reveal.js"></script>
    <script src="../../slides/js/settings-deeper.js"></script>

  </body>
</html>