Refine a ticket #6
Labels
🏕 Priority Mandatory
This work is expected
📅 Sprint 1
Assigned during Sprint 1 of this module
📅 Sprint 2
Assigned during Sprint 2 of this module
📅 Sprint 3
Assigned during Sprint 3 of this module
📅 Sprint 4
Assigned during Sprint 4 of this module
🎯 Topic Communication
Reading, writing, speaking, and listening in English; expressing our ideas
🎯 Topic Delivery
Shipping our work, deploying our code, delivering our product
🎯 Topic Iteration
Prototyping, testing, analysing, and refining in a cycle of development
🎯 Topic Problem-Solving
Breaking down problems and building up solutions
🎯 Topic Requirements
Interpreting requirements with precision and accuracy
🎯 Topic Teamwork
Working productively with other people
🎯 Topic Time Management
Managing competing needs and meeting deadlines
As a developer, you want to refine tickets so that anyone in your team can pick up and deliver any feature in your application.
Given a ticket in the backlog
When I refine the ticket
Then it is ready to be worked on
I expect a refined ticket to have
✅ Checklist
So a refined ticket has all the information anyone might need to complete a feature. This is usually:
🖼️ Refining Tickets Workflow
A ticket is fully refined when anyone in your team could pick it up. If you can validate a ticket in the Backlog as Ready, move it to Ready now.
Only tickets In Progress can belong to any particular team member, so don't claim tickets now.
🎫 Refine some tickets
Read over your team backlog. Validate the tickets against the checklist given above. If there are any tickets that are Ready, promote them from the Backlog.
Now select a ticket from the Backlog to refine. Use the refining tickets workflow. Don't promote your own ticket to Ready - leave that to a team-mate to validate.
You can do this asynchronously or in a call with your team. Whichever helps you to make progress.
The text was updated successfully, but these errors were encountered: