{"id":6308,"date":"2017-05-04T19:30:40","date_gmt":"2017-05-04T22:30:40","guid":{"rendered":"http:\/\/blog.plataformatec.com.br\/?p=6308"},"modified":"2017-05-05T09:12:07","modified_gmt":"2017-05-05T12:12:07","slug":"the-user-story-in-development-was-deprioritized-what-now","status":"publish","type":"post","link":"https:\/\/blog.plataformatec.com.br\/2017\/05\/the-user-story-in-development-was-deprioritized-what-now\/","title":{"rendered":"The user story in development was deprioritized, what now?"},"content":{"rendered":"

Let’s say you have a Kanban board like the following:<\/p>\n

\"Kanban\"<\/p>\n

Then, suddenly, the P.O. discovers that the features D and E were developed by a competitor and that you are losing users because of that. Therefore, the P.O. decides to deprioritize story C. This is only an example of why a card might be deprioritized in the middle of its development. But now that it was deprioritized, what happens to story C?<\/p>\n

Well, to answer that, let me make a parallel with an alcohol-based perfume company.<\/p>\n

In the backlog column, the company has the bottle ready to be filled but no fluid yet. When the bottle starts to be filled, the card goes to “in progress”. When the bottle is totally filled, the bottle is closed and the card goes to done.<\/p>\n

\"Perfume<\/p>\n

So what happens if another perfume suddenly receives a priority greater than the priority of the bottle being filled? Well, as we all know, alcohol-based fluids are volatile and, with time, they will completely evaporate, requiring them to be refilled.<\/p>\n

\"Perfume<\/p>\n

The same happens with the story and its code. With time, the code that is inside the story gets obsolete and unnecessary, losing its value. What to do with the story depends on the following rationales:<\/p>\n