Jira
Lab651 uses Jira, exclusively, for all project process tracking for both Scrum and Kaban. Every engineer will look to this board for task priorities and assignments.
Board Design
Section titled “Board Design”By default, the boards do not have all of the steps that we use at Lab651. There should be 5 standard columns in both the Kanban and the Scrum boards that you will work from:
- ToDo - A ticket that has not started or is not currently being worked (even if it has started)
- InProgress - A ticket that is in active development. If a ticket is not being worked on (for any reason), place the ticket back in ToDo. It is important that the board always reflects the current state of the project.
- QA - The tickets is assigned to Quality Assurance to be worked
- Acceptance - The ticket has been QA’d and it is currently waiting for the client or Product Owner for review and acceptance. If there is a problem, either a bug ticket will be created or a ticket will be kicked back for work.
- Done - The ticket is done and considered complete. Note that this should always be the last column in order for Jira to consider this the completed phase
There are optional columns that can be beneficial to help understand the state of the project. These will up to the Project Manager and the team to decide.
- Blocked - In a project, when tickets are often blocked, it may be beneficial for this column to be used so that the state can be exposed to the client and the team (and become a discussion point).
- CodeReview - In a project where there will be a large number of code reviews, adding this column may help in clearly identifying the state of the project and timelines.
Related
Section titled “Related”- Tickets — Stories, Tasks, Epics, and QA conventions
- Jira Set-Up — per-project board creation