How to use the sprint planner

[drcongo]

Hactar have set up a sprint planner board for your project with 6 columns. You can find the sprint planner by clicking on Projects ☝️up there. The columns will always be...

1. Inbox - Every new ticket added to the sprint planner board automatically goes in here. If you're creating new tickets, it's often helpful to add them to the Sprint Planner board so that they end up here for triage.
2. Sprint - When planning a sprint, tickets that will be worked on in the sprint time should be moved here. This could be either by you or by Hactar, but most often through a bit of collaboration and conversation.
3. In Progress - When we start work on a ticket, someone at Hactar will move it to here until it's done.
4. Done - When a ticket is completed but not yet deployed to staging or production, it goes in here.
5. Staged - Anything in staged has been done and deployed to the staging server for testing and sign-off. If you find something in here is not completed, move it back to In Progress with a comment to explain why.
6. Closed - Tickets get automatically moved to here when the associated code gets deployed to production.

Tickets flow from left to right in the sprint planner until they're completed and deployed. The only exception is when a problem is found with a ticket in Staged that means the work is incomplete, in this case the ticket should be moved back to In Progress with a comment to explain why. If everything is done to your satisfaction, you don't need to do anything, just leave the tickets in Staged and give us the nod that it's all good to go live.

The scope of a ticket should never change, so if your testing turns up an additional task that needs doing, this should always go in a new ticket. You can always link tickets together by mentioning the ticket number in the description or comments with hash character, ie: #123