Scribd
Upload
94 views1 page

Grooming Questions

The document outlines questions to consider when implementing a user story such as testing requirements, dependencies, architectural challenges, code reuse opportunities, security aspects, performance, developer capacity, demonstrations, alternative implementations, interpretations, technical debt, vague terms, tasks, skills, and splitting into smaller stories.

Uploaded by

CG
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
94 views1 page

Grooming Questions

The document outlines questions to consider when implementing a user story such as testing requirements, dependencies, architectural challenges, code reuse opportunities, security aspects, performance, developer capacity, demonstrations, alternative implementations, interpretations, technical debt, vague terms, tasks, skills, and splitting into smaller stories.

Uploaded by

CG
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

1.

Do we understand what we can do with the system after the story is completed (that we
cannot do with the current system)?
2. How would you test this user story?
3. Where do we see dependencies with other user stories or teams?
4. What architectural challenges do you see?
5. What parts of the implementation looks like code that already exists elsewhere, and
should we reuse it?
6. Are there security aspects we need to take into account?
7. Are there performance or UX aspects we need to take into account?
8. Is there any developer that thinks they cannot build this? Why?
9. What should we demo to show it works as planned?
10. Do we know any other implementation of a similar solution (in our own organization or
elsewhere), and where does our solution differ?
11. Is there any other implementation that we can do that is clearly not what we want, but
that satisfies the requirements anyway?
12. What other interpretation could a developer use to build the user story, and what test
do we need to perform to detect this?
13. Where do we create technical debt if we implement this user story as planned?
14. What vague terms are used in the user story—e.g., fast, soon, early, better, easy?
15. What tasks do we need to complete for this user story, and who wants to do (or not do)
what tasks?
16. What skills are needed to complete this user story, and do we have these skills in the
team?
17. Is it clear how the user story contributes to the product vision of the product owner?
18. Can we split the user story into smaller ones and still add value?

You might also like