One of my colleagues proposed an idea to split stories by default each time we write stories for the project into sub-tasks to represent different types of work a story has.
We are using Scrum and Jira at work.
The pros of that approach as I see them are:
- probably better estimations ("probably" because this will be more difficult to align a sum of multiple story points estimations from the sub-task with the Fibonacci sequence)
The cons, however, are pretty substantial in my opinion:
- more work to organize the workflow
- huge rise of the number of PBIs (product backlog items) which will screw up the statistics of sprints
- the team still has problems with passing the items around the Kanban board and reassigning correct people at different stages of development. In the scenario proposed we will have to interconnect sub-tasks and then manually go through the PBIs to make sure certain stages of development are complete
- there has to be a reason for each PBI to exist in the backlog - if I create PBIs just because I split all the stories by default, the whole process becomes less meaningful and I just let it slide
- we have already got 1500+ PBIs so it would make it difficult to switch tracks mid-project even for only open stories
In the end, I think that I should keep it simple but I would love to get your ideas so I could make sure that I am making a well-informed decision and not missing anything.