5. PM Documentation - Tivix/cpf GitHub Wiki
1. Meetings cadence
Daily:
- Dedicated to sharing information on:
- Working on OR about to work on
- Timeline on track OR off track
- If off track, then a reason so we can learn from it
- Signal discussions that should happen offline OR after the daily
- Impediments to raise
- Any general project updates
- Any relevant topic related to the shared daily update that should be communicated to & acknowledged by the whole team
- Frequency: Tuesday & Thursday
2. Impediments log
Description | Owner | Importance | Due Date | Action to be taken | Status | Comments | Resolved? (Y/N) |
---|---|---|---|---|---|---|---|
As a shortage of backend developers continues, we decided to move to the Supabase solution to replace the initially planned Django backend. This will help minimize the backend developers' role in the project and shift the burden of maintaining Supabase to the frontend developers. This is a new solution for the team, but it's a good playground for future projects. | Marcin Skorek | High | - | Marcin skorek is setting up Supabase | In Progress | - | N |
Team member rotation - The frequent changes of the team members don't allow for the preparation of a detailed roadmap because the team's capacity changes accordingly. | - | Low | - | Short-term planning and decomposing features into smaller tasks can help avoid situations where someone needs to take over a task from someone else in the middle of the development. Deciding on clear code standards and guidelines will make it easier for new team members to onboard and familiarize themselves with the code. | - | - | N |
Marcin Skorek, Mateusz Jasiński | Medium | 05.07.24 | - | - |
3. Project Roadmap
Link to the Spreadsheet with the list of all features: Click
Link to the Miro board with the timeline: Click