Remove Culture Remove Engineering Culture Remove Software Review Remove Team Building
article thumbnail

InnerSource, a practice that brings open-source principles to internal software development within organizations

Xebia

InnerSource can be defined as the application of open-source software development principles within an organization’s internal software development processes. It draws on the valuable lessons learned from open-source projects and adapts them to the context of how companies create software internally. What is InnerSource?

article thumbnail

Why organizations should commit to innersource in 2020

Github

Even if you’ve never heard the term “innersource” to describe how teams build their software, you’ll probably still recognize some of the principles behind it. They’re powering code at the world’s most influential companies, and they might even be important practices on your team. Innersource isn’t a novel concept.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Forbes names CircleCI to America's Best Startup Employers list

CircleCI

Our team at CircleCI has been hard at work this past year. After all this growth, we were running into challenges around evolving our engineering culture. So we created an engineering competency matrix , which is woven into everything we do. Want to help innovative organizations ship tomorrow’s software today?

article thumbnail

Cross-Functional Teams in Product Development: Definition, Principles and Examples

Altexsoft

However, building and managing effective cross-functional collaboration among employees can be challenging. For this, companies need to carefully design their teams, set clear goals and processes, and cultivate the culture of mutual trust and communication between employees with different expertise.

article thumbnail

On Becoming a VP of Engineering, Part 2: Doing the Job

Honeycomb

Alignment is your most important deliverable Most execs — at least the good ones — spend a lot of time on something that can be completely invisible to their teams: building alignment at the executive level. But what did that look like, in practice?