Seven Changes to Improve Your Software Development Flow
Many folks drinking the Lean coolade seem to believe that removing waste is at the heart of the Lean approach. I beg to differ. I’d say that improving flow is the heart of Lean.
Deployments gone bad are a leading cause of spending your evening or weekend hunched over a terminal instead of outdoors having fun. In this talk Jez presents a number of patterns which reduce the risk of releases, including techniques for zero-downtime releases, roll backs, and roll forwards.
Jenny, Pete and Chris would like to share our experience at Sparkle, in particular how we use examples to guide conversations and drive development, and our aspirations (and achievements) towards building a highly maintainable domain-driven living documentation system.
Infrastructure automation with the Windows platform is now a reality. With full Windows support in both Puppet and Chef, and Windows support coming soon for Ansible, technology teams can manage heterogeneous systems of Linux/*NIX and Windows environments using the same tooling, with cross-platform code.
We had a very large system built from a large collection of subsystems. Despite it being quite standard (or maybe because), it was problematic. The CI server did not accurately indicate the state of integration between components. We needed a CI system that didn’t follow the industry standard practices, but would address our problems.
Given that we know that iterative software development can work much better than ‘big bang’ or waterfall, should we apply the same process to organisational change? How about a backlog + iterations for shifting to a team structure which takes Conway’s Law into account, so that the organisation has a better chance of delivering the software systems it needs? We...