My ideal way of working

Analysis Planning

Product owner/manager talk to the customer to understand the scope of the feature request
Define userstories and verify scope of each story with the customer
Plan analysis tickets on the development board of the next sprint for each of the stories
The description of the ticket should describe the entire scope of the story. Give as much info here as possible to reduce confusion later on
Order of the tickets on the board define priority. Higher on the todo-queue means higher prio.
Continue reading

Pull, don't push

Currently

This is the current life cycle of a ticket on the Jira board.

In Progress

When the developer is looking for something to do they open the Jira board and look at the To Do column. Because the sprint planners did their job properly they can simply take the ticket at the top of the column and know that the priorities are right.
So they pull the ticket from To Do into In Progress.
Continue reading