Tasks - Do you know to use clear task descriptions?

When you create tasks in Scrum you are doing this within a time box and you tend to add only the information you need to remember what the task is. And the entire Team was at the meeting and were involved in the discussions around the task, so why do you need more? Once you have accepted a task you should then add as much information as possible so that anyone can work on that task.

You can use rich text and images to be extra clear, or even attach an email to the task.

❌ Figure: Bad example - there is not enough information for anyone to complete this task

✅ Figure: Good example - Azure DevOps - Lots of information so anyone can pick up that task

✅ Figure: Good example - GitHub - Lots of information so anyone can pick up that task