After pencil drafting , Rita’s back and front end as explained in our previous article:
https://goo.gl/Szjg9E ,we subdivided the whole project into smaller parts in order to have a bit more of a modular approach for the development and order during the coding.
We ended up creating 49 User Stories for all the parts together, front’s & back’s end and admin.
A short definition of user stories is the following one:
User stories are part of an agile approach that helps shift the focus from writing about requirements to talking about them. All agile user stories include a written sentence or two and, more importantly, a series of conversations about the desired functionality.
We ended up creating 49 sentences starting with the same 9 words: “As I user I want to be able to” + do this, do that, select something, change the selection, click on and be sent there, etc…
Missing out on details can sometimes be costly and we thought we didn’t miss any user story but it turned up we were wrong because the CTO identified during the development an important function we missed but were able to quickly adjust with no major changes at all…
Hope you’ll find this article interesting and share our excitement resulting from seeing the baby grow :)
In the next article we’ll explain the technology we decided to use and why. You’ll hear from us soon… Take care buddy.