-
Notifications
You must be signed in to change notification settings - Fork 0
/
scrum_intro.html
383 lines (358 loc) · 14.2 KB
/
scrum_intro.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
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Scrum Introduction</title>
<meta name="description" content="An introduction to Scrum & Agile best practices">
<meta name="author" content="Amri Hidayat">
<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="css/reveal.css">
<link rel="stylesheet" href="css/theme/white.css" id="theme">
<!-- Code syntax highlighting -->
<link rel="stylesheet" href="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 ) ? 'css/print/pdf.css' : 'css/print/paper.css';
document.getElementsByTagName( 'head' )[0].appendChild( link );
</script>
<!--[if lt IE 9]>
<script src="lib/js/html5shiv.js"></script>
<![endif]-->
</head>
<body>
<div class="reveal">
<!-- Any section element inside of this container is displayed as a slide -->
<div class="slides">
<!--- SCRUM -->
<section>
<section>
<h1>Scrum</h1>
<h4>An Introduction</h4>
<small>Amri Hidayat (amri.hidayat@gmail.com)</small>
</section>
<section>
<p>Brief introduction about me..</p>
<ul>
<li class="fragment">[study] Computer Science @ UI</li>
<li class="fragment">[work] Microsoft Innovation Center @ UI</li>
<li class="fragment">[study] Information Studies @ NTU</li>
<li class="fragment">[work] Hewlett-Packard Asia Pacific</li>
<li class="fragment">[work] Wolters Kluwer Asia Pacific</li>
<li class="fragment">[work] Silverlake Mobility</li>
</ul>
</section>
<section>
<h4>My Github</h4>
<img src="assets/github_qr.png" width="50%" />
</section>
<section>
<h4>My LinkedIn</h4>
<img src="assets/linked_in_qr.png" width="50%" />
</section>
</section>
<section>
<img src="assets/scrum/complex_project_onion.png" width="60%"/>
</section>
<section>
<section>
<h2>Project Constraints</h2>
<ul>
<li>Product Scope</li>
<li>Time/Schedule</li>
<li>Cost/Resource</li>
</ul>
</section>
<section>
<h1>Scrum</h1>
<h3 class="fragment">Delivering the highest business value in the shortest time</h3>
</section>
<section>
<h2>Scrum Roles</h2>
<ul>
<li class="fragment">Scrum Team</li>
<li class="fragment">Product Owner</li>
<li class="fragment">Scrum Master</li>
</ul>
</section>
<section>
<h2>Scrum Ceremonies</h2>
<ul>
<li class="fragment">Sprint Planning</li>
<li class="fragment">Daily Standup</li>
<li class="fragment">Product Review</li>
<li class="fragment">Process Review</li>
</ul>
</section>
<section>
<h2>Agile Values</h2>
<ul>
<li class="fragment">Focus</li>
<li class="fragment">Courage</li>
<li class="fragment">Openness</li>
<li class="fragment">Commitment</li>
<li class="fragment">Respect</li>
</ul>
</section>
<section>
<img src="assets/scrum/scrum_commitment.gif" width="100%" border="0"/>
</section>
</section>
<section>
<section>
<h1>Definition of Done</h1>
<small>Team, together with the product owner, defines what "done" means</small>
<ul>
<li>Design, coding, unit testing, integrated</li>
<li>Acceptance tested, deployable</li>
<li>Performance & Usability test</li>
<li><font style="color: #C2C2C2">Test in sandbox producation environment</font></li>
<li><font style="color: #C2C2C2">Update customer documentation & marketing plan</font></li>
</ul><br/>
<small style="color: #C2C2C2">Extending "done"</small>
</section>
<section>
<h1>Sprint Planning</h1>
<img src="assets/scrum/Scrum_process.svg.png"/>
</section>
<section>
<h1>Estimation</h1>
<ul>
<li class="fragment">Wideband Delphi</li>
<li class="fragment">PROBE</li>
<li class="fragment">Planning Poker</li>
</ul>
</section>
<section>
<h1>Planning Poker</h1>
<small>Fun way of saying requirement estimation</small>
<ul>
<li class="fragment">Pick a requirement and discuss about it</li>
<li class="fragment">Each team member picks a number from the deck</li>
<li class="fragment">Reach to an agreement and move to another requirement</li>
<li class="fragment">Stop if the team say so ...</li>
</ul>
</section>
<section>
<h1>Velocity</h1>
<p>Story points delivered for a period of time / Total ideal hours spent on a sprint</p>
<img src="assets/scrum/velocity.png" style="border:0"/>
</section>
<section>
<h1>Sprint</h1>
<p class="fragment">So what do you do within sprint ?</p>
</section>
<section>
<p class="fragment">1. Start a day with <b>Daily Standup</b></p>
<p class="fragment">2. Complete a task to achieve <b>acceptance criteria</b> of a user story</p>
<small class="fragment">... and if you are developing a software ... </small>
<p class="fragment">3. Pair up, Test-Driven Development, Ship it</p>
<p class="fragment">4. Try to automate things</p>
</section>
<!-- NOT YET READY
<section>
<h1>Cost Estimation</h1>
<p>Cost is a resource sacrificed or foregone or consumed to achieve a specific objective or something given up in exchange.</p>
<img src="assets/time_cost_scope.png" style="border:0"/>
</section>
-->
</section>
<section>
<section>
<h1>Documentation</h1>
<ul>
<li>Requirements</li>
<li>Agile Modelling</li>
</ul>
</section>
<section>
<h2>User Story</h1>
<small>In Waterfall project, the customer defines his requirements through functional specifications (FSD)</small>
<p class="fragment">Instead use a user story, to capture initial user needs</p>
<ul>
<li class="fragment">Name, Intention, Criteria</li>
<li class="fragment">Make the user story as small as possible</li>
<li class="fragment">Make it testable (can write a test to verify it)</li>
<li class="fragment">Make it visible for all</li>
</ul>
</section>
<section>
<h2>Backlog</h2>
<table>
<tr>
<th>Product Backlog</th>
<th>Sprint Backlog</th>
</tr>
<tr>
<td>Through out the project lifetime</td>
<td>Within a sprint</td>
</tr>
<tr>
<td>Will grow/shrink</td>
<td>Must not grow</td>
</tr>
<tr>
<td>Should be within project constraints (scope/time/cost)</td>
<td>Should be within team's velocity </td>
</tr>
</table>
</section>
<section>
<h1>Agile Modelling</h1>
</section>
<section>
<h3>Get a user story from the customer</h3>
<img src="assets/xp/am_user_story.jpg"/>
</section>
<section>
<h3>Create a workflow model to better understand the user story</h3>
<img src="assets/xp/am_workflow.jpg" width="60%"/>
</section>
<section>
<h3>Develop mockup screens</h3>
<img src="assets/xp/am_mockup.jpg" width="40%"/>
</section>
<section>
<h3>Use mockups & workflow together to build data model</h3>
<img src="assets/xp/am_data_model.jpg" width="60%"/>
</section>
</section>
<section>
<section>
<h1>Agile Best Practices </h1>
</section>
<section>
<h1>Improving Velocity</h1>
<ul>
<li class="fragment">Pay down technical debt</li>
<li class="fragment">Improve customer involvement</li>
<li class="fragment">Provide needed resources</li>
<li class="fragment">Offload programmer duties (automate things)</li>
</ul>
</section>
<section>
<h1>Automation</h1>
<ul>
<li class="fragment">Automate the build (Ant/Maven/Gradle/NAnt)</li>
<li class="fragment">Hyperaware Editing (Infinitest/NCrunch)</li>
<li class="fragment">Automate the acceptance tests (Robot Framework / CodedUI)</li>
<li class="fragment">Continous Integration (Jenkins/TFS)</li>
</ul>
</section>
<section>
<h1>Improving Skills & Knowledge</h1>
<p class="fragment">Practice makes perfect</p>
<ul>
<li class="fragment">Allocate 20% of your time to develop skills</li>
<li class="fragment">One way is by doing: <b>Dojo</b> & <b>Kata</b></li>
<li class="fragment">Katas: <font class="fragment">Algorithm</font> <font class="fragment">> Game</font> <font class="fragment">> Technology</font><font class="fragment">> Architecture</font></li>
</ul>
</section>
<section>
<h1>Topless Meetings</h1>
<p>Why Successful People Never Bring Smartphones Into Meetings<sup>1</sup></p>
<ul>
<li class="fragment">Lack of respect</li>
<li class="fragment">Lack of attention</li>
<li class="fragment">Lack of listening</li>
<li class="fragment">Lack of power</li>
</ul>
<p style="position:absolute;bottom:0;width:100%; height:10px;"><font size="3">[1] http://www.forbes.com/sites/kevinkruse/2013/12/26/why-successful-people-never-bring-smartphones-into-meetings/</font></p>
</section>
<section>
<h1>Ad-hoc & Frequent Communications</h1>
<p>Face 2 Face > Video Conference > Phone > Message Chat > Nothing </p>
<img src="assets/scrum/ad_hoc_communication.jpg" width="70%"/>
</section>
<section>
<h1>Smaller Handoffs</h1>
<p class="fragment">Problem: By the time we finished delivering a feature, it's already too late for QA to do any acceptance testing (let alone regression testing)</p>
<p class="fragment"><i>Transfer small tasks frequently. Once a developer finished with one acceptance criteria, hand it over to QA to test just that criteria. The developer could continue with the next acceptance criteria</i></p>
</section>
<section>
<h4>Smaller Handoffs (continued)</h4>
<img class="fragment" src="assets/scrum/smaller_handoff_1.png" width="75%"/>
<img class="fragment" src="assets/scrum/smaller_handoff_2.png" width="75%"/>
</section>
<section>
<h4>Smaller Handoffs (continued)</h4>
<img class="fragment" src="assets/scrum/smaller_handoff_3.png" width="90%"/>
</section>
<section>
<h1>Product Review</h1>
<ul>
<li class="fragment">Tell, don't show (describe what the user story is about)</li>
<li class="fragment">Describe the impact (business value) of the functionality being presented</li>
<li class="fragment">If everything goes haywire ? Show the automated test result</li>
</ul>
</section>
<section>
<h1>Swarming</h1>
<ul>
<li class="fragment">Helps on knowledge sharing between team member. Also helps reducing communication between team member <> product owner.</li>
<li class="fragment">Boost confident of the team on taking/conquering more complex problem (mission critical applications)</li>
<li class="fragment">Collective Ownership of the whole application</li>
</ul>
</section>
<section>
<h2>Pair Programming & TDD</h2>
<ul>
<li class="fragment">They do work best together</li>
<li class="fragment"><font class="fragment">"Two heads are better than one"</font><font class="fragment">,"It takes two to tango"</font></li>
<li class="fragment"><font class="fragment"><b>Navigator</b> (Strategical)</font> <font class="fragment">+ <b>Driver</b> (Tactical)</font></li>
<li class="fragment">Great way to start is by doing <b>Fizz Buzz Kata</b></li>
<li class="fragment">TDD Structure: <b>Arrange</b>, <b>Act</b>, <b>Assert</b></li>
<li class="fragment">TDD Process: <font color="red" style="strong">Make test fail</font>, <font color="green" style="strong">Make test pass</font>, <font color="blue" style="strong">Refactor</font></li>
</ul>
</section>
<section>
<h2>Specification by Example (A-TDD)</h2>
<small>Tests as requirements, Requirements as tests</small>
<p>Discuss in workshop -> Develop in concurrence -> Deliver for acceptance</p>
<img src="assets/test_automation.jpg" width="50%" style="border:0px"/>
</section>
</section>
<section>
<h2>
Is scrum not your cup of tea ?
</h2>
<h3 class="fragment">
relax, we have other agile methodologies that might suit to your taste
</h3>
<ul>
<li class="fragment">Feature Driven Development</li>
<li class="fragment">Kanban</li>
<li class="fragment">eXtreme Programming</li>
</ul>
</section>
<div id="footer" style="position:absolute;bottom:0;width:100%; height:10px;"><strong><font size="3">13 March 2015 | Amri Hidayat</font></strong></div>
</div>
</div>
<script src="lib/js/head.min.js"></script>
<script src="js/reveal.js"></script>
<script>
// Full list of configuration options available at:
// https://github.com/hakimel/reveal.js#configuration
Reveal.initialize({
controls: true,
progress: true,
history: true,
center: true,
transition: 'convex', // none/fade/slide/convex/concave/zoom
// Optional reveal.js plugins
dependencies: [
{ src: 'lib/js/classList.js', condition: function() { return !document.body.classList; } },
{ src: 'plugin/markdown/marked.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'plugin/markdown/markdown.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'plugin/highlight/highlight.js', async: true, condition: function() { return !!document.querySelector( 'pre code' ); }, callback: function() { hljs.initHighlightingOnLoad(); } },
{ src: 'plugin/zoom-js/zoom.js', async: true },
{ src: 'plugin/notes/notes.js', async: true }
]
});
</script>
</body>
</html>