Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

To begin with, all created issues are staged in a backlog. The product team then decides to allocate issues in "Sprints". Currently, the development methodology is not agile based, so sprints are not used. Instead, sprints will be used to define a time window to accomplish the work needed for a given release.
Developers and other technical users can then move issues to different status as work progresses via a board:
- To do: a developer needs to be assigned or take up this issue
- In development: the developer is currently working on this issue
- In testing: the work related to this issue is completed, and testing can start
- Done: once testing is signed off, this work is considered as done and will be reflected in the next code release

References:

...