Cloud will not fix your broken culture
Cloud will not fix your broken culture. Microservices won’t prevent your two-pizza teams from needing to have conversations with one another over that pizza. As Conway’s Law suggests, though, the quality of your software is a direct reflection on the quality of the culture creating it (just as the structure of your software reflects your organizational structure), making thoughtful decisions about tools and architecture can help. We succeed when we share responsibility and have agency, when we move past learned helplessness to active listening. "Anyone who says differently is selling something”.
Incremental improvement is better than sequential waterfall delivery. Cloud is not a “silver bullet”, there is no flowchart, no checklist, no shopping list of ticky boxes that will make everything better. Tools are essential, but how we implement the tools and grow the culture and practices in our organizations needs even more attention. Whether you’re just starting to implement technical and organizational change, or facing the prospect that you already have legacy microservices, it’s worth considering the why and the how of our behaviors, not just the what.
Outline/structure of the Session
Seeing non-tech companies large and small being forced to become software companies is a recent trend. After years of outsourcing and neglecting this part of IT in favor of wringing out costs in virtualization and SaaS, most companies find themselves terrible deficient in their software development capabilities. This talk will cover the history that's brought us to this point - how companies are now in a position where they need to become masters of their own custom software development - and then give guidelines for safely and reliably making the switchover to taking on a Agile mind-set. I'll cover associated concepts like what cloud actually is and can do for you and the major way that "management" needs to change.
Agile therapy, let’s talk about practical, actionable steps that will help. How do we evaluate our progress? How do we know when to course-correct? How do we react when it seems like there’s always something new we should have done last month? this talk will explain in the nerdiest of terms how to become Cloud Native, and what we can do to avoid sadness as a service.
Developers, IT, Architects, Project Managers, Coaches, VPs and Directors
schedule Submitted 1 year ago
People who liked this proposal, also liked:
The Future of Test AutomationGojko Adzic
schedule 1 year agoSold Out!
Processing is getting cheaper, software is getting more distributed and clouds are taking over. These trends will have a significant impact on what we can do with test automation and what will make sense to automate in the future. Prohibitively expensive testing strategies are becoming relatively cheap, and things that we didn’t even consider automating will become quite easy. At the same time, strategies that served us well for on-premise reliable hardware simply won't work for the distributed, fragmented, virtualised platforms.
Gojko presents emerging trends in the testing tools space and predicts how you'll be using tools differently ten years from now. If your organisation is suffering from the high cost of testing, come and learn about tools and trends that may help you outrun the competition.