1 / 6

Successful Collaborations

Discover the key principles of successful collaborations, including setting clear goals, creating clean interfaces, supporting collaborators, and fostering an organic community. Gain insights on how to build strong collaborations that benefit the community and achieve project success.

charlesrichardson
Download Presentation

Successful Collaborations

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Successful Collaborations Everything you needed to know about collaborations you learned in kindergarten. Bob Dalesio

  2. Make Clear Goals • Decide if you are working toward the good of the community or those of your laboratory. (For one project, it costs more to consider others. For the community, it costs less when you can build on previous work) • Identify the requirements (these are things that can be measured – not those that use the words good, fast, real-time, object oriented, application framework, Oracle).

  3. Make Clean Interfaces • Code that is structured with clean interfaces can be extended independently. • A narrow interface that is rarely extended allows code developers on either side of the interface to make changes that do not impact the entire community.

  4. Support Collaborators • To have a collaboration, you need collaborators. • Smart collaborators are better than ones that are not. • Collaborators become smart a lot faster when they are able to get support. • One day, you are going to call your collaborators for support. • This load is only accomplished by people dedicated to making the collaboration work with management that supports this goal.

  5. Collaborations need members • There is no collaboration if there is only one group. • All collaborators using the software contribute in some way, testing, bug fixes, and commentary at the least. • It is important for those joining a collaboration to understand that they are not customers – all problems are their problems.

  6. Collaborations are organic • A collaboration is a group of individuals that decide to work in the environment. • Software develops in many ways in a collaboration. • A community of collaborators is as important as the software.

More Related