Menu
While applying Scrum, the product backlog items are users stories. I have created a sample story on TFS as follows:
As a user, I can signup to system.
I then created the following tasks:
Some of the tasks are frontend (HTML, CSS, etc) and some are backend (send email, etc).
697
There are a few important things to consider when breaking down user stories into tasks: Keep tasks small, but not too small. As a rule of thumb, a task should be something that can be done within a single day, but not in a few minutes' time either. Keep tasks very precise in scope.
When splitting user stories, we should always split them vertically as if we are slicing a piece of cake. The whole cake is a cake and each vertical slice is a piece of cake with all it's layers.
Why Split User Stories? The simplest answer is that they are too big to complete within a single Sprint. If that's the case, then you will have to find a logical way to split it into smaller pieces – some of which would then be right-sized to get to “done” inside of a Sprint.
Agile teams often use 'estimating poker,' which combines expert opinion, analogy, and disaggregation to create quick but reliable estimates. Disaggregation refers to splitting a story or features into smaller, easier to estimate pieces. (Note that there are a number of other methods used as well.)
No. Agile focuses on delivering working code to the customer. Without each part implemented the code written offers no value. Unless the tasks can be shown to offer independent value, then they should be kept together.
Yes the different parts can be implemented by different people. You need to make sure they coordinate appropriately so that the requested feature as works a whole.
77
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
