Overview

Weekly planning is done using the Dev Standup board DS board - Agile Board - JIRA (atlassian.net). These are the current guidelines:

There is a “planned and expedited” swimlane which gives visuals for the upcoming week. It contains

• highest priority (expedited)

• planned work

All work which is planned to be done, including support tickets, should be marked as planned (by means of a label). If this can be done up-front, ie. before the meeting at 10am then so much the better.

Ultimately, all expedited tickets should be planned tickets but sometimes this is not possible, eg. if they are on hold. There is a possibility to have separate swimlanes should the highest priority and planned work tickets diverge.

Regular Processes

• On Monday preferably before, or if not after the meeting update planned tickets to contain a label “Planned”.

• Check the status of tickets to ensure that they are up-to-date (in progress, on hold, blocked, released, done)

• create ad-hoc tickets where relevant. These are not seen as part of the development, but ad-hoc tasks which are likely to be more than one hour in duration

• on completion of the ticket add the amount of time spent on it in the “actual time” once the “actual time” field has become available

Blocked Tickets

As developers we have to take a view on whether somebody is going to get back to us on something which we are waiting for, eg. requirements clarification. If they don’t get back to us in a certain time (one week as an experimental start duration) then the ticket should be returned to the backlog. The requester will contact us when they want us to progress the ticket and we can then plan for it in the next week.

Blocked Tickets

Action Items