Download as PDF, PPTX
More Related Content
![Conversational Development [Agile Portugal]](https://cdn.slidesharecdn.com/ss_thumbnails/agilept-180529111109-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Conversational Development
Conversational Development
- 1. Conversations Job van derVoort - @Jobvo @Jobvo - GitLab
- 2. Things people intech like @Jobvo - GitLab
- 3. working on coolstuff @Jobvo - GitLab
- 4. building great tech @Jobvo- GitLab
- 5.
- 6. working from home @Jobvo- GitLab
- 7. Things people intech don't like @Jobvo - GitLab
- 8.
- 9. more meetings @Jobvo -GitLab
- 10. going back andforth between product and engineering @Jobvo - GitLab
- 11. going back andforth between development and operations @Jobvo - GitLab
- 12. going back andforth @Jobvo - GitLab
- 13. fixing things thatare broken while we're working on cool stuff @Jobvo - GitLab
- 14.
- 15. pleading to getoperations to support my apps @Jobvo - GitLab
- 16. supporting an infrastructurewhile rogue developers try to break it all the time @Jobvo - GitLab
- 17.
- 18. Things we don'tlike to do feel like a waste of time @Jobvo - GitLab
- 19. Things we don'tlike to do are inefficient @Jobvo - GitLab
- 20. By doing lessof the things we don't like to do, we can be more efficient @Jobvo - GitLab
- 21. ..and more happy? @Jobvo- GitLab
- 22.
- 23.
- 24. ?! => meeting|| back and forth @Jobvo - GitLab
- 25. Where does itgo wrong? • Need to sync up on information, but it's scattered over apps, documents, logs • Not all stakeholders are available • Slow iterations, big changes • Communication (meetings) are slow and wasteful @Jobvo - GitLab
- 26. How do wefix this? @Jobvo - GitLab
- 27.
- 28. 170 people, nooffice @Jobvo - GitLab
- 29. A framework forworking better @Jobvo - GitLab
- 30. for everyone @Jobvo -GitLab
- 31. 4 principles ofConvDev 1. Shortened cycle 2. Threaded through all stages 3. Open without consensus 4. Result-oriented @Jobvo - GitLab
- 32.
- 33. 1. Shortened cycle MinimallyViable Change (MVC) @Jobvo - GitLab
- 34. 1. Shortened cycle •Easier to coordinate, reason, estimate • Quicker to respond to market need • Higher predictability • Better code quality • Easier to troubleshoot • More sense of progress @Jobvo - GitLab
- 35. 1. Shortened cycle Includegatekeepers into the conversation @Jobvo - GitLab
- 36. 1. Shortened cycle 1.Deploy frequently: if it hurts, do it more 2. Single changes: easier to link to problems 3. Deploy on peak times 4. Automated integration testing: test everything @Jobvo - GitLab
- 37. 2Thread the conversationthrough all stages @Jobvo - GitLab
- 38. 2. Thread theconversation through all stages @Jobvo - GitLab
- 39. 2. Thread theconversation through all stages @Jobvo - GitLab
- 40. Link everything • Giveeveryone access to the same information • Only way to measure cycle time, therefore focus on results • Optimally: Everything in a single tool (GitLab) @Jobvo - GitLab
- 41.
- 42. 3. Open conversationswithout consensus Embrace asynchronous conversations @Jobvo - GitLab
- 43. 3. Open conversationswithout consensus Prevent "Not Invented Here" syndrome by practicing innersourcing @Jobvo - GitLab
- 44. 3. Open conversationswithout consensus Prevent "Not Invented Here" syndrome by practicing innersourcing @Jobvo - GitLab
- 45. 3. Open conversationswithout consensus • Small changes allow you to make mistakes, consensus takes more time • Increases reuse of solutions, prevents duplicate work • Increases shared knowledge • Work async and remote! @Jobvo - GitLab
- 46.
- 47. 4. Result orientedconversations Connect work to relevant business metrics @Jobvo - GitLab
- 48. 4. Result orientedconversations @Jobvo - GitLab
- 49.
- 50. 1. Shortened cycle 2.Threaded through stages @Jobvo - GitLab
- 51. 3. Open withoutconsensus 4. Result oriented @Jobvo - GitLab
- 52.
- 53.
- 54. Questions? Find me @Jobvo Slidesat jobvandervoort.com/talks about.gitlab.com @Jobvo - GitLab
- 55.