Skip to main content

Do items listed in your defintion of done end up on your taskboard as individual tasks?

Last post 01:59 am April 7, 2017 by Ian Mitchell
1 reply
09:49 pm April 6, 2017

Do items listed in your defintion of done end up on your taskboard as individual tasks?  For example, let's say your definition of done include the following:

  1. Code Reviewed
  2. Deployed to environment
  3. Tested

And let's say the team has determined the following code changes need to be made to implement a given PBI.

  1. Implement Form
  2. Add Validation Checks
  3. Add Error Notification Messages

When you look at your taskboard would you see the following tasks or would you simply see the 3 coding tasks as it's implied that each task would need to be code reviewed, deployed, and tested before the task could be set to done?

  1. Implement Basic Form
  2. Implement Validation Checks
  3. Implement Error Notifications
  4. Code Reviewed
  5. Deployed to environment
  6. Tested

01:59 am April 7, 2017

All 6 of those activities represent work to be done, so explicitly planning each one as a task would provide good visibility over the work remaining.

Another option may be to capture Review, Deployment, and Testing as finer-grained stations for Work In Progress, such as by including them as columns on a team board. Each PBI would thus need to be reviewed, deployed, and tested before it is Done.


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.