This agreement is a work in progress document which will be extended by consumatech management based on the need
- 1 Characteristics of partnership
- 2 Purpose of agreement
- 3 Terms
- 4 Roles during a project
- 5 Collaboration during project
- 6 Availability during the project
- 7 Reliability
- 8 Connectivity
- 9 Video Calls & Meetings
- 10 Quarterly review meetings
- 11 Complaints and dispute resolution process
- 12 Payment
- 13 Project completion
- 14 Copyright
- Agreement on cooperation to develop software for Consumatech as a company
- We work together based on fairness, collaboration, and mutual respect
- We have the motivation to be successful together and achieve the best possible outcome for our clients
- Set of rules and expectations to maintain a sustainable partnership
- Mutual awareness of what is essential for each party
- Collaboration guideline before, during, and after projects
- Starting date: this agreement is effective immediatly after both parties agreed on it
- Period of notice: at least one month
For each project the following roles need to be staffed and communicated:
- Consumatech tech-lead: scoping, team-sourcing and contact for all technical questions
- Software Developer: engineer which is working on the project
- Each project begins with a dedicated kick-off meeting together with the Consumatech tech-lead, the partner-lead and the dedicated software developer
- We work agile with sprints; during the kick-off meeting, we define working hours, absence time and the length of the sprint
- We communicate via mail and slack
- Each project ends with a feedback meeting (retro)
- Every project owns a project folder with a dedicated task sheet; each tab is dedicated to a month
- On the last day of the month or after a project is finished: update your task sheet with tasks including the points given
- After updating the task sheet, send a notification to your responsible tech-lead
- General availability, (national) holidays, parental leave, planned or likely medical absences and planned or likely vacation days need to be communicated in the project kick-off. That means that the developer and the partner-lead need to jointly prepare a list of all those events before the project kick-off. In the weekly status meetings the developer needs to ensure to communicate any updates regarding these events. Failure to communicate updates about these events can have severe consequences for the relationship to the client. Therefore it is important that this obligation for updates is taken very seriously
- Emergencies like funerals, unplanned child-care, or sickness need to be reported on the same day
- Consumatech project manager schedules a weekly status update (10 minutes) with developer to receive feedback and guarantee availability
- In case no complete answer is possible in time, it should be promptly clarified by setting a new deadline
- Response time should be one hour during working hours or after a (lunch) break
- Over hours need to be reported to the tech-lead
- Working on other projects is only permissible with explicit permission by Consumatech tech-lead
- Clients expect professional and reliable partners. That's why it is very important to be on time at every meeting. If we can't be on time we need to inform the partner before
- Daily achievements and blocker needs to be communicated to the tech-lead via slack
- During your work, you need to have an internet speed minimum of 10 Mbps (downloading & uploading) to guarantee a stable connection during video calls
- The tech-lead needs to be informed if the minimum connectivity standards can not be reached
- Make sure to show a neutral background
- All team members choose silent places with no background noise
- Usage of basic headphones is required
Agreement on quarterly review meetings with an open feedback culture. Structure of the review meeting:
- Recap of last review meeting
- Current team structure
- What is going well and why?
- What is not going well and why?
- What needs to change?
- Approach us if someone is not happy with the situation, with how the project is going or if there is critical feedback
- Conflicts should be solved on eye level and out of court
- If both partners do not find a solution, a mediator will be installed to solve the conflict
- For a base salary, software engineers are expected to complete at least 16 points worth of tasks on Pivotal Tracker (PT) board
- An addition fee will be added for extra points completed in the month.
- The occurrence of the invoice: monthly basis
- Invoice us every month for hours you worked
- Send the invoice and a time sheet to the tech lead & cc Olatoye
- If you are not familiar with invoice generation, us a tool like https://invoice-generator.com/
- Transfer via wise will be initiated within ten working days after receiving the invoice
Please consider the following points before creating the invoice:
- Your full name and address
- Full name and address of the recipient of the service (Consumatech)
- Your VAT identification number (if available) or your Tax ID
- The date of issue
- A consecutive invoice number
- Quantity, description of the delivered products or services. For example: "Login Feature - 2 points."
- The date of delivery or service (this can also be a date range)
- The amount due for the delivered products or services.
- Add the following sentence: "The invoice amount is stated without VAT, as the reverse charge procedure applies in this case."
- Consumatech tech-lead informs software developer and partner manager about the day of project completion and schedules a meeting to finalize the project
- After the project, the copyright will be owned by Consumatech only
- The code and all other data referring to the project need to be deleted
- Both partners agree on the NDA to protect any confidential and proprietary information
- Only use open-source software packages (dependencies) with one of the following licenses mentioned in the OpenSource Licenses Whitelist: https://docs.google.com/document/d/1-G2MEXpVKXKv3H74VPjIYfRshTll176uhYQ5iiwR2Z4/edit