• Well-defined Project Scope
  • List of User Stories OR
  • Number of Man-days/Man-hours OR
  • Time of team availability AND
  • Requirements List
• Project Obligations for Non-profit
  • Commitment to allocate certain availability
  • Commitment to delivering necessary decisions and materials within some time frame (e.g., number of days)
• Project Obligations for Tech Company
  • Commitment to maintaining team availability
  • In the case of necessity to reallocate the team, Tech Company must present an emergency plan
• Maintenance Conditions
  • Does Tech Company commit to maintaining and developing the product in the future? On what terms?
    • TTTR Recommendation: Low-bono stakes with a fixed price for person-hour
  • If Tech Company does not commit, how do we ensure that Non-profit will handle future development and maintenance?
    • Training for Non-profit Team
    • Implementing Tech Team Member from Non-profit
    • Preparing high-quality documentation
• IP Rights
  • Who owns the copyrights after the project ends?
    • The company owns the product and gives a license to the Non-profit
    • Non-profit acquires IP rights
    • The product will be published on an open-source license
• Communications and presence of the Tech partner
  • How can Tech Partner communicate the project?
    • Case Study
    • Logo on the website
    • Joint content marketing campaign
    • Social Media communication
  • How Non-profit can help in raising awareness about company?
  • How long can both sides communicate about the partnership?
    • 2 years from the end of collaboration
    • Forever
  • How do you want to agree on what’s communicated?
    • Trust: Communicating anything without permission
    • Second-opinion: Asking the second party for permission to describe the collaboration in a certain way
• Implementation methodologies
  • Is there any methodology you want to stick to? (e.g., Scrum)
  • Are there any specific tools you want to use to streamline the development?