InnerSource has become a popular methodology for driving organizational collaboration and innovation. Known as “open source within the organization,” InnerSource encourages organizations large and small to apply the best practices of the open source development process to their internal software engineering projects. Developers and engineering teams can be early adopters for InnerSource development practices, but those transforming traditional, siloed development models into flexible collaborative processes face steep challenges in organizations where leadership is incentivized for shipping features quickly and efficiently.
Alolita Sharma shares a brief case study that succinctly illustrates the top challenges faced by engineering teams as they adopt InnerSource practices. Along the way, Alolita explains how InnerSource can help preserve efficiencies by fast-tracking interteam collaboration, reusing design thinking, and integrating continuous feedback to drive innovation.
Alolita Sharma is a principal technologist enabling open source at Amazon Web Services. Previously, she led engineering teams at PayPal, Twitter, Wikipedia, and IBM. Alolita serves on the board of the Unicode Consortium and has served on the board of the Open Source Initiative (OSI). She is an invited subject-matter expert on W3C and ECMA workgroups. She holds multiple degrees in computer science and speaks internationally on open source, InnerSource, the cloud, web and language technologies, deep learning, and open standards.
©2018, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org