As newly assigned manager on an already ongoing agile continuous delivery software development project, one of the objectives is the following.
Ensure that software quality meets long term requirements.
The project consist of 50+ software developers distributed on different sub-products. So far, the following issues has been identified, which can be possible indicators that improvement is needed of the software quality.
- No big new features been released in recent time
- Different UX across sub-products
- Some software modules are barely maintained after ownership shifts
- Architect team is not responsible for quality
- Software developers started leaving project
- Seem too much coordinating across teams for new initiatives
- Often workarounds are used meet customer requirements
So far, the approach to quality has been implicit. Recently, the following has been added.
- A Definition of Done of epics
This seems not to capture the above 7 issues, as it has a more narrow focus.
Quality seems hard to measure in a purposeful way as suggested by this and this. Further, it seems hard to navigate after the above 7 issues. This leads to the following considerations. How to identify purposeful efforts? How to estimate the effect of the efforts? When is it enough?
Anyone with any experience on how to approach managing long-term software quality focus?