Resetting Your Culture for Cloud-Native Success
0 likes•54 views
This document discusses the cultural and operational shifts necessary for successful cloud-native software development, emphasizing the importance of agile methodologies and DevOps in fostering collaboration and speed. It highlights the need for organizations to rethink traditional development practices, priorities, and tools to adapt to the cloud environment. Additionally, it stresses the significance of core values like collaboration, diversity, and transparency for achieving effective cloud-native operations.
Resetting Your Culture for Cloud-Native Success
- 1. 1 Resetting your Culture for Cloud-Native Success
- 2. 2 MarketingEntertainmentTransportation Ten+ years of life disruption
- 3. 3 CloudCollaborationIteration Ten+ years of innovation in the ways we work
- 4. 4 Work culture has been disrupted more than many realize
- 5. 5 What did your culture look like 5 or 10 years ago? How different is it now? ● Traditional ways of working are causing stock ticker churn ● Agile taught us “people and teams, not resources” ● Open cultures (not open offices) are attracting younger workers ● Today’s most effective culture “hacks” are... IMMEDIATE EMOTIONAL LOW EFFORT VISIBLE
- 6. 7 The shift to Cloud Native is fundamentally altering how we approach software development
- 7. 8 What makes you say that? For the first time in 20 years of software development, ● I no longer care where my app lives ● I focus differently on architecture and I may not care about scale ● I no longer fixate on availability and resiliency ● I no longer have the same dependencies and limitations
- 8. 9 A seismic shift or just another development fad? ● Agile and DevOps set the stage for the cloud ● Legacy tools struggle in cloud environments ● Legacy processes don’t promote cloud development ● Data centers are no longer top of mind
- 9. 10 Agile and DevOps set the stage
- 10. 11 Agile led the way ● Agile brings us new ways of working iteratively ● Agile encourages speed and efficient process ● Agile promotes smaller deliverables ● Agile encourages team focus But many Agile Coaches will tell you Agile is still just a
- 11. 12 DevOps took the next steps ● DevOps encourages team ownership ● DevOps fosters cross-team collaboration ● DevOps drives delivery ● DevOps thrives on automation But the typical enterprise still has massive silos between the business, development, security and operations
- 12. 13 What does that lead us to today? ● Shifting definitions of potentially shippable increments (value) ● Code ownership to a new level ● Collaboration and transparency at lower levels ● Automation as a mandate ● Standardize before you automate MVC > MVF > MVP (90 day or less app development is a new thing) DevSecGitRelMonBusOps? We don’t just plan together, we stay closer to the code together The cloud enables speed - speed requires automation Don’t automate the wrong things
- 13. 14 Minimum Viable Change (MVC) What you initially thought the solution was What the initial optimal solution was Optimal solution moved to Cycle time compression may be the most underestimated force in determining winners & losers in tech. — Marc Andreessen
- 14. 15 So, the first step is “Lift and Shift” to the cloud, right?
- 15. 16 Conway’s Law Conway’s law essentially says: Your system architecture will mimic the communication scheme within your organization. My Question: What happens if you take your existing applications and just dump them to the cloud? How’s your technical debt level?
- 16. 17 It’s time to think fundamentally different about software development
- 17. 18 You might not be cloud native if... ● You want to deploy serverless with tools from the 90’s ● You think containers are for leftovers ● “Docker” and “Kubernetes” remind you to fix your boat ● Someone says “AWS” and you check your Prime delivery status ● Your deployments are delayed 90 days due to server purchase approvals Jeff Foxworthy
- 18. 19 Change your Focus ● Focus less on releases, more on deploys ● Focus less on MVF and more on MVC ● Focus less on big up front architecture - parallelize small functions and create more value ● Focus less on what’s worked until now ● Focus on cloud education
- 19. 20 Think like a bank ● You must deploy securely. It’s not an option. Test every single commit. ● Performance monitoring matters ● Take advantage of auto-scaling technology ● Utilize automated backups
- 20. 21 Stop thinking locally, start thinking about global zones ● Target self-healing, not quick server access (Kubernetes and Containers really help) ● Perform in a global theater (never think local) ● Offload scalability/resiliency via stateless protocols (treat each request independently and centralize sessions to an independent database) ● Use tokens for scaled web session data mgmt (session stores require perfect sync across users)
- 21. 22 Think about the cloud service, not the tool ● Leveraged properly, you move to MVC from MVF/ MVP ● Leveraged properly, you save money ● Leveraged properly, uptime exceeds 99.99% ● Leveraged properly, deploys shrink in significance ● Leveraged properly, you don’t design for scaling ● Leveraged properly, backups are automated ● Leveraged properly, team autonomy is a natural byproduct of cloud adoption
- 22. 23 The cultural impact ● Loosely coupled, architecturally abstracted applications change how teams work ○ We don’t care where the application components live, we only care that they can communicate efficiently ● Cultural clashes await if we hire the same way we always have. We will no longer produce the same results. ○ Waterfall mindsets vs Agile vs Cloud Native ○ CI vs automated vs manual testing ○ Cloud development vs DevOps vs traditional methods ○ Architecture vs Feature focus
- 23. 24 GitLab defined these core values Collaboration Results Efficiency Diversity Iteration Transparency
- 24. 25 About GitLab Core Values Collaboration ○ Work asynchronously with a fully remote workforce using GitLab to build GitLab Results ○ Track outcomes, not hours Diversity ○ Hire those who add to culture, not those who fit with culture - we want cultural diversity not conformity Efficiency ○ Boring solutions win, complexity slows cycle time Iteration ○ Minimum Viable Change (MVC) if the change is better than the existing solution, ship it Transparency ○ Everything at GitLab is public by default: Strategy, Roadmap, Quarterly Goals, Handbook, and Issue Trackers
- 25. 26 3 critical cultural pillars for cloud native Collaboration ● Everyone needs to collaborate regularly in one place ● Collaboration has to happen closer to the code Diversity ● Diversity in this case is a variety of backgrounds and approaches on a single team, enabling us to work in new ways Transparency ● Increased developer ownership + faster commits = more required visibility to what’s planned and what’s done ● Die siloes, die
- 26. 27 Lastly, two things that can crush your culture Legacy Mindset ● decentralized vs centralized ● distributed vs hub ● autonomy vs mandate ● microservices vs decoupled vs monolith ● service mesh communication vs archaeic architecture ● serverless vs SOA ● security vs headline Legacy Tooling ● More nodes, more tools, more bailing wire. ● Old tools are barriers to new hires ● “Adapted for” is not “Built for”
- 27. 28 26X faster release cycles SVN was one blocker to adopting DevOps. Axway implemented GitLab and went from yearly to biweekly deployments. Public Case Study