{"id":158,"date":"2010-11-23T16:37:00","date_gmt":"2010-11-23T16:37:00","guid":{"rendered":"https:\/\/caroli.org\/en\/splitting-crud-stories\/"},"modified":"2020-01-10T19:30:13","modified_gmt":"2020-01-10T22:30:13","slug":"splitting-crud-stories","status":"publish","type":"post","link":"https:\/\/caroli.org\/en\/splitting-crud-stories\/","title":{"rendered":"Splitting CRUD stories"},"content":{"rendered":"

Two of my colleagues came across a CRUD (Create \/ Read \/ Update \/ Delete) story, and asked me for advice on how to convince people on splitting stories.<\/span><\/p>\n

\"crud\"<\/a><\/p>\n

I typically prefer to have smaller stories. In this case, instead of having one CRUD story, I would have one for Read, another for Create\/Update and a story for Delete.<\/span><\/p>\n

Here is an example.<\/span><\/p>\n

As a online store owner, I want to Create \/ Read \/ Update \/ Delete products so that I can offer my customers the top rated products<\/p><\/blockquote>\n

Instead of having this CRUD story, I split it like this (I will add a few sample tasks for making it more illustrative):<\/span><\/p>\n

As a online store owner, I want to Read (view) my products so that I can review what is current available on my site<\/p><\/blockquote>\n

Sample tasks:<\/span><\/p>\n