Dev ops
Download as PPTX, PDF1 like1,599 views
DevOps aims to integrate development and operations teams to shorten the development cycle. It builds on principles from Agile development which emphasize continuous delivery of working software and frequent feedback loops between teams. DevOps seeks to further reduce feedback times from months or weeks to hours or minutes by breaking down barriers between functions and having teams take full responsibility for software delivery from development to production support.
Dev ops
- 1. DEVOPS Its just Agile done right
- 4. 2001 AGILE!
- 9. 1990 Feedback Loop Features Business Developement Prod Year(s)
- 10. 1990 Feedback Loop Runtime Business Developement Prod Day(s)
- 11. 2000 Feedback Loop Features Business Developement Developement Test Test Prod Month(s) Month(s) Month(s) Year(s)
- 13. 2000 Feedback Loops Runtime Business Developement Developement Test Test Prod Month(s) Month(s) Month(s) ? ? ?
- 14. TestDevelopement 2005 Feedback Loop Features Business Prod TestDevelopement Week(s) Week(s) Month(s)
- 15. TestDevelopement 2005 Feedback Loop Runtime Business Prod TestDevelopement Week(s) Week(s) Month(s)
- 16. Principles behind the Agile Manifesto 1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
- 18. Prod TestDev 2011 Feedback Loops Business TestDev ProdTestDev ProdTestDev TestDev ProdTestDev Hour(s)
- 20. What is a Team? Work Group Team Organisational Unit
- 22. Workgroup
- 23. Team
- 24. Responsible for what? ! ? ! ? !
- 25. Architecture
- 26. Service Oriented Organization Infrastructure as a Service Plattform as a Service Service as a Service
- 27. Lead Time Dependencies Infrastructure as a Service Plattform as a Service Service as a Service Plattform as a Service Infrastructure as a Service Infrastructure as a Service Infrastructure as a Service
- 28. What Roles does a Team need?
- 29. 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
- 30. But what if its a Webapp? • Team Leadership • Requirement Analysis • Requirement Verification • Test Architecture • Test Automation • Frontend Design • Architecture • Frontend Development • Development • Deployment • Logging • Monitoring
- 31. But what if its IaaS Team? • Team Leadership • Requirement Analysis • Requirement Verification • Test Architecture • Test Automation • Architecture • Development • Deployment • Logging • Monitoring • Scripting • Operating System • Networking
- 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. 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
- 37. 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
- 38. DevOps, Taking full Responsiblity
Editor's Notes
- #3: Idea got lost in years of development.
- #4: To fix loss of context during development RUP was invented. Solution strict documentation to sequre the requirements. Test departments to verify that the Dev department did their job
- #5: Teamwork, Collaboration, Leadtime and Feedback
- #6: Remove organizational barriers during dev-test cycle Improved teamwork between dev and test… but then what
- #7: Smart guys meet about Agile Infra
- #8: Smart guys meet about Agile Infra
- #9: Remove organizational barrier between dev/test and prod Improved teamwork between dev and test… but then what
- #10: Idea got lost in years of development.
- #11: Idea got lost in years of development.
- #13: Idea got lost in years of development.
- #18: One team, One application, One backlog
- #21: One team build everything??? Servers, Datacenters, Sites????
- #22: One team build everything??? Servers, Datacenters, Sites????
- #23: One team build everything??? Servers, Datacenters, Sites????
- #24: One team build everything??? Servers, Datacenters, Sites????
- #25: One team build everything??? Servers, Datacenters, Sites????
- #26: Architecture follows the Delivery Model. Conways Law does apply!
- #27: Different teams have different customers but all teams deliver automated services with the same process
- #28: Lead time in dependecies escalate
- #36: Let team members grow in direction of Requirements and Test Architecture. Consider Hiring a GUI designer
- #37: This team wouldnt delivery very well
- #38: We have all the roles but bad coverage, bad utilization of competence and no overlap! Recruitement by Role is random!! We dont want random!
- #39: One team, One application, One backlog