Breaking down Product Backlog Items

1. Workflow steps? 2. Business rules?

What steps does a user perform? What rules apply to this story?
Are all the steps necessary now? Are all business rules necessary now?
Can steps be simplified for now? Can simpler rules suffice?

e.g.Steps in an order process, like selecting a e.g. Rules in an order process (no order below 10
payment option, delivery method, etc. dollars, no shipping outside US)

3. Happy / unhappy flow? 4. Input options?

What does the happy/unhappy flow look like? Which platforms are supported?
Are all unhappy flows necessary (right now)? Are all platforms required (right now)?
Can unhappy flows be simplified (for now)? Are some platforms harder to implement than others?

e.g. Failures during a webshop order process

and possible recovery options e.g. Tablet, iPhone, desktop, touchscreen

5. Data types and parameters? 6. Operations?

What datatypes are supported and relevant? What operations do the story entail?
Which parameterized views are there? Are all operations needed right now?
Are all parameters relevant at the moment?

e.g. Different search options/strategies or different e.g. Breaking down on CRUD (create, read, update,
kinds of reports (tables, graphs, etc.) delete)

7. Test cases? 8. Roles?

What test scenarios will verify this story? Which roles are involved in this story?
Are all test scenarios relevant at the moment? What can the roles do?
Are all roles necessary now?

e.g. Some test scenarios may be very complex, but e.g. A customer can create orders,
not highly relevant at this time administrators can manage orders, etc.

9. Browser compatibility? 10. Optimize now vs optimize later?

What browsers have to be supported? What optimizations can we think of (UX/UI)?

Are all optimizations necessary now?

e.g. Ignoring support for Internet Explorer 9 e.g. Implementing autocomplete for addresses,
because only a fraction of users makes use of it usage of GPS-location