Task Sprint
- DarkLight
Task Sprint
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Any requests or issues sent to us throughout the week that can't be immediately actioned by our support engineers will be booked into our Task Sprint workflow.
Tasks are now placed in a global queue where our Product Engineers, Front-End Developers and SEO Experts can pick up tasks based on their availability. This new approach allows us to pickup and action tasks any day of the week instead of the previous process which set aside 1 day a week exclusively for this work.
Tasks are arranged on a first-come first served basis with the exception of business critical P1 and P2 tasks. Our priority definitions can be found here: SLA & Priority Definitions
If your request is estimated to take more than half a day in the studio, we will arrange a separate time for the team to address it which will be communicated to you. This ensures that as many tasks as possible are completed promptly.
We review and test each task before sending it back to you. If you feel your issue or request requires more work, let us know, and the team will investigate further.
Below we have included a breakdown of the new Task Sprint process
Task Sprint Process |
Task Assignment: Tasks are immediately assigned out to a global queue for the respective teams where developers are free to pick up tasks as and when they have capacity. |
Working Times: Developers are free to action tasks any day of the week to fit around their workload. This will naturally allow for faster resolutions throughout the whole week instead of being limited to 1 day. |
Resolution Time: 3 weeks maximum, work can be completed any day of the week. |