Team guidelines proposal

team-guidelines.md

• I propose that we use the following Definition of Done:
  • Code was written according to the standards that we have within
  • Code review has been done
  • Acceptance criteria met
  • Automated tests have been written if applicable
  • Ticket has been tested by QA or another team member and test evidence has been added to the ticket
  • Product owner accepts the user story
• I propose that we use the following Definition of Ready:
  • Ticket has been discussed during a refinement (plan of attack)
  • Ticket has been estimated (user story)
  • Acceptance criteria are clear
  • Team is able to demo the user story
  • Dependencies are identified
  • Horror scenarios are identified if applicable
• I propose that we work in a hybrid way:
  • The days that we work remote are 'focus time' (preferably days without meetings)
  • We want to increase the collaboration within the team
  • We want to improve the relationship with coworkers
  • Feel more connected to the organization's culture and values
  • Easier to understand expectations and priorities
  • We define a time slot when everybody is available (working hours)
  • We let the team know if we are unable to work due to external factors
  • Define the day(s) that we come to the office => poll through slack or teams
  • Pair programming as an activity on office days
  • We could define a line about what's an acceptable reason not to come to the office
• I propose that we improve handovers from developers to QA:
  • By adding a comment to the ticket when development is done and deployed to test environment with test evidence
  • Meeting if it's a big ticket => 8 or 13 storypoints
  • The evidence format => screenshot or link
  • Ticket assigning not in scope
  • Only provide evidence for the scenario's mentioned in the ticket
• I propose that we define our internal communication strategy:
  • When do we use async communication (messages, e-mails) over sync (calls, meetings)
  • Prefer to use our team chat with threads over individual interactions (improves knowledge sharing)
• I propose that we prepare scheduled meetings
  • Show up on time => if you can't then communicate
  • Have an agenda
  • Provide time to prepare => has to be during working hours