Tasks - Do you know to ensure that relevant emails are attached to tasks?
27/06/2016 11:30 PM by
Often you will receive rich information from your Product Owner (Customer) about tasks. That information can be in the form of Word documents, HTML Emails and Pictures, but you generally receive them in the context of an Email. This should be done by one person called the scribe.
The Scribe will:
- take screenshots and notes
- turn them into multiple emails
- add them into the backlog with Team Companion (can be added directly into TFS on Web Browser)
You need to keep these so your Team can refer to it later, and so you can send a “done” when the task has been completed. This preserves the “history” of the task and allows you to keep relevant partied included in any future conversation.
Keep the original email so that you can
reply DONE and delete the email.
But keeping it in your email does not help other members of the team if they complete the task and need to send the “done”.
Worse yet, the description field in Team Foundation Server 2010 (TFS 2010) does not support HTML and images, nor does the default task template support an “interested parties” or CC field. You can attach this content manually, but it can be time consuming.
You should follow the existing
Rules to Better Project Management and attach the email to your task so you can refer to and reply to it later when you close the task:
When replying to an email with “done” you should follow:
Following these simple rules will help your Product Owner understand you better, and allow your team to more effectively collaborate with each other.
An added bonus is that as we are keeping the email history in sync with TFS. When you “reply all” to the email all of the interested parties to the Task are also included. This notifies those that may have been blocked by your task to keep up to date with its status.
Do you feel this rule needs an update?