I currently work on a large scale software project in a large company.
We follow an agile approach for development; however, due to the size of the the company there are several stakeholders that normally are not spoken about or simply assumed to be the developers in the Agile process.
- Architecture: Defines enterprise architecture guidelines
- Development: Defines enterprise development guidelines
- Product Design: Defines enterprise branding and design guidelines
IT Security: defines enterprise IT security guidelines
Operations: 24/7h operations support
- Customer Support: 24/7h client support
- Rollout: Rollout of the application per client ( client specific configurations )
Should I use User stories?
As IT security, I want to ...
or Debt tasks?
Tech debt - Code needs to be refractored
- ISO debt - Application must follow ISO1234
- Rollout debt - Configuration automation
- Operations debt - Special tool to manage data cache
- As application management, I want to be able to invalidate the cache, so the application is cleared of corrupt data.
The above doesn't really make sense to me as a business value user story. It represents more a maintenance required feature.
Is there any common practice on how to integrate the requirements of these stakeholders in user stories?
What is the best way to express the requirements from these stakeholders? They are functional yet not business value adding requirements.