At SSW we have always sent done emails to the owner/requestor to let them know that it is done. Others who are dependent on that tasks are CC’ed so they know they can proceed. But how does that fit into Scrum?
Update 14th April 2010
- Rule added to Rules to better Scrum with TFS
If you are working on a task:
When you complete a Task that is part of a User Story you need to send a done email to the Owner of that Story .
You only need to add the Task #, Summary and link to the item in WIWA. Remember that all your tasks should be under 4 hours , do spending lots of time on a Done Email for a Task would be counter productive. Add more information if required, for example you may have completed the task a different way than previously discussed.
Make sure that every User Story has an Owner as per the rules.
If you are the owner of a story:
When you complete a story you should send a comprehensive done email as per the rules when the story had been completed. Make sure you add a list of all of the Tasks that were completed as part of the story and the Done criteria that you completed.
If your done criteria says:
- Built Successfully
- 30% Code Coverage
- All tests passed
Then add an illustration to show this.
Figure: Show that you have met your Done criteria where possible.
This is all designed to help you Scrum Team members (Product Owner, ScrumMaster and Team) validate the quality of the work that has been completed. Remember that you are not DONE until your team says you are done.
Technorati Tags: SSW Scrum SSW Rules SP 2010 SharePoint
Smart Classifications
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.
What to read next
Combining Scrum, TFS2010 and Email to keep everyone in the loop
Explains how to integrate Scrum, TFS 2010, and email to share task details, maintain history, and keep all stakeholders informed throughout …
Do you know that every user story should have an owner?
Assigning an owner to each user story in Scrum ensures clear responsibility, better communication, and accountability throughout the sprint …
Even Scrum should have detailed Task descriptions
Scrum tasks should include detailed descriptions so anyone can complete them, ensuring project continuity if team members are unavailable or …
Do you have a contract between the Product Owner and the Team?
Explains the benefits of a Sprint Contract in Scrum, clarifying roles and agreements between Product Owner and Team to improve collaboration …
Adventures in Scrum: Lesson 2 - For the record
Highlights the importance of clear communication and documenting disagreements in Scrum to prevent misunderstandings and failed sprints, …
Unlocking Success in Agile: Why Your Definition of Done is Essential for Quality Delivery
Explains why a clear Definition of Done is vital in Agile and Scrum for quality delivery, transparency, and risk mitigation, with tips for …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
The Definition of Done is a Commitment to Quality
Defines the Definition of Done in Scrum as a clear, shared standard for quality, ensuring increments are releasable, transparent, and …
Why Your Definition of “Done” Is Holding Back Quality, Agility, and Trust, And How to Raise the Bar
Is your team’s “done” really done? Discover how a clear, objective definition of done boosts quality, agility, and trust in product …
Acceptance Criteria vs Definition of Done: Why Getting This Right Builds Trust and Delivers Quality Faster
Stop confusing acceptance criteria with definition of done, learn the crucial difference to boost quality, speed, and trust in your agile …
How to Evolve Your Definition of Done: Start Small, Grow Smarter, and Build Lasting Momentum
Unlock a smarter Definition of Done, start small, evolve standards, and build team momentum without overwhelm. Discover how progress drives …
Why Most Transformations Fail Without Honest Conversations
Most transformations fail without open, honest conversations that address real issues, making transparency and tough dialogue essential for …
Why Your Definition of Done Is the Secret Weapon for Real Business Impact and Agile Growth
Transform your definition of done into a strategic advantage, deliver real value, reduce risk, and drive business impact with every sprint.