Technical Collaboration Standards: Difference between revisions
Jump to navigation
Jump to search
| Line 16: | Line 16: | ||
#How are we approaching Test | #How are we approaching Test | ||
#What is the specific stage of the project that he wants to work? | #What is the specific stage of the project that he wants to work? | ||
#Can you do a project plan? | #Can you do a project plan? Milestones and metrics of evaluation. | ||
#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: | For collaboration purposes - have above documentation for project manager on our side: | ||
| Line 23: | Line 24: | ||
#Do we build capacity? | #Do we build capacity? | ||
#Do we have the budget? | #Do we have the budget? | ||
# | #What else is needed? | ||
=Request for Development Assistance= | =Request for Development Assistance= | ||
Revision as of 20:56, 28 September 2012
OSE Core team has specific standards for engaging in collaboration
Offers for Development Assistance - General Checklist for Evaluation
- Resume/qualifications
- Video interview - Summary of Interview
- Work samples
- Work references, personal references
- Volunteer or paid work?
- Type of engagement sought: Design, Prototyping ,Dedicated Project Visit, Remote Prototyping, Remote Design
- Resources they have available
- Resources needed
- Time Frame for project delivery
- Do we have a design specification? What is his assessment of our specification?
- How are we approaching Test
- What is the specific stage of the project that he wants to work?
- Can you do a project plan? Milestones and metrics of evaluation.
- 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:
- Do we have a review team for the project?
- Do we build capacity?
- Do we have the budget?
- What else is needed?