-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
executable file
·666 lines (550 loc) · 15 KB
/
index.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
<!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">
<title>Agile Al</title>
<link rel="stylesheet" href="css/reveal.css">
<link rel="stylesheet" href="css/theme/alprez.css">
<!-- Theme used for syntax highlighting of code -->
<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>
</head>
<body>
<div class="reveal">
<div class="slides">
<!-- Printing and PDF exports -->
<section>
<h1>Agile Al</h1>
</section>
<section>
Agile software development describes a <u>set of principles</u> for
software development under which requirements and solutions evolve through
the collaborative effort of <u>self-organizing cross-functional teams</u>. Based
off Agile Architecture, it advocates <u>adaptive planning</u>, <u>evolutionary
development</u>, <u>early delivery</u>, and <u>continuous improvement</u>, and it encourages
rapid and flexible response to change.
</section>
<section>
<section>
<h3>Agile</h3>
<ul>
<li>Formalized in 2001 in the Agile Manifesto</li>
<li>Agile was already a thing</li>
<li>This was just gathering the ideas of practices that were being very succesful at the time</li>
<li><a href="http://agilemanifesto.org/" target="_blank">http://agilemanifesto.org/</a></li>
</ul>
</section>
</section>
<section>
<section>
<h3>Agile Manifesto: Core Values</h3>
<ul>
<li>Individuals and interactions over processes and tools</li>
<li>Working software over comprehensive documentation</li>
<li>Customer collaboration over contract negotiation</li>
<li>Responding to change over following a plan</li>
</ul>
<br />
<br />
Value the items on the right...<br />
But more the items on the left
</section>
</section>
<section>
<section>
<h3>Agile Manifesto: 12 Principles</h3>
<ul>
<li>1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.</li>
<li>2. <u>Welcome changing requirements, even late in development</u>. Agile processes harness change for the customer's competitive advantage.</li>
<li>3. <u>Deliver working software frequently</u>, from a couple of weeks to a couple of months, with a preference to the shorter timescale.</li>
</ul>
</section>
<section>
<h3>Agile Manifesto: 12 Principles</h3>
<ul>
<li>4. Business people and developers must work together daily throughout the project.</li>
<li>5. <u>Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.</u></li>
<li>6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.</li>
</ul>
</section>
<section>
<h3>Agile Manifesto: 12 Principles</h3>
<ul>
<li>7.<u>Working software is the primary measure of progress.</u></li>
<li>8. Agile processes promote sustainable development.The sponsors, developers, and users should be able to maintain a constant pace indefinitely.</li>
<li>9. Continuous attention to technical excellence and good design enhances agility.</li>
</ul>
</section>
<section>
<h3>Agile Manifesto: 12 Principles</h3>
<ul>
<li>10. <u>Simplicity--the art of maximizing the amount of work not done--is essential.</u></li>
<li>11. The best architectures, requirements, and designs emerge from self-organizing teams.</li>
<li>12. <u>At regular intervals, the team reflects on how to become more effective</u>, then tunes and adjusts its behavior accordingly.</li>
</ul>
</section>
</section>
<section>
<section>
<h3>Types of Agile</h3>
<ul>
<li>Kanban</li>
<ul>
<li>Continual Delivery</li>
<li>No defined time frames</li>
</ul>
<li>Scrum</li>
<ul>
<li>Short sprints</li>
</ul>
<li>XP - Extreme Programming</li>
<li>TPS - Toyota Production System</li>
<ul>
<li>Just in time prodution</li>
</ul>
</ul>
</section>
</section>
<section>
<section>
<h1>Implementing Agile</h3>
</section>
<section>
<p>We start off herding cats</p>
<img src="./img/1110.png">
</section>
<section>
<p>We become more agile individually</p>
<img src="./img/1120.jpg">
</section>
<section>
<p>We reach Lean Mean Agile Team</p>
<img src="./img/1130.gif">
</section>
<section>
<p>But to get there, we need <u>change</u></p>
<img src="./img/1210.jpg">
</section>
</section>
<section>
<section>
<h1>Scrum Structure</h1>
<img src="./img/1300.jpg">
</section>
</section>
<section>
<section>
<h3>Scrum - Sprint</h3>
<ul>
<li>Predefined size sprints</li>
<li>Short, generally 2 weeks to a month</li>
<li>We use 2 weeks</li>
<li>At the end of a sprint, a release is done</li>
<ul>
<li>Used to do this in JCI</li>
<li>Working on in CPower</li>
</ul>
</ul>
</section>
</section>
<section>
<section>
<h3>Scrum - Stories</h3>
<ul>
<li>Often lots of mystery here, but should not be</li>
<li>Just a description of work</li>
<ul>
<li>Understandable to all</li>
</ul>
</ul>
</section>
<section>
<ul>
<li>Sized in a general way</li>
<ul>
<li>Like big/small/medium</li>
<li><u>Not</u> a time estimate</li>
<li>Provides a feature which can be implemented</li>
<li>Fits in a sprint</li>
</ul>
<li>Stories get broken into tasks</li>
<ul>
<li>Assignable to a team member</li>
<li>Have actual time estimates, ideally not more than 8 hours</li>
</ul>
</ul>
</section>
<section>
<ul>
<li>Stories have a general description</li>
<ul>
<li>Including why this is useful</li>
</ul>
<li>Stories have a very precise set of acceptance criteria</li>
<ul>
<li>This defines what is required for the story to be considered done</li>
<li>Conversely, implies that if the criteria is met then the story is done</li>
</ul>
</ul>
</section>
</section>
<section>
<section>
<h3>Scrum - Backlog</h3>
<ul>
<li>As stories are generated they are placed in a list</li>
<li>This is the backlog</li>
<li>In priority sequence</li>
</ul>
</section>
</section>
<section>
<section>
<h3>Scrum - Velocity</h3>
<ul>
<li>Calculation of how much a team member can do in a sprint</li>
</ul>
</section>
<section>
<ul>
<li>Calculated at beginning of each sprint </li>
<ul>
<li>Includes allowance for Scrum meetings</li>
<li>Includes special items for the sprint</li>
<ul>
<li>Vacations</li>
<li>Business training</li>
<li>Anything which means not availble to work on sprint</li>
</ul>
</ul>
</ul>
</section>
<section>
<ul>
<li>Group can select tasks for each person until reach velocity limit</li>
</ul>
</section>
</section>
<section>
<section>
<h3>Scrum - Burndown</h3>
<ul>
<li>Each task has a running estimate of remaining hours</li>
<li>This remaining time is displayed as a Burndown Chart</li>
</ul>
</section>
<section>
<h3>Scrum - Burndown</h3>
<img src="./img/1310.png">
</section>
</section>
<section>
</section>
<section>
<section>
<h3>Scrum Roles</h3>
<img src="./img/1350.jpg">
</section>
</section>
<section>
<section>
<h3>Product Owner</h3>
<ul>
<li>Responsible for maximizing the value of the product and the work of the team.</li>
<li>Is a person, not a committee</li>
<ul>
<li>May represent the direction of a committee</li>
<li>But anyone wanting to change the product backlog must go through prodcut owner</li>
</ul>
<li>How role is done can vary widely between teams</li>
</ul>
</section>
<section>
<h3>Product Owner Responsible for... </h3>
<ul>
<li>Clearly expressing backlog items</li>
<li>Ordering backlog items to best acheive goals</li>
</ul>
</section>
<section>
<li>Product Owner may do the work directly</li>
<li>Or may have team do it</li>
<li>But remains responsible</li>
</ul>
</section>
</section>
<section>
<section>
<h3>Development Team</h3>
<ul>
<li>Group of people who deliver a potentially releasble increment of done work at the end of each sprint</li>
</ul>
</section>
<section>
<ul>
<li>Empowered by the organiztion to manage their own work</li>
<li>The work being to turn product backlog items into the releasable increments</li>
<li>Scrum recognizes no titles other than Developer</li>
<li>Scrum recognizes no sub-teams regardless of specialized domains</li>
<li>Team members may have specialized skills or focus, but accountabililty belongs to the team as a whole</li>
</ul>
</section>
</section>
<section>
<section>
<h3>Scrum Master</h3>
<ul>
<li>Provide expertise about Scrum process</li>
<li>Schedules and runs Scrum meetings</li>
<li>Removes obstacles for the team</li>
<li>Actually has huge list of potential responsibilities all
dealing with the goal of helping the Product Manager and
the Development Team use Scrum effectively
</li>
</ul>
</section>
</section>
<section>
</section>
<section>
<section>
<h3>Scrum Meetings (Ceremonies)</h3>
<img src="./img/1410.jpg">
</section>
</section>
<section>
<section>
<h3>Scrum Meetings</h3>
<ul>
<li>Most are done each sprint</li>
<li>The ongoing process of "how we work the sprint"</li>
</ul>
</section>
</section>
<section>
<section>
<h3>Grooming</h3>
<ul>
<li>Process of refining a story so it is ready to be worked</li>
<li>Is done by the team</li>
<ul>
<li>Though as we do it can often be done by a subset of the team</li>
</ul>
<li>It is possible that a story will be groomed multiple times</li>
<ul>
<li>Process of refinement, getting additional information</li>
</ul>
</ul>
</section>
<section>
<ul>
<li>Ideally happens 2-4 times during a sprint preparing for future sprint</li>
<ul>
<li>Though we do once a sprint</li>
</ul>
<li>Ideally have 2-3 sprints worth of work groomed at any point in time</li>
<ul>
<li>Not end of the world if not</li>
<li>But both future grooming and planning processes will be much less smooth</li>
</ul>
</ul>
</section>
</section>
<section>
<section>
<h3>Planning</h3>
<ul>
<li>Process of loading a sprint with work</li>
<li>Is done by the team</li>
<li>At this point stories potentially going into the sprint should be fully groomed</li>
<li>Some discussion as to whether tasks are developed here, or before</li>
<ul>
<li>We found doing tasks in the planning meeting made for painfully long planning meetings</li>
</ul>
</ul>
</section>
</section>
<section>
<section>
<h3>DSU / Daily Standup</h3>
<ul>
<li>A quick team catchup</li>
<li>Every day</li>
<li>Is attended by the entire team</li>
<li>Short! 15 minutes</li>
</ul>
</section>
<section>
<ul>
<li>Everyone gives an update</li>
<ul>
<li>What I did since that last DSU</li>
<li>What I'm planning to do in the next period</li>
<li>Items where I may need help</li>
<li>Issues/problems that may jeapordize the delivery of the sprint work</li>
</ul>
</ul>
</section>
<section>
<ul>
<li>The DSU is used to identify and bring up issues</li>
<li>It is not the place to discuss in depth nor solve them</li>
</section>
</section>
<section>
<section>
<h3>Demo</h3>
<ul>
<li>Just what it sounds like, a demo</li>
<li>At end of sprint</li>
<li>Actually showing the result of work done in sprint</li>
<li>Entire team</li>
<li>Users / stakeholders, though attendance may vary by content</li>
</ul>
</section>
<section>
<ul>
<li>Easy to skip, but important not to</li>
</ul>
</section>
</section>
<section>
<section>
<h3>Retro</h3>
<ul>
<li>Entire team</li>
<li>Open discussion of how sprint went, good and bad</li>
<li>Important to encourage and allow discussion</li>
<li>Provides input for continual improvement of the process, tailored to the team.</li>
</ul>
</section>
</section>
<section>
<section>
<h3>Testing</h3>
<ul>
<li>Not technically part of scrum</li>
<ul>
<li>Though is embraced by agile in general</li>
</ul>
<li>Doing a release every sprint implies doing regression testing every sprint</li>
<li>So any level of automated testing is a plus</li>
<ul>
<li>But more coverage is better</li>
</ul>
</ul>
</section>
</section>
<section>
</section>
<section>
<h1>Agile ala us</h1>
</section>
<section>
<section>
<h3>As we do it</h3>
<ul>
<li>Use Scrum</li>
<li>Learned under a variant called SAFe (Scaled Agile Framework)</li>
<ul>
<li>Used Scrum as base</li>
<li>But provides additional processes to allow Scrum teams to cooridinate with other scrum teams in larger network</li>
</ul>
</ul>
</section>
</section>
<section>
<section>
<h3>TFS</h3>
<ul>
<li>Use for source control</li>
<li>But also use as our set of Scrum managment tools</li>
<li>Helps with the multiple locations</li>
<li>Makes information and status available to anyone, anytime</li>
</ul>
</section>
</section>
<section>
<section>
<h3>Some challenges</h3>
<ul>
<li>Relative newness to scrum</li>
<li>Different experience levels in use of scrum</li>
<li>Above includes both team members and users</li>
<li>Remote - especially as pertains to devs</li>
</ul>
</section>
</section>
<section>
<section>
<h3>All or Nothing?</h3>
<ul>
<li>Do all teams have to be agile/scrum?</li>
<li>Would be nice, but not required</li>
<li>Useful to have other teams aware that we use it</li>
<li>And how we use it</li>
</ul>
</section>
</section>
<section>
<section>
<h3>Backlog Organization</h3>
<ul>
<li>At this point we were finding some dificulty keeping items from major areas visible</li>
<li>We use three sections in the backlog</li>
<ul>
<li>Roadmap - For some of the major direction for the compay</li>
<li>Strategic - For the work to kepp the company running</li>
<li>Technical - For the work to keep the infrastucture running and progressing</li>
</ul>
</ul>
</section>
</section>
<section>
</section>
<section>
<h1>TFS Demo</h1>
</section>
<section>
</section>
<section>
<img src="./img/9910.jpg">
</section>
<section>
<section>
<h3></h3>
<ul>
<li></li>
<li></li>
<li></li>
</ul>
</section>
</section>
<!-- Printing and PDF exports -->
</div>
</div>
<script src="lib/js/head.min.js"></script>
<script src="js/reveal.js"></script>
<script>
// More info https://github.com/hakimel/reveal.js#configuration
Reveal.initialize({
history: true,
// More info https://github.com/hakimel/reveal.js#dependencies
dependencies: [
{ src: 'plugin/markdown/marked.js' },
{ src: 'plugin/markdown/markdown.js' },
{ src: 'plugin/notes/notes.js', async: true },
{ src: 'plugin/highlight/highlight.js', async: true, callback: function() { hljs.initHighlightingOnLoad(); } }
]
});
</script>
</body>
</html>