I’ve had the pleasure of working with many internal development teams in my career in software development. For our company, working in partnership with internal development teams is, in fact, a common project type. Clients call on our particular services for any number of reasons but the most common are to a) increase development traction or b) supplement core internal skills with outside development expertise.
We’ve worked with internal teams comprised of a single developer as well as internal development teams for vast, multinational tech companies with internal departments that dwarf our entire company. (more…)
Most of us have probably used the term collaboration enough to have such a good idea of what it means that we don’t really have to stop to consider its implications. As the Google summary above says, the term derives from the latin word collaboratio (which also derives from the Latin terms for together (col) and and work (laborare)). Despite its similarities to the word cooperate — which also has connections to working (operari) together (co) — collaboration when it comes to software development and programming has a very distinct meaning from cooperation.
How Does Collaboration Differ From Cooperation?
While cooperating is an essential part of working with someone on a project, it does not connote a sense of ownership. This is an important distinction since ownership, the taking of responsibility for a task, is vital to working effectively when developing software. When collaborating with clients, it’s important that developers and programmers be willing to offer their clients the benefits of their expertise, particularly since it’s their expertise that clients needed when they first decided to work with an outside consultant. (more…)