Technical Collaboration Standards

From Open Source Ecology
Revision as of 21:02, 28 September 2012 by Marcin (talk | contribs) (→‎Request for Development Assistance)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

OSE Core team has specific standards for engaging in collaboration

Offers for Development Assistance - General Checklist for Evaluation

  1. Resume/qualifications
  2. Video interview - Summary of Interview
  3. Work samples
  4. Work references, personal references
  5. Volunteer or paid work?
  6. Type of engagement sought: Design, Prototyping ,Dedicated Project Visit, Remote Prototyping, Remote Design, on site, consulting, hire, mentor, advisor?
  7. Resources they have available
  8. Resources needed
  9. Time Frame for project delivery
  10. What is the design specification? What is his assessment of our specification?
  11. How are we approaching Test
  12. What is the specific stage of the project that he wants to work?
  13. Can you do a project plan? Milestones and metrics of evaluation.
  14. So that is a proposal, we will take 2 weeks to review it.

For collaboration purposes - have above documentation for project manager on our side:

  1. Do we have a review team for the project?
  2. Do we build capacity?
  3. Do we have the budget?
  4. What else is needed?

Request for Development Assistance

  • At this time, we are working on the priorities shown in Strategic Plan. If the request is consistent with the Strategic Plan, then we can entertain collaboration.

Strategic Technical Partnerships

Advisory Boards