-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathdevops-checklist.html
666 lines (626 loc) · 39.3 KB
/
devops-checklist.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 lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<!-- Google font -->
<link href="https://fonts.googleapis.com/css?family=Lato:700%7CMontserrat:400,600" rel="stylesheet">
<!-- Bootstrap -->
<link type="text/css" rel="stylesheet" href="css/bootstrap.min.css"/>
<!-- Font Awesome Icon -->
<link rel="stylesheet" href="css/font-awesome.min.css">
<!-- Custom stlylesheet -->
<link type="text/css" rel="stylesheet" href="css/style.css"/>
<!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media queries -->
<!-- WARNING: Respond.js doesn't work if you view the page via file:// -->
<!--[if lt IE 9]>
<script src="https://oss.maxcdn.com/html5shiv/3.7.3/html5shiv.min.js"></script>
<script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
<![endif]-->
<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src="https://www.googletagmanager.com/gtag/js?id=UA-133680862-1"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag() { dataLayer.push(arguments); }
gtag('js', new Date());
gtag('config', 'UA-133680862-1');
</script>
<meta name="description" content="DevOps Taiwan 社群獲得 DevOps Checklist 網站作者 Steve Pereira 授權，將其翻譯為繁體中文。針對中文翻譯有任何建議，歡迎回饋或送 PR，謝謝">
<meta property="og:image" content="http://devopstw.club/img/fotos/5.jpg">
<meta property="og:url" content="http://devopstw.club">
<meta property="og:description" content="DevOps Taiwan 社群獲得 DevOps Checklist 網站作者 Steve Pereira 授權，將其翻譯為繁體中文。針對中文翻譯有任何建議，歡迎回饋或送 PR，謝謝">
<meta property="og:site_name" content="DevOps Taiwan Community | DevOps 台灣社群 | DevOps Checklist">
<title>DevOps Taiwan Community | DevOps 台灣社群</title>
<link rel="apple-touch-icon" sizes="57x57" href="icon/apple-icon-57x57.png">
<link rel="apple-touch-icon" sizes="60x60" href="icon/apple-icon-60x60.png">
<link rel="apple-touch-icon" sizes="72x72" href="icon/apple-icon-72x72.png">
<link rel="apple-touch-icon" sizes="76x76" href="icon/apple-icon-76x76.png">
<link rel="apple-touch-icon" sizes="114x114" href="icon/apple-icon-114x114.png">
<link rel="apple-touch-icon" sizes="120x120" href="icon/apple-icon-120x120.png">
<link rel="apple-touch-icon" sizes="144x144" href="icon/apple-icon-144x144.png">
<link rel="apple-touch-icon" sizes="152x152" href="icon/apple-icon-152x152.png">
<link rel="apple-touch-icon" sizes="180x180" href="icon/apple-icon-180x180.png">
<link rel="icon" type="image/png" sizes="192x192" href="icon/android-icon-192x192.png">
<link rel="icon" type="image/png" sizes="32x32" href="icon/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="96x96" href="icon/favicon-96x96.png">
<link rel="icon" type="image/png" sizes="16x16" href="icon/favicon-16x16.png">
</head>
<body>
<!-- Header -->
<header id="header" class="transparent-nav">
<div class="container">
<div class="navbar-header">
<!-- Logo -->
<div class="navbar-brand">
<a class="logo" href="index.html">
<img src="./img/devops_logo-alt.png" alt="logo">
</a>
</div>
<!-- /Logo -->
<!-- Mobile toggle -->
<button class="navbar-toggle">
<span></span>
</button>
<!-- /Mobile toggle -->
</div>
<!-- Navigation -->
<nav id="nav">
<ul class="main-menu nav navbar-nav navbar-right">
<li><a href="https://devopstw.club/#meetup">活動資訊</a></li>
<li><a href="https://devopstw.club/#about">關於我們</a></li>
<li><a href="https://github.com/DevOpsTW/jobs/issues">徵才資訊</a></li>
<li><a href="http://cfs.devopstw.club/">投稿</a></li>
<li><a href="http://sponsor.devopstw.club/">贊助與合作</a></li>
<li><a href="https://devopstw.club/devops-checklist.html">DevOps Checklist</a></li>
<li><a href="https://devopsdays.tw">DevOpsDays Taipei</a></li>
</ul>
</nav>
<!-- /Navigation -->
</div>
</header>
<!-- /Header -->
<!-- Home -->
<div id="home" class="hero-area">
<!-- Backgound Image -->
<div class="bg-image bg-parallax overlay" style="background-image:url(./img/header.jpg)"></div>
<!-- /Backgound Image -->
<div class="home-wrapper">
<div class="container">
<div class="row">
<div class="col-md-8">
<h1 class="white-text">DevOps Checklist 繁體中文翻譯</h1>
<p class="lead white-text">DevOps Checklist 的版權屬於<a href="http://devopschecklist.com/" style="color: white;">原網站</a>所有，DevOps Taiwan 社群已取得原網站作者 Steve Pereira 授權得以翻譯並公開發佈繁體中文。</p>
<a class="main-button icon-button" href="http://fb.devopstw.club">立即瀏覽</a>
</div>
</div>
</div>
</div>
</div>
<!-- /Home -->
<div id="about" class="section">
<!-- container -->
<div class="container">
<!-- row -->
<div class="row">
<section id="sponsor">
<div class="container">
<div class="row">
<div class="col-lg-12 text-center">
<h2 class="section-heading">Alignment</h2>
<hr class="primary">
<p class="description">統合團體與個人的方向及目標，讓組織航向超凡願景。</p>
</div>
<div>
<ul class="check-list">
<li class="check-item filter-item i1 culture">
我們會根據業務目標（business objectives）決定任務的優先順序。
</br><span class="more">DevOps is all about alignment. It was born out of frustration and trouble between the disparate priorities and incentives of Development and Operations teams. Alignment comes from unifying towards a common goal.</span>
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
</ul>
</li>
<li class="check-item filter-item i2 culture">
比起被動的任務分配，我們更傾向主動認領任務。
</br><span class="more">Autonomy is a critical facet to motivation and job satisfaction. By allowing team members to self-select tasks, you'll see them work on what they're best suited to complete.</span>
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
</ul>
</li>
<li class="check-item filter-item i3 culture measurement">
我們的團隊擁有明確符合公司願景的團隊目標。
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
<li class="filter-item Measurement"><span class="label label-info">Measurement</span></li>
</ul>
</li>
<li class="check-item filter-item i4 culture automation measurement">
我們的產品團隊注重可永續的開發步調，而並非當下的速度。
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
<li class="filter-item automation"><span class="label label-info">Automation</span></li>
<li class="filter-item Measurement"><span class="label label-info">Measurement</span></li>
</ul>
</li>
<li class="check-item filter-item i5 culture measurement">
比起在意系統可以正常運作多久不發生問題，我們更在意需要花費更少時間將問題修復。
</br><span class="more">A great deal of software delivery theory actually stems from manufacturing. The major difference is that testing failure is faster, cheaper and non-destructive. Thus, we focus on early failure detection through automated testing, as far upstream as possible to catch issues before they become costly. We also focus on learning from simulating production failure by staging <a href="https://stripe.com/blog/game-day-exercises-at-stripe" target="_blank">'Game Days'</a>, <a href="http://www.pagerduty.com/blog/failure-friday-at-pagerduty/" target="_blank">'Failure Fridays'</a> and optimizing reaction time and corrective process.</span>
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
<li class="filter-item Measurement"><span class="label label-info">Measurement</span></li>
</ul>
</li>
<li class="check-item filter-item i6 culture">
在我們的組織當中，DevOps 並非是某個被分別出來的角色。
</br><span class="more">Hiring a 'DevOps engineer' is an antipattern because it charges an individual with understanding and operating in two worlds with their respective opposing incentives, while remaining independent of either, as their own silo. Even more confusing is reconciling that position with a larger organizational DevOps pursuit. Hiring an Automation, Systems, Operations or Development engineer specifically, or just simply an engineer would be more humane and doesn't require you to write a manifesto for your job descriptions. For more info on hiring for DevOps, see <a href="http://www.oreilly.com/webops-perf/free/devops-hiring.csp">O'Reilly's free book.</a></span>
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
</ul>
</li>
<li class="check-item filter-item i7 culture">
在我們的組織當中，DevOps 也並非是某個被分別出來的團隊。
</br><span class="more">DevOps works best as a cross-functional team focus. Large organizations have often seen success with an exploratory task force team or a greenfield project team, but in order to get optimal results every team should be able to build and deliver without relying on another department. Vote no on silos!</span>
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
</ul>
</li>
<li class="check-item filter-item i8 culture">
對我們而言，「維運」（Operations）功效也同樣被視為是組織競爭優勢的來源之一。
</br><span class="more">A large part of why DevOps exists is in reaction to common perceptions of IT as a cost to an organization, yet we now know it can just as easily be a source of innovation.</span>
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
</ul>
</li>
</ul>
</div>
</div>
</div>
</section>
<section id="sponsor">
<div class="container">
<div class="row">
<div class="col-lg-12 text-center">
<h2 class="section-heading">Context</h2>
<hr class="primary">
<p class="description">提供相關資訊給隨時有需要的人。</p>
</div>
<div>
<ul class="check-list">
<li class="check-item filter-item i9 culture sharing">
在開發團隊的衝刺規劃會議（Sprint Planning ）中，維運團隊的代表也被邀請參與其中。
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
<li class="filter-item sharing"><span class="label label-info">Sharing</span></li>
</ul>
</li>
<li class="check-item filter-item i10 culture sharing">
我們讓產品團隊的所有成員都能看到潛在的改變（變革）。
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
<li class="filter-item sharing"><span class="label label-info">Sharing</span></li>
</ul>
</li>
<li class="check-item filter-item i11 culture sharing">
我們擁有一個自動化的系統來執行任務，並且能夠透過團隊的即時通訊工具接收到相關的通知。
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
<li class="filter-item sharing"><span class="label label-info">Sharing</span></li>
</ul>
</li>
<li class="check-item filter-item i12 culture sharing">
在設計系統時，我們定期與審計和監管單位（部門）諮詢並尋求指導。
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
<li class="filter-item sharing"><span class="label label-info">Sharing</span></li>
</ul>
</li>
<li class="check-item filter-item i13 culture sharing">
我們鼓勵團隊針對任務及其優先順序提出質疑。
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
<li class="filter-item sharing"><span class="label label-info">Sharing</span></li>
</ul>
</li>
<li class="check-item filter-item i14 sharing">
我們擁有一個集中的即時通訊系統，並且產品團隊的所有成員都加入在其中。
<ul class="tags">
<li class="filter-item sharing"><span class="label label-info">Sharing</span></li>
</ul>
</li>
<li class="check-item filter-item i15 sharing measurement">
產品團隊的所有成員都擁有權限可以存取環境狀態、相關指標和歷史紀錄。
<ul class="tags">
<li class="filter-item sharing"><span class="label label-info">Sharing</span></li>
<li class="filter-item measurement"><span class="label label-info">Measurement</span></li>
</ul>
</li>
<li class="check-item filter-item i16 sharing measurement">
產品團隊的所有成員都擁有權限可以存取程式碼的狀態、相關指標和歷史紀錄。
<ul class="tags">
<li class="filter-item sharing"><span class="label label-info">Sharing</span></li>
<li class="filter-item measurement"><span class="label label-info">Measurement</span></li>
</ul>
</li>
</ul>
</div>
</div>
</div>
</section>
<section id="sponsor">
<div class="container">
<div class="row">
<div class="col-lg-12 text-center">
<h2 class="section-heading">Learning</h2>
<hr class="primary">
<p class="description">藉由「持續改善」（Continuous Improvement）來強化個人成長和培養團隊的相互理解。</p>
</div>
<div>
<ul class="check-list">
<li class="check-item filter-item i17 culture">
我們在組織當中陶冶一種持續學習的環境。
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
</ul>
</li>
<li class="check-item filter-item i18 culture">
我們會定期為了團隊所獲得的學習與成功而慶祝。
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
</ul>
</li>
<li class="check-item filter-item i19 culture sharing">
我們會定期與我們組織的其他夥伴分享我們產品團隊的學習和成功。
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
<li class="filter-item sharing"><span class="label label-info">Sharing</span></li>
</ul>
</li>
<li class="check-item filter-item i20 culture sharing measurement">
我們公開討論過失，藉此共同學習。
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
<li class="filter-item sharing"><span class="label label-info">Sharing</span></li>
<li class="filter-item measurement"><span class="label label-info">Measurement</span></li>
</ul>
</li>
<li class="check-item filter-item i21 culture measurement">
我們能夠識別必需的技能並改進之以應對未來目標。
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
<li class="filter-item measurement"><span class="label label-info">Measurement</span></li>
</ul>
</li>
<li class="check-item filter-item i22 culture measurement">
我們會長期不畏艱難地持續檢視我們是如何完成我們的工作，以及我們又是如何有效地完成工作。
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
<li class="filter-item measurement"><span class="label label-info">Measurement</span></li>
</ul>
</li>
<li class="check-item filter-item i23 measurement">
我們所進行的預估、推估是建立於度量及過往歷史經驗的基礎之上。
<ul class="tags">
<li class="filter-item measurement"><span class="label label-info">Measurement</span></li>
</ul>
</li>
</ul>
</div>
</div>
</div>
</section>
<section id="sponsor">
<div class="container">
<div class="row">
<div class="col-lg-12 text-center">
<h2 class="section-heading">Lifecycle</h2>
<hr class="primary">
<p class="description">在日新又新的生態系中，專注於軟體上，並將其視為是值得關照、關注和深思的產品。</p>
</div>
<div>
<ul class="check-list">
<li class="check-item filter-item i24 culture">
我們的軟體開發週期為2週，或少於2週。
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
</ul>
</li>
<li class="check-item filter-item i25 culture measurement">
我們的軟體開發週期是以將能正常運作之軟體異動發佈，並部署至正式運行環境來界定的。
</br><span class="more">Iterative development and process optimization depends on repeatedly performing the critical functions of building and deploying software. The more it's done, the better it's understood, the easier it is to improve and automate.</span>
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
<li class="filter-item measurement"><span class="label label-info">Measurement</span></li>
</ul>
</li>
<li class="check-item filter-item i26 culture">
我們一旦發現缺陷，會先暫停開發工作，評估缺陷以決定修復它的優先順序
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
</ul>
</li>
<li class="check-item filter-item i27 culture automation">
開發人員或產品負責人（product owner）都能夠將我們的產品部署到正式運行環境。
</br><span class="more">The focus here is empowering the most informed to perform the task. Someone intimately familiar with a change is best positioned to evaluate its performance and correctness. Developers and POs should be empowered to measure and visualize the operation of the change as well, in order to give them a holistic view of the changed system.</span>
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
<li class="filter-item automation"><span class="label label-info">Automation</span></li>
</ul>
</li>
<li class="check-item filter-item i28 automation testing">
在自動化部署至正式運行環境之前，我們都有進行自動化測試。
</br><span class="more">Production deploys can still be manually initiated in cases where a signoff is required, yet the testing, deployment process and validation should be entirely automated to ensure consistency, accuracy and optimal speed. Automating deploys means no copy and paste, less security risk, more auditability, more confidence.</span>
<ul class="tags">
<li class="filter-item automation"><span class="label label-info">Automation</span></li>
<li class="filter-item testing"><span class="label label-info">Testing</span></li>
</ul>
</li>
<li class="check-item filter-item i29 automation">
我們的系統組態（configuration）設定是自動化的。
</br><span class="more">Friends don't let friends manually configure systems.</span>
<ul class="tags">
<li class="filter-item automation"><span class="label label-info">Automation</span></li>
</ul>
</li>
<li class="check-item filter-item i30 automation">
我們所部署的系統組態（system configuration）是不可變的（immutable）。
</br><span class="more">Immutability is an ideal state as it allows operations to focus on optimizing consistent and predictable systems.</span>
<ul class="tags">
<li class="filter-item automation"><span class="label label-info">Automation</span></li>
</ul>
</li>
<li class="check-item filter-item i31 automation testing">
我們發佈和部署的自動化沒有被環境綁定。
</br><span class="more">To avoid fragmentation or repetition, it's best to limit environmental differences to variable values only.</span>
<ul class="tags">
<li class="filter-item automation"><span class="label label-info">Automation</span></li>
<li class="filter-item testing"><span class="label label-info">Testing</span></li>
</ul>
</li>
</ul>
</div>
</div>
</div>
</section>
<section id="sponsor">
<div class="container">
<div class="row">
<div class="col-lg-12 text-center">
<h2 class="section-heading">Organization</h2>
<hr class="primary">
<p class="description">提供一個具備互動與凝聚力的組織架構，作為協作與生產力（工作效率）的後盾。</p>
</div>
<div>
<ul class="check-list">
<li class="check-item filter-item i32 culture sharing">
我們擁有的領域專業知識與經驗並不會只侷限在某些人員身上。
</br><span class="more">If you're lucky, you're surrounded by experts. Ideally, they're not just islands of knowledge and responsibility, but part of a peer group within the organization.</span>
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
<li class="filter-item sharing"><span class="label label-info">Sharing</span></li>
</ul>
</li>
<li class="check-item filter-item i33 culture sharing testing">
針對異動（changes），我們允許進行跨部門或同儕之間的審查（review）
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
<li class="filter-item sharing"><span class="label label-info">Sharing</span></li>
<li class="filter-item testing"><span class="label label-info">Testing</span></li>
</ul>
</li>
<li class="check-item filter-item i34 culture">
我們的組織是圍繞著跨職能團隊進行配置的。
</br><span class="more">Cross-functional teams are more empowered to build and deploy their own software without being hindered by constraints. They also avoid an 'us vs them' effect of siloed functional teams, learn from, and foster awareness and empathy for eachothers priorities and interests.</span>
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
</ul>
</li>
<li class="check-item filter-item i35 culture">
我們的團隊是以客戶和產品為導向的。
</br><span class="more">Customer focus helps align teams towards valuable goals, and keeps development and engineering zeroed in on delivery and processing feedback.</span>
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
</ul>
</li>
<li class="check-item filter-item i36 culture sharing">
我們會定期審查（review）優先事項。
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
<li class="filter-item sharing"><span class="label label-info">Sharing</span></li>
</ul>
</li>
<li class="check-item filter-item i37 automation testing">
我們的開發人員能夠自助自理在類正式運行的系統上工作並進行測試。
<ul class="tags">
<li class="filter-item automation"><span class="label label-info">Automation</span></li>
<li class="filter-item testing"><span class="label label-info">Testing</span></li>
</ul>
</li>
<li class="check-item filter-item i38 automation testing">
我們的開發人員能夠自助使用類正式運行環境的資料（數據）進行工作與測試。
<ul class="tags">
<li class="filter-item automation"><span class="label label-info">Automation</span></li>
<li class="filter-item testing"><span class="label label-info">Testing</span></li>
</ul>
</li>
<li class="check-item filter-item i39 automation testing">
我們的開發人員能夠自助存取在建置和測試軟體時所需的一切相依性（dependencies）。
<ul class="tags">
<li class="filter-item automation"><span class="label label-info">Automation</span></li>
<li class="filter-item testing"><span class="label label-info">Testing</span></li>
</ul>
</li>
</ul>
</div>
</div>
</div>
</section>
<section id="sponsor">
<div class="container">
<div class="row">
<div class="col-lg-12 text-center">
<h2 class="section-heading">Process</h2>
<hr class="primary">
<p class="description">擁有精心打造的儀式（老規矩），培養一貫與信心，能夠為持續改善提供一個框架。</p>
</div>
<div>
<ul class="check-list">
<li class="check-item filter-item i40 culture">
我們的組織遵循敏捷開發實踐。（Agile Development）
</br><span class="more">To realize the full power of a focus on DevOps, feedback and regular iteration are critical. <a href="http://www.agileweboperations.com/lean-agile-devops-related" target="_blank">DevOps is built on agile.</a></span>
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
</ul>
</li>
<li class="check-item filter-item i41 culture sharing">
我們已在團隊內實行「不咎責的事後檢討」（blameless postmortems）
</br><span class="more">Focus on learning and continual improvement. This is the human equivalent of focusing on MTTR vs MTBF. Read: <a href="https://codeascraft.com/2012/05/22/blameless-postmortems/" target="_blank">John Allspaw's great article on Etsy's process</a></span>
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
<li class="filter-item sharing"><span class="label label-info">Sharing</span></li>
</ul>
</li>
<li class="check-item filter-item i42 culture measurement">
我們定期檢查軟體交付過程中的各種限制。
<ul class="tags">
<li class="filter-item culture"><span class="label label-info">Culture</span></li>
</ul>
</li>
<li class="check-item filter-item i43 automation testing">
我們的系統組態（system configuration）有進行版本控制。
<ul class="tags">
<li class="filter-item automation"><span class="label label-info">Automation</span></li>
<li class="filter-item testing"><span class="label label-info">Testing</span></li>
</ul>
</li>
<li class="check-item filter-item i44 sharing">
我們的文件（documentation）有進行版本控制，並且是團隊共享的。
<ul class="tags">
<li class="filter-item sharing"><span class="label label-info">Sharing</span></li>
</ul>
</li>
<li class="check-item filter-item i45 sharing">
我們會維護一份任務待辦清單，所有團隊成員都可以查看並提供意見與評論。
<ul class="tags">
</ul>
</li>
<li class="check-item filter-item i46 testing">
我們已在團隊內實行 TDD 或 BDD
<ul class="tags">
<li class="filter-item testing"><span class="label label-info">Testing</span></li>
</ul>
</li>
<li class="check-item filter-item i47 testing">
我們會將程式碼（支線）合併到主線來測試我們的異動
</br><span class="more">Until you prove your code isn't a destructive regression, it shouldn't be deployed for someone else to discover. Automated testing and frequent merging should catch most of these issues, and make sure you don't find out about problems from someone else - or worse, Twitter.</span>
<ul class="tags">
<li class="filter-item testing"><span class="label label-info">Testing</span></li>
</ul>
</li>
<li class="check-item filter-item i48 testing">
我們會比照正式運行環境的負載量以及使用模式，來測試我們的軟體更動
<ul class="tags">
<li class="filter-item testing"><span class="label label-info">Testing</span></li>
</ul>
</li>
</ul>
</div>
</div>
</div>
</section>
</div>
</div>
</div>
<div id="about" class="section bg-primary">
<!-- container -->
<div class="container">
<!-- row -->
<div class="row">
<div class="col-lg-8 col-lg-offset-2 text-center">
<p class="thank-you">
關於這份 DevOps Checklist 有任何的想法與回饋，您可以直接回覆給<a style="color: #FFF; text-decoration: underline" href="http://devopschecklist.com/">原網站</a>之連絡信箱 [email protected]。如針對中文翻譯有任何意見，歡迎<a style="color: #FFF; text-decoration: underline" href="https://github.com/DevOpsTW/devopstw.club">回饋或發送 PR 給 DevOps Taiwan 社群</a>，謝謝！
</p>
<h2>References</h2>
<p><a style="color: #FFF; text-decoration: underline" href="https://www.youtube.com/watch?v=LdOe18KhtT4" target="_blank">10+ Deploys a Day: Dev and Ops Cooperation at Flickr</a></p>
<p><a style="color: #FFF; text-decoration: underline" href="http://www.thoughtworks.com/continuous-integration" target="_blank">Continuous Integration</a></p>
<p><a style="color: #FFF; text-decoration: underline" href="http://continuousdelivery.com" target="_blank">Continuous Delivery</a></p>
<p><a style="color: #FFF; text-decoration: underline" href="http://itrevolution.com/books/phoenix-project-devops-book" target="_blank">The Phoenix Project</a></p>
<p><a style="color: #FFF; text-decoration: underline" href="http://devopsdays.org" target="_blank">DevOpsDays Conferences</a></p>
<p><a style="color: #FFF; text-decoration: underline" href="http://devopsweekly.com" target="_blank">DevOps Weekly</a></p>
<p><a style="color: #FFF; text-decoration: underline" href="http://scrumguides.org" target="_blank">Scrum Guides</a></p>
<p><a style="color: #FFF; text-decoration: underline" href="http://ixdchecklist.com" target="_blank">Myplanet's IxD Checklist</a></p>
<p><a style="color: #FFF; text-decoration: underline" href="http://www.partnersforlearning.com/questions.php" target="_blank">Dimensions of the Learning Organization</a></p>
<p><a style="color: #FFF; text-decoration: underline" href="https://www.deming.org/theman/theories/fourteenpoints" target="_blank">Deming's Fourteen Points of Management</a></p>
<p>DevOps Checklist 的版權屬於<a style="color: #FFF; text-decoration: underline" href="http://devopschecklist.com/">原網站</a>所有，DevOps Taiwan 社群已取得原網站作者 Steve Pereira 授權得以翻譯並公開發佈繁體中文。</p>
</div>
</div>
</div>
</div>
<section id="meetup" class="bg-primary">
<div class="container">
<div class="row">
</div>
</div>
</section>
<!-- Footer -->
<footer id="footer" class="section">
<!-- container -->
<div class="container">
<!-- row -->
<div class="row">
<!-- footer logo -->
<div class="col-md-4">
<div class="footer-logo">
<a class="logo" href="index.html">
<img src="./img/devops_logo.png" alt="logo">
</a>
</div>
</div>
<!-- footer logo -->
<!-- footer nav -->
<div class="col-md-8">
<ul class="footer-nav">
<li><a href="https://devopstw.club/#meetup">活動資訊</a></li>
<li><a href="https://devopstw.club/#about">關於我們</a></li>
<li><a href="https://github.com/DevOpsTW/jobs/issues">徵才資訊</a></li>
<li><a href="http://cfs.devopstw.club/">投稿</a></li>
<li><a href="http://sponsor.devopstw.club/">贊助與合作</a></li>
<li><a href="https://devopstw.club/devops-checklist.html">DevOps Checklist</a></li>
<li><a href="https://devopsdays.tw">DevOpsDays Taipei</a></li>
</ul>
</div>
<!-- /footer nav -->
</div>
<!-- /row -->
<!-- row -->
<div id="bottom-footer" class="row">
<!-- social -->
<div class="col-md-4 col-md-push-8">
<ul class="footer-social">
<li><a href="https://www.facebook.com/DevOpsTaiwan/" class="facebook"><i class="fa fa-facebook"></i></a></li>
<li><a href="https://www.facebook.com/groups/DevOpsTaiwan/" class="facebook"><i class="fa fa-facebook"></i></a></li>
<li><a href="https://www.youtube.com/channel/UC401Z2pUq-Y37ayeeSprXSg" class="youtube"><i class="fa fa-youtube"></i></a></li>
</ul>
</div>
<!-- /social -->
<!-- copyright -->
<div class="col-md-8 col-md-pull-4">
<div class="footer-copyright">
<span>© Copyright 2019. All Rights Reserved. | This template is made with <i class="fa fa-heart-o" aria-hidden="true"></i> by <a href="https://colorlib.com">Colorlib</a></span>
</div>
</div>
<!-- /copyright -->
</div>
<!-- row -->
</div>
<!-- /container -->
</footer>
<!-- /Footer -->
<!-- preloader -->
<div id='preloader'><div class='preloader'></div></div>
<!-- /preloader -->
<!-- jQuery Plugins -->
<script type="text/javascript" src="js/jquery.min.js"></script>
<script type="text/javascript" src="js/bootstrap.min.js"></script>
<script type="text/javascript" src="js/main.js"></script>
</body>
</html>