We are all one team. We all discuss and make decisions that impact us all as a team.
- Office hours are 9AM-4PM Seattle TimeZone (6PM-1AM CET TimeZone) Monday-Friday
- No meetings scheduled outside of agreed working hours
- No expectations to reply to messages or review PRs outside office hours
- No expectations to work late in the night or over the weekend
- Be respectful of timezones and team members' working schedule
- The sprint starts on Thursdays and Ends on Wednesdays with Demos, Retrospective and Sprint Planning
- All meetings should have an agenda and a clearly communicated objective
- All meetings should be planned at least a few days in advance
- Sprint planning, Sprint demo, Retrospectives and Daily Standup should always happen at the same time every week
- All meetings should have a time keeper to ensure the meeting doesn't overrun
- If you cannot attend one of the meetings, try to let the team know at least 15 minutes in advance
- Starts on time and it should not take longer than the pre-agreed time
- Format: What did I do yesterday? What will I do today? Any blockers?
- Any in-depth discussion should be taken offline
- Everyone should try to attend standups daily, but if not possible send an offline message on Teams with your status update
- Retrospectives are set to Wednesdays
- Everyone should give 4 votes to the available retro groups before the Retro
- Discussion about each entry is time boxed - 3 to 4 minutes
- Demos are done on Wednesdays as part of the end of the sprint
- Demos should be announced to the scrum master the day before the demo
- Demos are strictly time boxed and should focus on informing the team or demoing acceptance criteria for User Stories
- Sprint Planning involves the whole team, with Product Owners as mandatory
- Before Sprint Planning, everyone should add their capacity to the sprint.
- The User Stories that were not finished in the previous sprint are moved to the next sprint or backlog as appropriate. Remaining time for the tasks is estimated and any new tasks needed are added and estimated.
- The top prioritized new User Stories are defined with Acceptance Criteria
- Each of the potential User Stories are split into an initial set of tasks and the tasks are estimated. (some prep may be done before to speed things up)
- User Stories are added to the next sprint until capacity is met.
- Split each dev task in the story into 3 (Research, Implementation, Review). This doesn't apply if you felt the task is too short.
- Main goals: 1. something working and 2. ability of recreating it independently (documentation on this project is highly important).
- Tasks should have a time estimate from the following options: 1h, 2h, 5h, 8h or 13h
- If multiple team members are pair programming on a taks, create as many tasks on the board as there are team members and mark them as copies of each other
- Tasks should not have estimates bigger than 13h (or 2 working days) -> if this is the case, try to split it into two separate tasks
- Estimate 6 coding hours/day per team member
- Items in "New" should not be assigned to anyone -> a new task should be picked up and set to "Active" by a team member when they finished their last active task and they estimate they have time to work on it
- If you are no longer working on a task, move it back to unassigned
- Anything you work on related to the project should be captured in a task
- If you are not available to work on tasks related to the project, this should be reflected in the availability for the sprint
- Create a PR for each completed task if appropriate
- Update README along the way
- Pair programing, so when someone is not available, the team is not blocked, it doesn't have to be 1 MS and 1 D3, it could be 2 MS or 2 D3 as well.