How Intuit is overhauling legacy engineering practices at scale with innersource
Download as PPTX, PDF0 likes113 views
Intuit is overhauling their legacy engineering practices by implementing an "innersource" program inspired by open source practices. They established unified guidelines, set teams up for success by appointing trusted committers and defining review SLAs. They are also scaling the effort by establishing technical community leaders and prioritizing foundational capabilities. Getting started involves connecting with leaders, researching standards, identifying model teams, and conducting workshops to teach the new practices. Roles like engineers, product managers, and data analysts are needed, along with tooling like an internal contributions site and rewards program. The benefits include empowered and engaged engineers, decreased wait times, higher quality products, and faster fixes for customers.
How Intuit is overhauling legacy engineering practices at scale with innersource
- 1. How Intuit is overhauling legacy engineering practices at scale with innersource Aliza Carpio and Rocio Montes, Intuit
- 2. about us Aliza Carpio Principal Tech Evangelist @socialac @alizaflips linkedin.com/in/alizacarpio/ Rocio Montes Staff Software Engineer @montes_roxio @roxiomontes linkedin.com/in/montesr ocio #GitHubUniverse
- 3. In a world … communities of practice, almost zero meetings, code stewards
- 5. There are hurdles to get to this nirvana
- 6. Challenges Code is owned by teams and individuals = reliance on a person/team, resulting in long wait times Lack of documentation makes it hard to contribute Varying standards across groups makes it challenging to “onboard” easily The “waiting” impacts work/life balance; at times, heroics to meet deadlines #GitHubUniverse
- 7. Solution: inspired by inner source model Apply open source practices internally
- 8. Solution: inner source program Unified guidelines Declare a single and unified “Inner Source Guidelines” #GitHubUniverse
- 9. ● Suggested GitHub document structure for a repository to be set up for inner source ● Github provides helpful features when these documents exists Unified guidelines ● CI/CD automation Pull Request (PR) builds Unit tests Code coverage ● Local development using containers
- 10. Solution: inner source program Unified guidelines Declare a single and unified “Inner Source Guidelines” Set up teams for success Mutual ownership, appoint decision makers (trusted committers), define SLA for review #GitHubUniverse
- 11. Set up teams for success ● Mindset reorientation adopting internal developers as their first customers ● Created a new role with defined responsibilities, called the Trusted Committer (TC) ● Code Review training, each PR is an opportunity for mentorship ● "On-call" TC rotation ● Defined SLA for reviews #GitHubUniverse
- 12. Solution: inner source program Unified guidelines Declare a single and unified “Inner Source Guidelines” Set up teams for success Mutual ownership, appoint decision makers (trusted committers), define SLA for review Scale effort via influencers Create tech community “site” leaders Prioritize foundational capabilities Services with which most teams integrate and from which changes are usually requested Establish a rewards and recognition program End-to-end recognition system #GitHubUniverse
- 13. Getting started: practical first steps 1 Connect and align with your leaders to get support We connected with site leaders and partner with an engineer leader at each site. 2 Research and unify standards: one playbook We created these guidelines on GitHub to have them close to engineers’ day-to-day tools. 3 Identify teams to be the “models” for inner source We identified foundational capabilities in each business unit. 4 Conduct workshops to teach the “model” teams how to do inner source We have global tours and have one-week workshops with teams at different Intuit sites. #GitHubUniverse
- 14. ● Engineers who can build “with teams” to show them how to work in an open source way ● Product management who understand and communicate that “inner source” enables business goals ● Measuring and analyzing data to determine success of the program We use GitHub Webhooks to gather data for each commit, PR and issue created. Roles Skills Roles and skills you’ll need ● Sharing, story-telling and demoing the impact of the program to leaders and teams across the globe - bring them along ● Tooling and rewards that makes engineers’ lives fun and easier We created the “Intuit First Time Contributions” site. We created a badge to award inner source practices. #GitHubUniverse
- 17. Everyone benefits Software engineer Business ● Empowered to contribute = I can make an impact every day, “pride” ● Decrease “wait times” from other teams who “own” the code ● Develop new skills = investing in my craft ● Speed to delivering high quality products and features to customers ● Higher engagement from technologists = retention Customers ● Use products that are “delightful” and irreplaceable ● When there are customer problems, the fix is quickly delivered #GitHubUniverse
- 18. Resources/inspiration Community “HERD” by Mark Earls Inspired us to tap into our “social” nature to change behavior Inner Source http://innersourcecommons.org/ Overview of inner source principles Model www.madewithcode.com/community/ Inspired us to inject fun in everything we do - acts as a catalyst to open discussions and partnerships … also taught us the importance of sharing with others Change Mgmt “SWITCH: How to change things when change is hard” by Chip Heath & Dan Heath ● Provide clear direction ● Engage people’s emotional side ● Shape the path (path is the situation) #GitHubUniverse
- 19. Thank you! Aliza Carpio, @socialac Rocio Montes, @montes_roxio