Just a Simple Paragraph

This post is the fourth one in the first Build-Measure-Learn cycle. In the last post, I broke down the story “Import a Text or Document File” into smaller stories. From the resulting set of smaller stories, I have picked the one called “Import a File with a Single Paragraph”. I am going to detail this story and add some acceptance criteria. Continue reading “Just a Simple Paragraph”

User Story “Import a text or document file”

This post is the third one in the first Build-Measure-Learn cycle to build a Minimum Viable Product. In the last post, I broke down the epic ‘Storing text files’ into major user tasks. With the new set of major user tasks, I was able to tell into detail Anton’s story of importing some files into the Text Analyzer Platform. From the set of major user tasks I will pick the story “Importing a Text or Document File” for implementation. I will flesh out the story and then analyse the story applying the INVEST characteristics. As a result, the story has to be split up into even smaller stories. Continue reading “User Story “Import a text or document file””

Exploring the Major User Task ‘Storing text files’

In the third post, I gave an insight into the story of the Text Analyzer Platform using the ‘User Story Mapping’ methodology. This is the second post in the first Build-Measure-Learn cycle to build a Minimum Viable Product. It comprises of the decomposition of the major user task ‘Storing Text Files’. We are now going to look at this part of Anton’s story in more detail. It reveals some important properties of the Text Analyzer Platform (TAP). Continue reading “Exploring the Major User Task ‘Storing text files’”