Skip to content

Sprint planning

Siddhesh edited this page Mar 4, 2022 · 13 revisions

Setting up Project board

We create a new project board every sprint - with 4 columns: Backlog (no automation), To Do, In Progress, Done.

Columns

columns

Automation

All columns has an automation in place - except Backlog. merge_from_ofoct

Description

We document the board by naming it properly and with a date of last date of the sprint. sprint_description

Labels

We are using these labels:

  • user-story
  • epic
  • bug, bugfix
  • test
  • frontend
  • backend
  • documentation
  • planning
  • sprint1, sprint2, sprint3, sprint4
  • easy, medium, hard

You can read their descriptions here.

Creating Issues

We are utilizing issue templates to create issues (bugs, user-stories, epics). Sprint board of the current sprint is assigned as the Project.

  • Bug - Description, Steps to reproduce, Expected Behavior, Screenshots, Device information, Additional context, Label=bug. Additional labels like frontend, backend, easy/medium/hard, sprintN are assigned to them.
  • Epic - Description, User stories, Label=epic. No additional labels are assigned. No project is assigned.
  • User story - Description, Acceptance criteria, Label=user-story. Additional labels like frontend, backend, documentation, planning, development, easy/medium/hard, sprintN are assigned to them. Project of specific sprint is assigned.
Clone this wiki locally