Say that you have user stories like user A, B, C, D and E want to do. However, describe all the features of a web application that does not exist yet.
So, how do you handle user stories like making project structures and building all the scaffolding and service levels and all?
I agree that there are many ways in it, every time I have done it in something special, like 'technical user stories', I have always been told how you do not tighten. .
As you are right, this problem has many different perspectives.
Some teams have given Sprint 'Sprint 0'. This happens when all the sets are up and there is also an initial population of the backlog. The downside with this approach is that this business does not focus on providing value and so can oppose the product owner and stakeholders.
My preferred method is to choose a simple user story and set up as a part, assuming size about it, it should be kept in mind. This can also mean that you only offer a very simple item of functionality in its first iteration. But at least you are providing some business value and are being end-to-end in the set up process.
It follows the principle of peak "Our top priority is to make the client satisfy through fast and continuous distribution of valuable software."
No comments:
Post a Comment