Whats the best way to handle many small requests during a one week sprint period?

[Roni Hoffman]

We have a small number of developers in our team.  And we are getting many smaller requests/tasks that come up during the week.  I want to have a weekly sprint with items to be worked on but we can't ignore the requests that come up during the day/week.  Generally the smaller requests should take priority.

Is there a proper way to handle this?  Should I be adding each request as a ticket and then moving them into the sprint board?

Thanks!

[Petter Gonçalves · Accepted solution]

Hello @Roni Hoffman

Thank you for reaching out.

If the small requests worked through the week will impact the Sprint estimation and should be considered there, the best approach would be to create a new issue and add it to the Sprint with the amount of time estimated.

Issues added after the Sprint start will be displayed with an * in the reports and will be considered scope change, but will properly count to the Sprint estimation.

If the amount of time spent on each request are not relevant individually, you can also create a single request with the total amount of time spent on all the small requests, optionally creating sub-tasks under that parent issue to properly register the work done.

Let us know if you have any questions.

[Roni Hoffman]

Thank for this

[Roni Hoffman]

Hi @Petter Gonçalves 

If I add say 10 unplanned items during a week long sprint, is there a way for Epics and/or other tasks to auto adjust their time estimation or expected due dates?