ESTIMATING TASKS FOR TESTERS
Having tasks on a Scrum Board helps the development team visualise the work being done during the Sprint. This could either be a physical Scrum Board, where team members can simply write and pin papers to the board, or a digital Scrum Board, which can be accessed online from anywhere. Everyone can see which tasks are going beyond the estimated work hours, which tasks another development team member can help out on, and which tasks have impediments.
Task Impediments
Even if the Scrum team has added buffer hours or have considered spikes during Sprint Planning, impediments can still take place within the Sprint.
Impediments are a form of waste that keeps the development team from finishing their tasks. They could be technical difficulties, dependencies, outages, etc. These can come up as soon as someone experiences them during their work. Impediments can also be determined when the Scrum Master or anyone from development team sees a task that is taking longer than expected or as estimated.
For example, when a tester raised a question to the development team that needs further investigation, this question should be tacked to the Scrum Board. Another impediment for testing would be an outage of the test environment – this must also be made visible on the Scrum Board.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: