Secret ingredients to quality software


Do you give your emails a Business Value?

Last updated by Penny Walker on 04 May 2017 12:37 am (about 4 years ago) See History

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:

  1. Send an email only. Email sign

Figure: Bad example - An email with requirements does not indicate the priority

  1. Put the task straight into the backlog, and send no email: straight to scrum

Figure: Bad example - The developer does not get a chance to ask questions and refine it before it hits the backlog

  1. 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. Developer entered

Good example - Email tasks with a Business Value, allow the developer to review before putting it in the backlog

The perfect email workflow

Before you email a task to someone, think about how important it is to you. Then draft your email, add the Business Value using the same scale that you would use to estimate your PBIs. Email Diagram

Figure: Good example - The best workflow for sending an email

Q: What if you need to write an email to multiple recipients? A: Assign each person a Business Value. In the case of "To Myself" emails, you can also add the amount of 'Effort' required too. Email screenshot

Figure: Good example - The best workflow for sending an email (with multiple recipients)

Related links

Adam CoganAdam Cogan
Ulysses MaclarenUlysses Maclaren
Penny WalkerPenny Walker

We open source. This page is on GitHub