I am working with a team that is maintaining case management software. We are suffering from drift between different specifications, agile artefacts, implementations and understandings. I would like to propose a solution to the team that aligns with agile methodologies that works for our team.
Frequently, we will get a request to "show additional data X about entity Y on screen Z", where X may be an existing or new field/property, and Y and Z are almost always an existing entities / screens.
There would have already been a user story that has long been closed:
As a user ... I want to see information ABC about entity Y so that I can ..., which would have been used to create the screen in the first place.
field X would just be another piece of information that is not important in itself, but is important when in the context of
entity Y. I would find it hard to justify having a story purely to see
field X, and other stories typically look at collections of data, not single datums.
Create a new story
As ... I want to see X about Y so that I can ...- this keeps closed stories closed, and means smaller, more incremental stories, but also means that the old story is no longer current, so I can't treat it as part of the documentation.
Re-open the old story and update the acceptance criteria
As ... I want to see ABCX about Y so that I can ..., and then create a task
Add field Y to Z- this means that stories, tasks (and other artefacts) are all up to date. Typically, the
Some other solution? Perhaps use a feature/epic/whatever to track
screen Z, and keep that up to date with all the fields about entities that
screen Zwould display, and then use method 1 and reference the feature?
Something completely different?