Managing Definition of Ready in TFS

Ready for the sprint? (Photo credit: amanda tipton)
  1. Define and agree to the user story.
  2. Define acceptance criteria.
  3. Identify any dependencies.
  4. Define user experience.
  5. Estimate the size of the User Story.
  6. Create and approve mockups/UI.
  7. Identify training needs.
  8. Identify marketing and communication needs.
  9. Identify content needs.
  10. Determine who will approve User Story

Tracking the Definition of Ready

New “Ready” Activity type for Tasks
No story points? Bad team!

Monitoring and Communicating the Definition of Ready

A User Story with all Ready Tasks completed
It’s easy to see which Stories need more work before they are Ready

The Benefits of Being Ready

Writer and technology leader. Living and working in Cincinnati.

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Mike Hickerson

Mike Hickerson

Writer and technology leader. Living and working in Cincinnati.

More from Medium

An Intro To Agile Development

Technology that Remote Software Developers Need to Know Now

Making Big Improvements with Small Changes

What is a PID, and why do we need it?

PID is between SET GOALS and TAKE ACTION