▷ https://william-yeh.net/post/2016/05/devops-a-lean-perspective/ 敏捷運動與 DevOps，有某些共同的淵源，但也有不同的偏重取向。 Agile 陣營的人，常會有個疑問：「聽起來，DevOps 好像只是把 Agile 觸角從 Dev 伸到 Ops 端，只是舊瓶裝新酒？」 Waterfall 陣營的人，也常會有個疑問：「聽起來，DevOps 好像只是 Agile 那一票人搞出來的；我們 Waterfall 陣營是不玩這一套的。」 真的是這樣嗎？ 本次活動會以一些小遊戲、一些小短片，帶領大家從 Lean Thinking 角度，重新審視軟體研發的 value stream。回歸 DevOps 的原點，你將能夠自己給出上述問題的答案。 ▷ 2016-05-03 於 Agile Meetup Taipei 演講實況錄影: https://william-yeh.net/post/2016/05/devops-a-lean-perspective/ 全長整整 2 小時，請享用～～～

1. Agile
DevOps
William Yeh
Agile Community Taiwan, 2016-05-03
http://school.soft-arch.net/blog/115652/devops-a-lean-perspective

2. Q:

3. Q:

4. Q: Agile

5. Q: Dev Ops

6. Q:

7. :):(
value
value proposition
feedback

8. :):(
value
value proposition
feedback

11. DevOps

24. in batch!

25. 0
50
100
4 6

26. 0
50
100
4 6
Round
Batch
size
Time first item
reaches customer
WIP Defects Accepted
1
2
3
6 minutes game!

29. Two Teams…

30. Team 1

31. Team
Batch
size
Time first item
reaches customer
WIP Defects Accepted
1 6
No talk!
Fast forward!
No re-work!
Do your best to maximize productivity!
PM will warn you when 5 minutes has elapsed!

32. Team 2

33. Team
Batch
size
Time first item
reaches customer
WIP Defects Accepted
2 1
No talk!
Fast forward! Forward only when next station is empty.
No re-work!
Do your best to maximize productivity! Quality first.
PM will warn you when 5 minutes has elapsed!

34. Let’s Go!
6 Minutes

35. 6 Minutes…

36. Team
Batch
size
Time first item
reaches customer
WIP Defects Accepted
1 6
2 1
Throughput:
(Defects + Accepted) / Time
Lead time:
WIP / Throughput

37. Retrospective
RO
I D

38. RO I D

39. RO I D

40. RO I D

41. RO I D

42. Value
Value stream
Flow
Pull
Perfection

43. 1.

44. :):(
value

45. :):(
value
Scope
Time
Quality
Cost

46. :):(
value
Scope
Time
Quality
Cost
Q: Waterfall model

47. :):(
value
Scope
Time
Quality
Cost
Q: Agile methods

49. :):(
value
Scope
Time
Quality
Cost
Q: DevOps

50. DevOps is a set of practices
intended to reduce the time
between committing a
change to a system and the
change being placed into
normal production, while
ensuring high quality.

51. DevOps is a set of practices
intended to reduce the time
between committing a
change to a system and the
change being placed into
normal production, while
ensuring high quality.
Scope
Time
Quality
Cost

52. DevOps is a set of practices
intended to reduce the time
between committing a
change to a system and the
change being placed into
normal production, while
ensuring high quality.
Scope
Time
Quality
Cost

53. DevOps is a set of practices
intended to reduce the time
between committing a
change to a system and the
change being placed into
normal production, while
ensuring high quality.
Scope
Time
Quality
Cost

54. :):(
value
value proposition
Agile Individuals and interactions
Working software
Customer collaboration
Responding to change
DevOps a set of practices intended to reduce the time
between committing a change to a system and
the change being placed into normal production,
while ensuring high quality.

55. Q: Agile

56. Q:

57. 2.
value stream

58. :):(
value
value proposition

59. :):(
value
value proposition

60. :):(
value
value proposition
•
•
•

61. current state

62. current state

63. future state

64. :):(
value
value proposition

65. 3.
flow

66. :):(
value
value proposition
feedback

67. :):(
value
value proposition
feedback

69. One Piece

71. One Piece Flow
https://youtu.be/Bi9R1Hqr8dI
http://school.soft-arch.net/blog/101712/lean-perspective-of-multitasking

73. :):(
value
value proposition
feedback

74. :):(
value
value proposition
feedback

75. :):(
value
value proposition
feedback

76. Q:

77. WHY?
WHAT?
HOW?

78. DevOps “Lean”

83. DevOps

84. DevOps

86. Developer:
Faster, cheaper, safer
Operator:
API driven platform automation
Responsibilities

87. Q: Dev Ops

88. Dev Ops Ops Dev

89. Q:

90. One piece flow
5S

91. https://en.wikipedia.org/wiki/5S_(methodology)

92. 4.
pull

100. Pull
https://youtu.be/FpwwcpubUIw

101. :):(
value

102. 5.

103. :):(
value
value proposition
feedback

104. “The Three Ways”
Create fast flow of work from Dev into IT Ops.
Shorten and amplify feedback loops.
Create a culture that simultaneously fosters 2 things:
1. continual experimentation, learning from failure.
2. repetition and practice is the prerequisite to
mastery.
Create fast flow of work
from Dev into IT Ops.
Shorten and amplify
feedback loops.

105. DevOps

106. We refer to "DevOps" as
the outcome of applying
Lean principles to the
IT value stream.

107. Value
Value stream
Flow
Pull
Perfection
Scrum
Kanban
DevOps

110. Appendix

111. • The Dot Game (original!)
• http://www.netobjectives.com/resources/articles/the-
dot-game/
• A Leaner Dot Game
• http://lyndsayp.com/2015/11/08/a-leaner-dot-game/