You’ve seen how effective open source projects have been at other companies and you want in. Unfortunately, it’s safe to assume that like most other companies, if you took a look at the collaboration between your development units, you’d find significant areas for improvement. At some point, you’d also realize that the flow of information from one end of the company to the next is, say, a bit stagnant. Furthermore, if you took a step back, you’d realize that there are more than just a couple of silos in your organization. These are all symptoms of failing to recognize the competing values of development teams, which results in operational norms that harm the productivity and efficiency of all parties involved.
What does developer culture mean in your organization, and how does it differ from your overall organizational culture? Do you have the “right” developer culture to embrace open source projects, and how you can nurture the developer culture you have today to enable open-source projects and to support the goals of your organization?
Eshanno Byam walks you through what you need to do to successfully leverage open source projects in your company and foster collaborative values and norms in your development organizations; it requires you to invest in nurturing your developer culture. You’ll learn the most important dos and the most tragic don’ts as Eshanno elaborates on what happens when you only look at the tech side of a change rather than taking a more holistic view that allows your colleagues to see the benefits and gain their support, sparking their intrinsic motivation for the change.
This session is sponsored by SAP.
Eshanno has 10+ years experience working in multiple organizations as a strategist and change leader. Now, he works as a strategist for the Global Developer and Community Relations organization and acts an ambassador for nurturing developer/ engineering culture within SAP.
©2019, 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