Some background: At work, there are several epic (user visible) stories whose effort will be greatly reduced by improving the roles and permissions infrastructure in our code base. However, the effort of shoe-horning any one of these epics into existing infrastructure is less than the effort of improving the infrastructure.
Our team has been tasked with improving our roles and permissions. Additionally, since we would like to follow an Agile methodology, we have been given one of the mentioned epics to work on and are attempting to follow Scrum while building it. However, we are struggling with coming up with user stories that produce work that:
- is user facing (as all user stories should be),
- improves our infrastructure in any significant way, and
- fits into one sprint.
It seems to be a 2 out of 3 deal: Either we make things user facing and fit into one sprint at the expense of making things harder to fix in the future, or we improve things in 1 sprint that we can't show anybody, or we improve things and make changes user facing but it doesn't fit into 1 sprint.
This makes me wonder if there is an Agile methodology that would work for us better than Scrum. Do you have any suggestions?