Meetings 🤝

Work Session

A meeting time where developers can work and ask the TPM questions on their tasks. Should occur every week for 1.5-2 hours.

Sprint Planning

Sprint planning (found on Trello) is where tasks from the previous sprint and for the upcoming sprint are reviewed. These should occur once every two weeks, usually when team standup meetings occur.

On Carriage, tasks are self-assigned, so developers can manage their own workload. However, developers should still be taking a number of tasks

Tasks/Tickets

When creating a task/ticket, first decide on the feature or bug you have in mind. Some ways to come up with one:

• Look at the Trello backlog lists
• Look around the website or apps and see if something is broken or unfinished
• Look at the Figmas for missing features
  • Admin/Rider Web: https://www.figma.com/file/RJDRCUZEQaagKkjiiVNxDj/Admin-Web
  • Rider: https://www.figma.com/file/K0YiWfWzr90Q76gwJOWMDs/Carriage-Rider
  • Driver: https://www.figma.com/file/RHCXjAH53ZEkC5eH0Y3Us0/Driver
• Look at the PRD: https://docs.google.com/document/d/1QDSWh7cvl-U2FGXSPl5ZUTAS-oEPXl5JWvFOzPqczTI/edit?usp=sharing

Make sure each feature/bug is broken down into as many sub-tasks as possible. This makes it much easier to monitor progress, test, and review. Be sure to put in as much detail into the ticket description as possible, so developers don’t go down the wrong path.

Story points guide:

• 1: One-line change, or super trivial.
• 2: Somewhat trivial. Maybe a minor fix to existing code, or a small addition.
• 3: Most common, usually a new feature or fixing a bug.
• 5: A large feature or tricky bug.
• 8: Shouldn’t happen, divide into smaller related tasks. If not, then it will be a very complex feature.