From the course: Agile at Work: Planning with Agile User Stories

Unlock this course with a free trial

Join today to access over 25,300 courses taught by industry experts.

Story quality and the definition of ready

Story quality and the definition of ready

From the course: Agile at Work: Planning with Agile User Stories

Start my 1-month free trial Buy for my team

Story quality and the definition of ready

“

- User stories, like any other requirement capturing approach, must be a sufficient quality. One of the most significant problems with delivering projects has always been requirements. Agile approaches recognized this, which is why we plan our work in small increments and need to have requirements that can be started and finished in that short period. Agile enables fast feedback and exposes if there are misconceptions or miscommunications about what is being asked for. This is good, but it is even better to address this upfront. Agreeing on the quality of our stories and how we manage it provides great benefits. There are two aspects of quality I will focus on. One is a simple mnemonic that serves as a reminder of story quality. The other is a team agreement, which defines a state of readiness for stories to assure quality before a story is planned to be implemented. A pneumonic called INVEST is one of the longstanding approaches to ensuring we have good quality stories. It was…

Contents