Don't cross the Rubicon
•
1 like•811 views
As a tech leader at ThoughtWorks, a large part of my job involves recommending practices to our clients so they can build and deliver good quality software faster. In doing so repeatedly for many clients I have created a toolkit that contains practical advice from being on the ground. This is what we do, we know it works. When Julius Caesar entered Rome with his army by crossing the river Rubicon, he did something that couldn’t be undone ever again. In your journey as a leader, avoid mistakes that are difficult to correct later. Here are a set of practices that you want to adopt as soon as possible.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Don't cross the Rubicon
Similar to Don't cross the Rubicon (20)
More from Thoughtworks
More from Thoughtworks (20)
Recently uploaded
Recently uploaded (20)
Don't cross the Rubicon
- 1. Don’t cross the Rubicon Manasi Kulkarni © 2020 ThoughtWorks
- 3. ‘A tech lead is a software engineer, who is responsible for driving the technical direction whilst working closely with the business. They are accountable for technical decisions made on the team’
- 4. In production from day 1 Stop half baked CI/CD The blinker theory Don’t take your business hat off Choose the right lens You own your architecture Quality is everyone’s problem
- 5. In production from day 1 In production from day 1
- 6. Deployment frequency Lead time Change fail percentageTime to restore (MTTR)
- 7. Deployment frequency Lead time
- 8. Accelerate: State of DevOps 2019
- 9. Accelerate: State of DevOps 2019
- 10. Accelerate: State of DevOps 2019
- 11. ‘Successfully’ deploy every commit to production
- 12. In production from day 1 Stop half baked CI/CD The blinker theory Don’t take your business hat off Choose the right lens You own your architecture Quality is everyone’s problem
- 13. Stop half baked CI/CD Stop half baked CI/CD
- 14. Accelerate: State of DevOps 2019
- 15. Anti patterns
- 17. In production from day 1 Stop half baked CI/CD The blinker theory Don’t take your business hat off Choose the right lens You own your architecture Quality is everyone’s problem
- 18. Quality is everyone’s problem Quality is everyone’s problem
- 19. Quality is not just QA’s problem
- 20. Not just quality of code
- 21. Culture of caring about quality
- 22. In production from day 1 Stop half baked CI/CD The blinker theory Don’t take your business hat off Choose the right lens You own your architecture Quality is everyone’s problem
- 23. You own your architecture You own your architecture
- 25. Architecture is not dictated
- 26. An effective Architect looks like a good Tech Lead - Pat Kua
- 27. In production from day 1 Stop half baked CI/CD The blinker theory Don’t take your business hat off Choose the right lens You own your architecture Quality is everyone’s problem
- 28. Choose the right lens Choose the right lens
- 36. In production from day 1 Stop half baked CI/CD The blinker theory Don’t take your business hat off Choose the right lens You own your architecture Quality is everyone’s problem
- 37. The blinker theoryThe blinker theory
- 42. In production from day 1 Stop half baked CI/CD The blinker theory Don’t take your business hat off Choose the right lens You own your architecture Quality is everyone’s problem
- 43. Don’t take your business hat offDon’t take your business hat off
- 44. Product owner Business analystTech lead
- 45. Not all solutions are tech solutions
- 46. Build a culture of ‘why’
- 47. In production from day 1 Stop half baked CI/CD The blinker theory Don’t take your business hat off Choose the right lens You own your architecture Quality is everyone’s problem
- 48. Manasi Kulkarni Thank you © 2020 ThoughtWorks
- 49. Continue the conversation on Slack © 2020 ThoughtWorks XConfEurope2020 xconfeurope2020.slack.com #talk3-do-not-cross-the-rubicon #XConfOnline