3 thoughts on “Agile Resources”

1. I need advice on how many repeats of ‘given / when / then’ entries are best put in acceptance criteria, in the same scenario.

   For example, ‘As an online operations employee, I want to delete store type information, so that outdated store types are no longer present for association with store information’

   Would one put in the acceptance criteria, each of the steps to be followed, like this :

   1. Given that the employee is logged into CMS and the Store Type Management page is displayed, when the grid is displayed, then an option to delete store type information should be available through a delete button in the action column in each store type’s row

   2. Given that the employee is logged into CMS and the Store Type Management page is displayed, when the delete store type button is clicked, then a confirmation popup should appear stating the type which is about to be deleted along with yes and no buttons

   3. Given that the delete button has been clicked and the confirmation popup is displayed, when the yes (confirmation) button is clicked, then it must be validated that the relevant store type is not linked to a store.

   4. Given that the yes (confirmation) button has been clicked, when the relevant store type is verified not to be linked to a store, then it must be deleted from the database table and a success message should be displayed.

   5. Given that the yes (confirmation) button has been clicked, when the relevant store type is verified to still be linked to a store, then an error message should be displayed stating that the type is still associated with a store’s information and no changes are made to the database.

   6. Given that the delete button has been clicked and the confirmation popup is displayed, when the no (confirmation) button is clicked, then the popup should close and no changes are made to the database

   This seems WAY too wordy. Please advise..

   Reply

   1. Hi Phil,

      Thanks for writing. I strongly recommend that acceptance criteria not be written down in long form anywhere. Instead, use a word or two for each acceptance criterium and then use ongoing conversation with the team as well as automated acceptance tests (e.g. Specification by Example) to share and capture important details. You are right: it IS way too wordy.

2. Hi Mishkin,

   I have a possible addition to suggest for your agile resources, hopefully you’ll find it useful for your readers!

   The top 15 agile books you should read (infographic with a brief written overview) – https://www.knowledgetrain.co.uk/resources/practice/top-agile-books

   Thank you,

   Alison Wood

   Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.