> ...but the release just felt like a blip in our planned schedule before jumping into more sprints and fires and thinking about the next iteration.
Welcome to agile? I know the feeling, honestly, but in software engineering there's always more bugs to fix, more features to develop, more needs of the users that require your attention. Cutting a release should feel like letting go, and indeed at places it does, but ultimately once the release is out in the wild it's done. The only thing to do then is to move forward with the next iteration, the next sprint, the next release.
Sorry, but are there examples or cites for this harassment from the users? Was it fallout from the layoffs? I feel like I need a bit more context.
Welcome to agile? I know the feeling, honestly, but in software engineering there's always more bugs to fix, more features to develop, more needs of the users that require your attention. Cutting a release should feel like letting go, and indeed at places it does, but ultimately once the release is out in the wild it's done. The only thing to do then is to move forward with the next iteration, the next sprint, the next release.
Sorry, but are there examples or cites for this harassment from the users? Was it fallout from the layoffs? I feel like I need a bit more context.