| **GOALS: What are our team goals for this project? What do we individually want to accomplish? |
|---|
| - complete the project to a satisfactory degree - first on the module, quality product for the client |
| EXPECTATIONS: What do we expect of one another in regard to attendance at meetings, participation, frequency of communication, the quality of work, etc.? |
| communicate if you need to miss something meet once a week to talk about what has/needs to happen maintain a standard of work: think about conventional commits, branching code, PR workflows meeting notes somewhere to store them, shared obsidian |
| COLLABORATION: Define what roles each member will have in the team, or how roles or responsibilities will be distributed or shared. How will you organise collaborative coding and writing? |
| figure out strengths of people based on programming languages, frameworks, etc NB. conventional commits, code licensing (condition to sell or open source if attempts fail), do we want shared or independent IP (by parts) |
| POLICIES & PROCEDURES: What rules can we agree on to help us meet our goals and expectations? |
| in terms of code: - what process do we need to merge - what process is required for deployment some amount of tests |
| CONSEQUENCES: How will we address non-performance in regard to these goals, expectations, policies and procedures systematically? |
| assess whether this is a systemic issue first, i.e. whether we are assigning work correctly to people’s strengths, etc, is it something that they enjoy doing or could it be something that should be a shared responsibility and they can take on something else; may need rescoping of project? |