I keep encountering a recurring issue when developing user stories from Epics that the business have devised.
I come up with a number of stories which capture the requirements of the system users and present them to the development team. At this point we review them along with the acceptance criteria and discuss INVEST and potential solutions.
However. when we move onto the sizing a number of them come back as being too large and I'm asked to further split the stories. Every time I have had this issue it seems that what the developers want is for me to split them into tasks for them.
Has anyone else come across this problem? If so, how do you manage it?
In my opinion, as long as your stories are sized to be started, developed and completed involving Dev & Test within one sprint cycle, they are good from a BA perspective.
Dividing them into tasks is Not a BA responsibility.
brought to you by enabling practitioners & organizations to achieve their goals using:
Advertising Opportunities | Contact Us