As a stakeholder I want to have a better understanding of the main product goals. As a PO I need to have a better overview of the goals and associated tasks. As a team member I need a tool that helps me in my work.
Acceptance criteria
Product goals are visible on the GitHub board.
Product goals can be consolidated among platforms.
The board is easy to understand and use.
Tasks
[x] Discuss desired behavior with the team.
[x] Use milestones to deal with product goals and attach related issues.
[x] Issues might not be attached to a milestone for other unrelated work.
[x] The Epic field is removed.
[x] The Epics tab is removed.
[x] Update board setup documentation accordingly. Maybe move this documentation to the documentation repository.
The Product Backlog tab now only shows issues with the Draft or Backlog status. Issues are grouped according to this status.
Milestones serve as replacement for epics, which have been removed. We introduced a Current Milestone tab to display the current milestone (i.e. the main current focus).
We renamed Test as Testing to avoid confusion with a board which would have been created for a quick test.
We also agreed to discuss next how we could better integrate testing or code review in our boards.
As a stakeholder I want to have a better understanding of the main product goals. As a PO I need to have a better overview of the goals and associated tasks. As a team member I need a tool that helps me in my work.
Acceptance criteria
Tasks