Celebrating Small Wins; The importance of user stories
In software development, one of the hardest things to do well is knowing how to keep track of features that you need to ship, and when to ship them.
A common problem I faced prior to learning, and applying agile software management techniques, is that when there is a feature I am trying to tackle, I end up not knowing how much of a feature I need to build, or how much I have done without looking back at my code and going 'Ah! There was were I previously stopped at.'
In agile software development, a large piece of work / feature that can be broken into smaller chunks is known as an epic.
The smaller chunks within each epic are called user stories.
A real life example I could think of would be travelling between point A to B in say a car. We generally wouldn’t know the details in between A to B.
User stories would be how we actually plan get from A to B.
Celebrating Small Wins
It is often hard to estimate how long we will take when building software, there are too many decisions we need to make, and that can lead to overthinking or poor estimates.
To correct or reduce the risks involved in estimating, we use user stories to help better estimate a task we have at…
