DevOps - Its just Agile done right
1 like824 views
The document discusses the evolution of DevOps as an implementation of agile principles, emphasizing the importance of continuous delivery, team autonomy, and accountability across the service lifecycle. It outlines the roles and competencies required for effective teams, including leadership, requirement analysis, and various development specialties. The document concludes by highlighting that DevOps is a culture where all teams are responsible for their services, rather than having a separate DevOps team.
DevOps - Its just Agile done right
- 1. DEVOPS Its just Agile done right
- 2. Tomas Riha (tomas.riha@wirelesscar.com) • Domain Architect Delivery Engine VGT/WirelessCar • Great at Delivery, Change, Quality, Efficiency and Fun • Bad at Manual & Repetitive Tasks, Following written instructions • Huge Project Liability
- 3. 1990 The IT Department Business Developement Prod
- 4. 1990 Feedback Loop Features Business Developement Prod Year(s)
- 5. 1990 Feedback Loop Runtime Business Developement Prod Day(s)
- 7. 2000 Feedback Loop Features Business Developement Developement Test Test Prod Month(s) Month(s) Month(s) Year(s)
- 8. 2000 Feedback Loops Runtime Business Developement Developement Test Test Prod Month(s) Month(s) Month(s) ? ? ?
- 9. 2001 The Agile Manifesto AGILE! cooperation embrace change small deliveries often simplicity individuals autonomous team trust
- 11. TestDevelopement 2005 Feedback Loop Features Business Prod TestDevelopement Week(s) Week(s) Month(s)
- 12. TestDevelopement 2005 Feedback Loop Runtime Business Prod TestDevelopement Week(s) Week(s) Month(s)
- 14. 2011 Continuous Delivery Continuous Delivery! Jez & Dave
- 15. Prod TestDev 2011 Continuous Delivery & DevOps Business TestDev ProdTestDev ProdTestDev TestDev ProdTestDev
- 17. Prod TestDev 2011 Feedback Loops Business TestDev ProdTestDev ProdTestDev TestDev ProdTestDev Hour(s)
- 18. Principles behind the Agile Manifesto 1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
- 19. What is a Team? Work Group Team Organisational Unit
- 21. Workgroup
- 22. Team
- 23. Responsible for what? ! ? ! ? !
- 25. Build Test and Operate Login Invite Config
- 26. Login Invite Config Only Depend on APIs
- 27. Test Levels – Component Testing Test Env App API Config Mock
- 28. Test Env Test Levels – Contract Testing App API Config Mock Test Env App API
- 29. Test Levels – Simulation & Monitoring QA & PROD Environments App API Test Envenvironment App API Config Mock Test Envenvironment App API App API App API
- 30. What Roles does a Team need?
- 31. What capabilites does a Team need? • Team Leadership • Requirement Analysis • Requirement Verification • Test Architecture • Test Automation • Architecture • API Design • Development • Database Design • Database Implementation • Deployment • Logging • Monitoring
- 32. Riha-Floren Team Competence Chart Team Leadership Requirement Analysis Requirement Verification Test Automation Test Architecture Architecture Frontend design Frontend development Backend development Database Design Database Development Database Admin Logging Monitoring Operative System Networking
- 33. Riha-Floren Team Competence Chart Team Leadership Requirement Analysis Requirement Verification Test Automation Test Architecture Architecture Frontend design Frontend development Backend development Database Design Database Development Database Admin Logging Monitoring Operative System Networking
- 34. Riha-Floren Team Competence Chart Team Leadership Requirement Analysis Requirement Verification Test Automation Test Architecture Architecture Frontend design Frontend development Backend development Database Design Database Development Database Admin Logging Monitoring Operative System Networking
- 35. Riha-Floren Team Competence Chart Team Leadership Requirement Analysis Requirement Verification Test Automation Test Architecture Architecture Frontend design Frontend development Backend development Database Design Database Development Database Admin Logging Monitoring Operative System Networking
- 36. What Roles does a Team need? Team Leadership Requirement Analysis Requirement Verification Test Automation Test Architecture Architecture Frontend design Frontend development Backend development Database Design Database Development Database Admin Logging Monitoring Operative System Networking BA Architect Tester Developer DBA Operations Specialist
- 37. The Team and the Individuals Engineer in Test - Test Spec, Glue Code, DSL, Bug fixes, Backend Code Engineer in Architecture – Architecture, Prototype, Backend Code, Bug Fixes , Test Spec Engineer in Backend - Backend Code, Bug Fixes, Glue Code, DSL, Test Spec Engineer in GUI Test - Test Spec, Glue Code, DSL, Bug fixes, GUI Code Engineer in Frontend - GUI Code, Bug Fixes, Glue Code, DSL, Test Spec Engineer in Infrastructure - Infrastructure Code, Bug Fixes, Glue Code, DSL, Test Spec
- 38. Definition of Done In production delivering value and meeting SLA.
- 39. Definition of Done Or is it actually…. When service is decommissioned.
- 40. The DevOps miss concepts You don’t have “a DevOps team” that supports the other teams. You don’t hire “a DevOp” to put in your development teams. You don’t hire a Dev to put in your operations teams.
- 41. DevOps DevOps is a Culture All teams are DevOps teams All teams have full responsibility of a service lifecycle All teams are autonomous Organization must support DevOps • Create an Organization that matches Delivery Model and Architecture
- 42. Now Im Done! Catch me at the coffee machine or • Blog http://continuous-delivery-and-more.blogspot.se • Twitter @TomasRihaSE • Mail triha74@gmail.com