When you put all of the step needed to create good software up on the board, there's a lot of them. It's a lot more than just writing code, or even writing requirements and stories. Around Pivotal, we think of this full, end-to-end process as the circle of code: Ideas → prioritization / planning → coding → deployment → runtime → monitoring → feedback, and back again. Richard and Coté discuss these steps and how organizations are starting to appreciate "the big picture."
They also cover some cloud native news: Amazon buying a browser-based IDE, Cloud9; Google expanding their cloud; and Verizon's purchase of Yahoo!
- "Circle of Software," Onsi’s talk where he outlines this concept:
- Ideas → prioritization / planning → coding → deployment → runtime → monitoring → feedback, and back again
- What do Coté and Richard think of this model?
- Lots of individually popular tools at each stage of the circle …
- Prioritization: Jira, Pivotal Tracker, Trello, and more
- Coding → Java/Spring, Node, .NET, Ruby, and more. Plus countless IDEs from IntelliJ to Visual Studio Code to Spring Tool Suite. Not to mention web IDEs.
- Deployment → Jenkins, Concourse, GoCD, TravisCI, and more.
- Platform → Pivotal Cloud Foundry, cloud IaaS, containery stuff
- Monitoring → Datadog, New Relic, Dynatrace, and more. Log storage in Splunk and others.
- Feedback → Tools like UserVoice
- Where does friction arise in the handoffs between those stages?
- Damon Edwards value-stream talk from DevOpsDays Austin 2015.
- Is anyone currently trying to bridge the gaps? Between which stages?
- The marriage of tools and culture in making this work
- If you aren’t committed to continuously delivery and using feedback to fuel the next iteration, don’t waste your time setting up this machinery
- Also: SpringOne Platform! Aug 1st to 4th. Use the code pivotal-cote-300 for $300 off registration.