Daily Standup
- James Seabrook
This is time-boxed to 15 minutes.
The standup is for the development team to hear about what they did in the preceding 24 hours, what they are planning to do in the next 24 hours and what is blocking progress.
The Dev Standup board is designed to facilitate this.
Any meetings which are required as a product of the standup should be scheduled for another specific meeting. This will help prevent people being unnecessarily held up from their work.
Staff members on Standup board
All Indigina Windsor staff are on the board as well as some iTransition development and Testing and Support staff. When a user is selected it will show only those tickets which are currently assigned to that user. The testing staff tickets are available for visibility of tickets which have been moved on from development.
Filters
Any filters can be combined and this will use “AND” logic to reduce the number of hits.
Filter Name | Filter behaviour |
|---|---|
All tasks except for stories and epic | |
Only stories (for grouping tasks) | |
Support / Maintenance tasks only | |
Unassigned | |
Has been touched by Mark | |
Has been touched by Gurminder | |
Has been touched by Danny | |
Has been touched by Dean | |
Has been touched by James | |
Has been touched by Alon | |
Updated in the last 3 days | |
Development staff only | |
Ad-hoc requests only | |
Completed by development in the last 2 weeks, ie. set to QA | |
Marked as done (resolved) in the last 2 weeks: ie. entire life cycle has been completed |
Swimlanes
“Planned” Swimlane
Ticket Labels have “Planned” in them or they are the highest priority. This will send them to the “planned” swimlane. Only items which are planned to be worked on should be in this swimlane.
Order of Priority
“Ranking” is enabled which means that the tickets can be ordered by priority within the development board. This enables different tickets to sit in priority order across different projects.
Rules
“In Progress” column
The board should not contain any “In Progress” entries which are not in the “planned” column. This is because these should be in the backlog (to-do column). There may be exceptions to this but the exceptions should be either in the comments or in the summary (the summary is visible which really helps).
“To-do” column
This is work which is coming up. The only tickets to work on in that list should be “planned”. This is either because the ticket is being amended to update specifications or the work will become “In Progress” for development during the week.
“Blocked” column
The blocked column is for work which is in progress but which cannot be actioned because of a block. The blocking reason should be in the comments. After the end of the week the blocked tickets should be moved back to the backlog as they have been unable to be worked on for too long.
“On Hold” column
For the time being the “On Hold” column is simply for things which have been put on hold for a specific reason. This means they are not blocked as such but will be imminently returned to “In Progress”.
There is an argument that “On Hold” should not exist and they should go back to the backlog.