Intro to DevOps

Copyright ©2017. All Rights Reserved

DevOps

https://scr.sad.supinfo.com/articles/resources/212924/3652/0.png

Ops Team

Scrum Team: Focus on Delivery and Speed

Source – Dana Pylayeva, http://www.bookmetrix.com/detail/book/5c5e07b6-7993-4cb8-9712-79295d14a87e#downloads

Max 30 days

Releasable

On-call supportMonitoringUpgrades

Security PatchingBackups

Ops Team: Focus on Stability and Reliability

Source – Dana Pylayeva, http://www.bookmetrix.com/detail/book/5c5e07b6-7993-4cb8-9712-79295d14a87e#downloads


And the frustration continued…1. Chaos at production because of frequent deliveries

2. Lot of manual work resulting in deployment issues and downtime

3. Still works in silos, no end-to-end ownership

4. Lead time between development completion to customer delivery


DevOps is NOT


Its Not No Ops

https://devops.com/wp-content/uploads/2015/11/NoOps.jpg


Its Not Just Tools

http://www.ecmag.com/sites/default/files/xml_uploads/unzipped/_KleinTools.ElectriciansHandTools_0.jpg


Its Not a Job Title

https://dlutzy.files.wordpress.com/2011/06/devopsorgchart2.gif


Its Not Just Dev and Ops

http://sdtimes.com/wp-content/uploads/2015/08/SEP15-0817-OPINION-GUESTVIEW-SETHU.png


DevOps is1. Continuous Development, Integration and Testing

2. Continuous Delivery and Deployment

3. Continuous Operations and Monitoring

https://media.licdn.com/mpr/mpr/AAEAAQAAAAAAAAfGAAAAJGMzOTkzNjMxLWQ1ZDYtNDVkZS1iMzVkLTUxNTFlZDEyMDdlYw.jpg


References

https://images-na.ssl-images-amazon.com/images/I/51E8AO50Y7L._AC_UL320_SR212,320_.jpg

https://images-na.ssl-images-amazon.com/images/I/51GspNFDWIL._SY344_BO1,204,203,200_.jpg


Three Ways Approach1. System Thinking

2. Amplify the feedback loop

3. Continuous experimentation and learning

http://images.techhive.com/images/article/2016/07/gears-1443762_1280-100669732-primary.idge.jpg


1st Way – System Thinking

http://itrevolution.com/wp-content/uploads/2012/08/first-way2.png

Understand and increase the flow of work, from left to right


1st Way – System Thinking1. Make work visible – Kanban or Sprint board

2. Limit WIP – context switching and multitasking

3. Reduce the batch size – annual vs monthly release schedule

4. Reduce the number of handoffs – horizontal and vertical both

5. Continually identify and elevate our constraints1. Environment creation2. Code deployment3. Test setup and run

6. Eliminate Waste in the value stream1. Partially Not Done work2. Extra processes3. Extra features4. Manual work


2nd Way – Amplify the feedback loops

Create short feedback loop that enables continuous improvement, right to left


2nd Way – Amplify the feedback loops1. See problems as they occur – GM car manufacturing

2. Swarm and solve problems to build new knowledge – Andon cord

3. Keep pushing quality closer to the source – testing, approvals, deployments etc.

4. Enable optimizing for downstream work centres – internal customers


3rd Way – Continuous Experimentation and Learning


3rd Way – Continuous Experimentation and Learning

1. Enabling organizational learning and a safety culture

2. Institutionalize the improvement of daily work – Technical debt, Alcoa case study

3. Transform local discoveries into global improvements – reinventing the wheel

4. Inject resilience patterns into our daily work - RBS


Video


Thanks

Intro to DevOps

Software

Transcript of Intro to DevOps