DevOps, Agile methods and Continuous Improvement in the Software development lifecycle

Editor's Notes

1. Vou cobrir dois assuntos - métodos Ágeis e DevOps - de uma maneira superficial. A ideia de ter uma visão global do que são, como encaixam e como o conjunto, com tudo o que englobam contribui para atingir o objectivo final - produzir software adaptável, com qualidade, que responda com eficiência as mudanças do ambiente entregue valor ao cliente de uma maneira consistente.
2. Agile Values – Top level philosophy, usually agreed to be embodied in the Agile Manifesto. These are the core values that inform agile. Agile Principles – Generally agreed upon strategic approaches that support these values. The Agile Manifesto cites a dozen of these more specific principles. You don’t have to buy into all of them to be Agile, but if you don’t subscribe to many of them, you’re probably doing something else. Agile Methods – More specific process implementations of the principles. XP, Scrum, your own homebrew process – this is where the philosophy gives way to operational playbooks of “how we intend to do this in real life.” None of them are mandatory, just possible implementations. Agile Practices – highly specific tactical techniques that tend to be used in conjunction with agile implementations. None are required to be agile but many agile implementations have seen value from adopting them. Standups, planning poker, backlogs, CI, all the specific artifacts a developer uses to perform their work. Agile Tools – Specific technical implementations of these practices used by teams to facilitate doing their work according to these methods. JIRA Agile (aka Greenhopper), planningpoker.com, et al.
3. Change Management Project team requirement objectives Business context, etc
4. They help but not ensure. Communication Shared goal / Shared responsibilities Goal understending Continues improvement Sustainable passe
5. Refactoring
6. Continues improvement , feedback loop For exemple : in scrum Sprint retrospective incident management in CD / DevOps
7. Standup Backlog / Backlog grooming Planning Poker CI Agile Practices – highly specific tactical techniques that tend to be used in conjunction with agile implementations. None are required to be agile but many agile implementations have seen value from adopting them. Standups, planning poker, backlogs, CI, all the specific artifacts a developer uses to perform their work.
8. Ticket Management: JIRA CI: Jenkins / Bamboo Backlog management: JIRA Agile Code Quality: SonarQ Depedency Management : Artifactory
9. API integration Tool Chain approach Repeatable system / processes
10. (more general than “software”.)
11. API integration Tool Chain approach Repeatable system / processes
12. API integration Tool Chain approach Repeatable system / processes
13. DevOps Methods – Some of the methods here are the same; you can use Scrum with operations, Kanban with operations, etc. (although usually with more focus on integrating ops with dev, QA, and product in the product teams). There are some more distinct ones, like Visible Ops-style change control and using the Incident Command System for incident reponse. The set of these methodologies are growing; a more thoughtful approach to monitoring is a hot topic right now. DevOps Practices –Specific techniques used as part of implementing the above concepts and processes. Continuous integration and continuous deployment, “Give your developers a pager and put them on call,” using configuration management, metrics and monitoring schemes, a toolchain approach to tooling… Even using virtualization and cloud computing is a common practice used to accelerate change in the modern infrastructure world.
14. Ticket Management: JIRA CI: Jenkins / Bamboo Backlog management: JIRA Agile Code Quality: SonarQ Depedency Management : Artifactory DevOps Tools – Tools you’d use in the commission of these principles. In the DevOps world there’s been an explosion of tools in release (jenkins, travis, teamcity), configuration management (puppet, chef, ansible, cfengine), orchestration (zookeeper, noah, mesos), monitoring, virtualization and containerization (AWS, OpenStack, vagrant, docker) and many more. While, as with Agile, it’s incorrect to say a tool is “a DevOps tool” in the sense that it will magically bring you DevOps, there are certainly specific tools being developed with the express goal of facilitating the above principles, methods, and practices, and a holistic understanding of DevOps should incorporate this layer.
15. DevOps Methods – Some of the methods here are the same; you can use Scrum with operations, Kanban with operations, etc. (although usually with more focus on integrating ops with dev, QA, and product in the product teams). There are some more distinct ones, like Visible Ops-style change control and using the Incident Command System for incident reponse. The set of these methodologies are growing; a more thoughtful approach to monitoring is a hot topic right now. DevOps Practices –Specific techniques used as part of implementing the above concepts and processes. Continuous integration and continuous deployment, “Give your developers a pager and put them on call,” using configuration management, metrics and monitoring schemes, a toolchain approach to tooling… Even using virtualization and cloud computing is a common practice used to accelerate change in the modern infrastructure world.