Hello everyone, i have a specific problem about states and categories, here is a full description of my implementation for better view of the problem, lists of question will be in the bottom of the page.
Description:
In my project, i have 1 scrum, and 6 Kanban boards:
1* Sprint (Scrum)
2* User Story (Kanban)
3* Design (Kanban)
4* Development (Kanban)
5* Bug (Kanban)
6* Epic (Kanban)
The workflow schema turn around the movement of a story into the different boards. So I will describe the next workflows from the 2* board for better understanding.
2* User Story (Kanban)
Filter: show only Stories issues
Backlog: Creating any story .
Statut associated: « Backlog », no column in board
Board Columns: Business Analysis -> Ready For Design -> Design Doing -> Tech Validation To Do -> In Dev -> In Test -> Code Review -> Done
Board Statut: Business Analysis -> Ready For Design -> Design Doing -> Tech Validation -> « Backlog sprint/Sprint* »-> To Do -> In Dev -> In Test -> Code Review -> Done
Backlog sprint/Sprint*: when an issue goes from « tech validation » to « Backlog Sprint » status, the issue disappear from the board and goes to the backlog of the 1* Sprint (Scrum). When the issue will pass from « backlog sprint» to a real sprint, the issue will go to the « To Do » column on boards 1*, 2*, 4*.
1* Sprint (Scrum)
Filter: show only Bug AND Stories
Backlog: Stories pushed in when transited from "Tech Validation" status to « Backlog Sprint » status available in 2*, 3*, 4* Boards
When i push a Stories or Bug from the Sprint Backlog to a real sprint:
°Boards 1*, 2*and 4* : Issues available in the "To Do" column
Board columns: To Do In Dev In Test Code Review Done
Board status: To Do -> In Dev -> In Test -> Code Review -> Done
3* Design (Kanban)
Backlog: show stories transitioned from « Business Analysis » to « Ready for design »
Status associated: « Ready For Design »
Board Column: To Do -> Doing -> Tech Validation -> Done
Board Status : To Do -> Doing -> Tech Validation -> Backlog Sprint
4* Development (Kanban)
Filter: see only stories and bug
Swimlane : 2 (Stories and Bug separated)
Backlog: No Backlog
Board Column: Tech Validation-> To Do-> In Dev-> In Test-> Code Review-> Done
Board Status: Tech validation -> Backlog Sprint/Sprint* ->To Do -> In Dev -> In Test -> Code Review -> Done
Backlog sprint/Sprint*: when an issue goes from « tech validation » to « Backlog Sprint » status, the issue disappear from the board and goes to the backlog of the 1* Sprint (Scrum). When the issue will pass from « backlog sprint» to a real sprint, the issue will go to the « To Do » column on boards 1*, 2*, 4*.
5* Bug (Kanban)
Filter: only bug
Backlog: All issue Bug created
Statut associated: Backlog
Board Column: Tech Validation-> To Do-> In Dev-> In Test-> Code Review-> Done
Board Status: Tech Validation -> Backlog Sprint/Sprint*-> To Do -> In Dev -> In Test -> Code Review -> Done
6* Epic (Kanban)
Filter: only epic
Backlog: No Backlog, when created, the epic goes to « to do » column automatically.
Board Column: To Do-> Running -> Doing-> Done
Automation:
-> When an epic is created in « To Do », if one features associated to this epic is done or is in a sprint, the epic goes in « Running »
-> When all the issues associated to an epic are done, the epics transit to « Done » column.
QUESTIONS :
Hi @Alan Chêne ,
That is what you call an elaborate story! I will focus on your questions:
Good luck
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.