Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Agile
DevOps
William Yeh
Agile Community Taiwan, 2016-05-03
http://school.soft-arch.net/blog/115652/devops-a-lean-perspect...
Q:
Q:
Q: Agile
Q: Dev Ops
Q:
:):(
value
value proposition
feedback
:):(
value
value proposition
feedback


DevOps
in batch!
0
50
100
4 6
0
50
100
4 6
Round
Batch
size
Time first item

reaches customer
WIP Defects Accepted
1
2
3
6 minutes game!
Two Teams…
Team 1
Team
Batch
size
Time first item

reaches customer
WIP Defects Accepted
1 6
No talk!
Fast forward!
No re-work!
Do your best ...
Team 2
Team
Batch
size
Time first item

reaches customer
WIP Defects Accepted
2 1
No talk!
Fast forward! Forward only when next st...
Let’s Go!
6 Minutes
6 Minutes…
Team
Batch
size
Time first item

reaches customer
WIP Defects Accepted
1 6
2 1
Throughput:

(Defects + Accepted) / Time
Lea...
Retrospective
RO
I D
RO I D
RO I D
RO I D
RO I D
Value
Value stream
Flow
Pull
Perfection
1.
:):(
value
:):(
value
Scope
Time
Quality
Cost
:):(
value
Scope
Time
Quality
Cost
Q: Waterfall model
:):(
value
Scope
Time
Quality
Cost
Q: Agile methods
:):(
value
Scope
Time
Quality
Cost
Q: DevOps
DevOps is a set of practices
intended to reduce the time
between committing a
change to a system and the
change being plac...
DevOps is a set of practices
intended to reduce the time
between committing a
change to a system and the
change being plac...
DevOps is a set of practices
intended to reduce the time
between committing a
change to a system and the
change being plac...
DevOps is a set of practices
intended to reduce the time
between committing a
change to a system and the
change being plac...
:):(
value
value proposition
Agile Individuals and interactions
Working software
Customer collaboration
Responding to chan...
Q: Agile
Q:
2.
value stream
:):(
value
value proposition
:):(
value
value proposition
:):(
value
value proposition
•
•
•
current state
current state
future state
:):(
value
value proposition
3.
flow
:):(
value
value proposition
feedback
:):(
value
value proposition
feedback
One Piece
One Piece Flow
https://youtu.be/Bi9R1Hqr8dI
http://school.soft-arch.net/blog/101712/lean-perspective-of-multitasking
:):(
value
value proposition
feedback
:):(
value
value proposition
feedback
:):(
value
value proposition
feedback
Q:
WHY?
WHAT?
HOW?
DevOps “Lean”
DevOps
DevOps 

Developer:
Faster, cheaper, safer
Operator:
API driven platform automation
Responsibilities
Q: Dev Ops
Dev Ops Ops Dev
Q:
One piece flow
5S
https://en.wikipedia.org/wiki/5S_(methodology)
4.
pull
Pull
https://youtu.be/FpwwcpubUIw
:):(
value
5.
:):(
value
value proposition
feedback
“The Three Ways”
Create fast flow of work from Dev into IT Ops.
Shorten and amplify feedback loops.
Create a culture that s...
DevOps
We refer to "DevOps" as
the outcome of applying
Lean principles to the
IT value stream.
Value
Value stream
Flow
Pull
Perfection
Scrum
Kanban
DevOps


Appendix
• The Dot Game (original!)
• http://www.netobjectives.com/resources/articles/the-
dot-game/
• A Leaner Dot Game
• http://l...
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
有了 Agile,為什麼還要有 DevOps?
You’ve finished this document.
Download and read it offline.
Upcoming SlideShare
Docker 導入:障礙與對策
Next

of

有了 Agile,為什麼還要有 DevOps? Slide 1 有了 Agile,為什麼還要有 DevOps? Slide 2 有了 Agile,為什麼還要有 DevOps? Slide 3 有了 Agile,為什麼還要有 DevOps? Slide 4 有了 Agile,為什麼還要有 DevOps? Slide 5 有了 Agile,為什麼還要有 DevOps? Slide 6 有了 Agile,為什麼還要有 DevOps? Slide 7 有了 Agile,為什麼還要有 DevOps? Slide 8 有了 Agile,為什麼還要有 DevOps? Slide 9 有了 Agile,為什麼還要有 DevOps? Slide 10 有了 Agile,為什麼還要有 DevOps? Slide 11 有了 Agile,為什麼還要有 DevOps? Slide 12 有了 Agile,為什麼還要有 DevOps? Slide 13 有了 Agile,為什麼還要有 DevOps? Slide 14 有了 Agile,為什麼還要有 DevOps? Slide 15 有了 Agile,為什麼還要有 DevOps? Slide 16 有了 Agile,為什麼還要有 DevOps? Slide 17 有了 Agile,為什麼還要有 DevOps? Slide 18 有了 Agile,為什麼還要有 DevOps? Slide 19 有了 Agile,為什麼還要有 DevOps? Slide 20 有了 Agile,為什麼還要有 DevOps? Slide 21 有了 Agile,為什麼還要有 DevOps? Slide 22 有了 Agile,為什麼還要有 DevOps? Slide 23 有了 Agile,為什麼還要有 DevOps? Slide 24 有了 Agile,為什麼還要有 DevOps? Slide 25 有了 Agile,為什麼還要有 DevOps? Slide 26 有了 Agile,為什麼還要有 DevOps? Slide 27 有了 Agile,為什麼還要有 DevOps? Slide 28 有了 Agile,為什麼還要有 DevOps? Slide 29 有了 Agile,為什麼還要有 DevOps? Slide 30 有了 Agile,為什麼還要有 DevOps? Slide 31 有了 Agile,為什麼還要有 DevOps? Slide 32 有了 Agile,為什麼還要有 DevOps? Slide 33 有了 Agile,為什麼還要有 DevOps? Slide 34 有了 Agile,為什麼還要有 DevOps? Slide 35 有了 Agile,為什麼還要有 DevOps? Slide 36 有了 Agile,為什麼還要有 DevOps? Slide 37 有了 Agile,為什麼還要有 DevOps? Slide 38 有了 Agile,為什麼還要有 DevOps? Slide 39 有了 Agile,為什麼還要有 DevOps? Slide 40 有了 Agile,為什麼還要有 DevOps? Slide 41 有了 Agile,為什麼還要有 DevOps? Slide 42 有了 Agile,為什麼還要有 DevOps? Slide 43 有了 Agile,為什麼還要有 DevOps? Slide 44 有了 Agile,為什麼還要有 DevOps? Slide 45 有了 Agile,為什麼還要有 DevOps? Slide 46 有了 Agile,為什麼還要有 DevOps? Slide 47 有了 Agile,為什麼還要有 DevOps? Slide 48 有了 Agile,為什麼還要有 DevOps? Slide 49 有了 Agile,為什麼還要有 DevOps? Slide 50 有了 Agile,為什麼還要有 DevOps? Slide 51 有了 Agile,為什麼還要有 DevOps? Slide 52 有了 Agile,為什麼還要有 DevOps? Slide 53 有了 Agile,為什麼還要有 DevOps? Slide 54 有了 Agile,為什麼還要有 DevOps? Slide 55 有了 Agile,為什麼還要有 DevOps? Slide 56 有了 Agile,為什麼還要有 DevOps? Slide 57 有了 Agile,為什麼還要有 DevOps? Slide 58 有了 Agile,為什麼還要有 DevOps? Slide 59 有了 Agile,為什麼還要有 DevOps? Slide 60 有了 Agile,為什麼還要有 DevOps? Slide 61 有了 Agile,為什麼還要有 DevOps? Slide 62 有了 Agile,為什麼還要有 DevOps? Slide 63 有了 Agile,為什麼還要有 DevOps? Slide 64 有了 Agile,為什麼還要有 DevOps? Slide 65 有了 Agile,為什麼還要有 DevOps? Slide 66 有了 Agile,為什麼還要有 DevOps? Slide 67 有了 Agile,為什麼還要有 DevOps? Slide 68 有了 Agile,為什麼還要有 DevOps? Slide 69 有了 Agile,為什麼還要有 DevOps? Slide 70 有了 Agile,為什麼還要有 DevOps? Slide 71

YouTube videos are no longer supported on SlideShare

View original on YouTube

有了 Agile,為什麼還要有 DevOps? Slide 73 有了 Agile,為什麼還要有 DevOps? Slide 74 有了 Agile,為什麼還要有 DevOps? Slide 75 有了 Agile,為什麼還要有 DevOps? Slide 76 有了 Agile,為什麼還要有 DevOps? Slide 77 有了 Agile,為什麼還要有 DevOps? Slide 78 有了 Agile,為什麼還要有 DevOps? Slide 79 有了 Agile,為什麼還要有 DevOps? Slide 80 有了 Agile,為什麼還要有 DevOps? Slide 81 有了 Agile,為什麼還要有 DevOps? Slide 82 有了 Agile,為什麼還要有 DevOps? Slide 83 有了 Agile,為什麼還要有 DevOps? Slide 84 有了 Agile,為什麼還要有 DevOps? Slide 85 有了 Agile,為什麼還要有 DevOps? Slide 86 有了 Agile,為什麼還要有 DevOps? Slide 87 有了 Agile,為什麼還要有 DevOps? Slide 88 有了 Agile,為什麼還要有 DevOps? Slide 89 有了 Agile,為什麼還要有 DevOps? Slide 90 有了 Agile,為什麼還要有 DevOps? Slide 91 有了 Agile,為什麼還要有 DevOps? Slide 92 有了 Agile,為什麼還要有 DevOps? Slide 93 有了 Agile,為什麼還要有 DevOps? Slide 94 有了 Agile,為什麼還要有 DevOps? Slide 95 有了 Agile,為什麼還要有 DevOps? Slide 96 有了 Agile,為什麼還要有 DevOps? Slide 97 有了 Agile,為什麼還要有 DevOps? Slide 98 有了 Agile,為什麼還要有 DevOps? Slide 99 有了 Agile,為什麼還要有 DevOps? Slide 100

YouTube videos are no longer supported on SlideShare

View original on YouTube

有了 Agile,為什麼還要有 DevOps? Slide 102 有了 Agile,為什麼還要有 DevOps? Slide 103 有了 Agile,為什麼還要有 DevOps? Slide 104 有了 Agile,為什麼還要有 DevOps? Slide 105 有了 Agile,為什麼還要有 DevOps? Slide 106 有了 Agile,為什麼還要有 DevOps? Slide 107 有了 Agile,為什麼還要有 DevOps? Slide 108 有了 Agile,為什麼還要有 DevOps? Slide 109 有了 Agile,為什麼還要有 DevOps? Slide 110 有了 Agile,為什麼還要有 DevOps? Slide 111 有了 Agile,為什麼還要有 DevOps? Slide 112 有了 Agile,為什麼還要有 DevOps? Slide 113 有了 Agile,為什麼還要有 DevOps? Slide 114 有了 Agile,為什麼還要有 DevOps? Slide 115 有了 Agile,為什麼還要有 DevOps? Slide 116 有了 Agile,為什麼還要有 DevOps? Slide 117 有了 Agile,為什麼還要有 DevOps? Slide 118
Upcoming SlideShare
Docker 導入:障礙與對策
Next
Download to read offline and view in fullscreen.

Share

有了 Agile,為什麼還要有 DevOps?

Download to read offline

▷ 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 小時,請享用~~~

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

有了 Agile,為什麼還要有 DevOps?

  1. 1. Agile DevOps William Yeh Agile Community Taiwan, 2016-05-03 http://school.soft-arch.net/blog/115652/devops-a-lean-perspective
  2. 2. Q:
  3. 3. Q:
  4. 4. Q: Agile
  5. 5. Q: Dev Ops
  6. 6. Q:
  7. 7. :):( value value proposition feedback
  8. 8. :):( value value proposition feedback
  9. 9.
  10. 10. DevOps
  11. 11. in batch!
  12. 12. 0 50 100 4 6
  13. 13. 0 50 100 4 6 Round Batch size Time first item
 reaches customer WIP Defects Accepted 1 2 3 6 minutes game!
  14. 14. Two Teams…
  15. 15. Team 1
  16. 16. 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!
  17. 17. Team 2
  18. 18. 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!
  19. 19. Let’s Go! 6 Minutes
  20. 20. 6 Minutes…
  21. 21. Team Batch size Time first item
 reaches customer WIP Defects Accepted 1 6 2 1 Throughput:
 (Defects + Accepted) / Time Lead time:
 WIP / Throughput
  22. 22. Retrospective RO I D
  23. 23. RO I D
  24. 24. RO I D
  25. 25. RO I D
  26. 26. RO I D
  27. 27. Value Value stream Flow Pull Perfection
  28. 28. 1.
  29. 29. :):( value
  30. 30. :):( value Scope Time Quality Cost
  31. 31. :):( value Scope Time Quality Cost Q: Waterfall model
  32. 32. :):( value Scope Time Quality Cost Q: Agile methods
  33. 33. :):( value Scope Time Quality Cost Q: DevOps
  34. 34. 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.
  35. 35. 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
  36. 36. 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
  37. 37. 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
  38. 38. :):( 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.
  39. 39. Q: Agile
  40. 40. Q:
  41. 41. 2. value stream
  42. 42. :):( value value proposition
  43. 43. :):( value value proposition
  44. 44. :):( value value proposition • • •
  45. 45. current state
  46. 46. current state
  47. 47. future state
  48. 48. :):( value value proposition
  49. 49. 3. flow
  50. 50. :):( value value proposition feedback
  51. 51. :):( value value proposition feedback
  52. 52. One Piece
  53. 53. One Piece Flow https://youtu.be/Bi9R1Hqr8dI http://school.soft-arch.net/blog/101712/lean-perspective-of-multitasking
  54. 54. :):( value value proposition feedback
  55. 55. :):( value value proposition feedback
  56. 56. :):( value value proposition feedback
  57. 57. Q:
  58. 58. WHY? WHAT? HOW?
  59. 59. DevOps “Lean”
  60. 60. DevOps
  61. 61. DevOps 

  62. 62. Developer: Faster, cheaper, safer Operator: API driven platform automation Responsibilities
  63. 63. Q: Dev Ops
  64. 64. Dev Ops Ops Dev
  65. 65. Q:
  66. 66. One piece flow 5S
  67. 67. https://en.wikipedia.org/wiki/5S_(methodology)
  68. 68. 4. pull
  69. 69. Pull https://youtu.be/FpwwcpubUIw
  70. 70. :):( value
  71. 71. 5.
  72. 72. :):( value value proposition feedback
  73. 73. “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.
  74. 74. DevOps
  75. 75. We refer to "DevOps" as the outcome of applying Lean principles to the IT value stream.
  76. 76. Value Value stream Flow Pull Perfection Scrum Kanban DevOps
  77. 77.
  78. 78. Appendix
  79. 79. • 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/
  • a0919275722

    May. 15, 2019
  • DanielFung22

    Jun. 17, 2018
  • DorisHsu

    Sep. 27, 2017
  • pomelo8121

    Dec. 13, 2016
  • yhku

    Sep. 27, 2016
  • huthief

    Sep. 26, 2016
  • mendickxiao

    Sep. 22, 2016
  • LukeLubansky

    Jul. 21, 2016
  • zulu1853

    Jul. 15, 2016
  • MariaEstherSalazarsa

    Jul. 9, 2016
  • ThanabalanMuniandy

    Jul. 9, 2016
  • metavige

    Jul. 5, 2016
  • MiChunChiu

    Jun. 12, 2016
  • vinniehsu3

    May. 30, 2016
  • cloudolphin

    May. 13, 2016
  • checkincheckin

    May. 12, 2016
  • TzuchinWang

    May. 7, 2016
  • bbhenry

    May. 6, 2016
  • jimyeh

    May. 5, 2016
  • GemElleMix

    May. 5, 2016

▷ 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 小時,請享用~~~

Views

Total views

11,810

On Slideshare

0

From embeds

0

Number of embeds

6,136

Actions

Downloads

179

Shares

0

Comments

0

Likes

54

×