My team is currently working on defining user stories with the product owner. He supplied us with a story that is on one hand quite complex, on the other hand he says, that no part of it is independently of value.
I would like some hint on how to do this in scrum:
Our field is a register for last wills, the users are people who search for and handle last wills for deceased citizens.
Our stories now are:
A User wants to enter Filter criteria to get at max 100 results from the Database at once. (business process = "send inquiry")
results are digitally signed according to law xY max 100 rows at once a button for "the next 100" last Name, given Name, as possible filter criteria
And then there is a second story:
An Auditor wants to review all "inquiries" sent by a defined user, to see if he entered legally correct filters, see what results were provided at the time of the inquiry, and see if the user handled all results properly (legally).
results are digitally signed according to law xY Story 1 criteria as possible filter criteria ( action would be: "give me all inquiries where the user filtered for "given Name"="Bob"") show the same results as the user saw at that time results never change
SO if my team now decided to tackle Story 1 now, but Story 2 on a seperate sprint:
How I have to handle these "inquiries"in Story 2 obviously influences the implementation of Story 1.
It is even legally not allowed to deliver a final product with story 1 but not story 2 (these reviews are mandatory once a year for each user)
Are these one story? Does scrum encourage just implementing Story 1 with no regards to story 2 and possible having to rework Story 1's result to enable Story 2? Do I add "inquires have to be stored with filters and results" as an acceptance criterion to Story 1 and reference Story 2 (that would break the "independent" requirement of the INVEST principle)?
My main question is:
If two stories have potential(or are sure to) to influence each other, but cannot be completed in the same sprint, do I:
- disregard the second story's influence (need to redo work, but decide as late as possible)
- merge the stories (make it more complex, but delivering the full business value of the features)
- Plan the influence into the implementation (no need to refactor - possible time saved later, but no longer independent stories, working against the "embrace change, decide late" principle)
All courses i took and free videos I watched, papers I've read did not give me a satisfying answer, I really need your help here.
Thank you in advance!