Scrum Board Instructions
This is a sprint board
This is the board you will be looking at everyday and how we will be tracking who is doing what.
Every team meeting PM and TPM should be review adding and reviewing Tasks
| Project Managers (PMs) | Technical PMs | Student Teams |
|---|---|---|
| • Represents client’s priorities when reviewing the scrum board - guiding team to correctly prioritize tasks based on client goals. | ||
| • Using the scrum board as a guide during each team meeting and referencing it during meetings with PL. | ||
| • Ensures usage/provides accountability to team. This looks like: |
◦ Checking that students are creating tasks/cards
◦ Assigning themselves to cards
◦ Making progress on tasks/moving cards
◦ Making sure all cards have someone assigned
◦ Checking that cards are ordered based on importance/priority
◦ Make sure all cards have relevant information: PRs, links to data, etc.
◦ Is the work being shared/distributed equitably | • Ensure client’s technical needs are correctly represented and prioritized in the cards
• Provide accountability and feedback for students. This looks like: ◦ Reviewing tasks to check that they are the right size for a weekly sprint ◦ Ensuring that the tasks align with the work to be done ◦ Checking that students are making progress with tasks/moving cards, following up to ensure no technical barriers | • Create cards (tasks) ◦ Students may need support/guidance from TPM and PM to ensure tasks are relevant to the project & the right size ◦ Cards should be a ‘bite sized’ amount of work, something that can be done within the weekly sprint ◦ Cards should have all relevant information for task review - links to pull requests, data sets, etc. • Assign themselves to cards ◦ Only one student should be assigned to each card, if there are multiple facets of a task, there should be multiple cards with a student assigned to each. |