Continuosly Kicking Ass
Download as KEY, PDF0 likes564 views
The document discusses priorities for continuous delivery including individuals and interactions over processes and tools, working software over documentation, and customer collaboration over contract negotiation. It emphasizes building, integrating, and maintaining speed through iterations. While tests and tools are mentioned, responding to change and communication are prioritized. The document concludes by returning to practicing continuous integration and delivery using tools like PaaS platforms and Kanban boards.
Continuosly Kicking Ass
- 1. Continuously Kicking Ass
- 2. Continuous Delivery • Build, build and build more. • Integrating Always • Iterations bah. Maintain Speed! • The Tests Run
- 3. Continuous Delivery • Keep building... • Integration, Delivery, What? • Iterations are still ok... • Unit, Integration, Mess oh’ my...
- 5. Priority • Individuals and interactions over processes and tools
- 6. Priority • Working software over comprehensive documentation
- 7. Priority • Customer collaboration over contract negotiation
- 8. Priority • Responding to change over following a plan
- 10. Priority • Pairing & Communication...
- 11. Priority Now let’s get back to practice & tools...
- 13. Builds
- 14. Builds
- 15. Builds
- 16. Builds
- 17. Builds
- 26. CI & Kanban Live Tools in Action
- 27. PaaS
Editor's Notes
- #2: \n
- #3: \n
- #4: \n
- #5: Before we dive into tooling and actions around CI, let’s talk about what makes CI a necessity and what really makes it a key to success.\n
- #6: Individuals, individual contributors, leaders, organizers, community members, team members, managers and more. Without the individuals there is no reason for process and tools. There is a decisive priority here.\n
- #7: Continuous Delivery makes this dramatically easier than in the past, it provides an almost turn key solution to making sure teams have working software as often as possible.\n
- #8: But again, collaboration and communication are far more important. The single biggest advantage that CD has is it communicates to everyone what state the tools, and in turn the project, are in.\n
- #9: Being able to respond to change requires confidence, knowledge and awareness of where the project is. You must know where the product is, what you’re doing and what is done on the product. CI & D give us this ability to communicate this easily.\n
- #10: ...they are the root of destroying stress and keeping things moving for all involved in a reliable way. Testing provides confidence, pride in ones work, and removes that dreaded “why is it not working on my machine” issue.\n
- #11: ...are fundamental to knowledge sharing and continuous learning. A team needs to maintain learning of everything about themselves and their practices to their tools and implementations. Learn as much as often as well as possible. Never stop.\n
- #12: \n
- #13: I agree with my fellow feline friend here. We can indeed build a better mousetrap.\n
- #14: \n
- #15: \n
- #16: \n
- #17: \n
- #18: \n
- #19: Continuous Integration\n
- #20: \n
- #21: \n
- #22: \n
- #23: \n
- #24: Deployment, don’t screw it up.\n
- #25: Even though there are tools out there that help get us a long way towards easier deployment we often still end up with...\n
- #26: ...a bunch of messy scripts. \n
- #27: Github + Huboard + TeamCity + ??\nGithub + Hubaord + Travis CI + Node.js PaaS Somewhere\n
- #28: Platforms are usually important, not that any of them hold a panacea for all, but they’re what we build everything on top of. Platforms are the keys to our kingdoms, ya know, if developers had a kingdom. It is often said, we’re the kingmakers now but I’ve still not seen a kingdom anywhere that is ours.\n
- #29: \n
- #30: \n
- #31: \n