Do you give your emails a Business Value?
The problem with emailing a task, is that no one knows how important that email is, in relation to all their other emails. So, what is the solution?
There are the 3 ways people can send tasks:
Figure: Bad example - An email with requirements does not indicate the priority
Figure: Bad example - The developer does not get a chance to ask questions and refine it before it hits the backlog
- Send an email, the recipient reviews it and places it into the backlog, based off the specified Business Value. Developers often prefer this method if they like control over their backlog.
Good example - Email tasks with a Business Value, allow the developer to review before putting it in the backlog
The perfect email workflow
Figure: Good example - The best workflow for sending an email
Figure: Good example - The best workflow for sending an email (with multiple recipients)