Product development can be chaotic these days. Planning for these five challenges helps avoid them. By Jim Tyrrell (Red Hat).
According to PWC, one-third of users are unlikely to use any product from a company after one bad experience. That shift in bug tolerance by the developer and change in expectations from the user can lead to chaos.
This challenge of delivering technology-centered compelling experiences that do not require costly support while balancing the needs of past and future development is what author calls the Software Chaos Loop, and it affects most software delivery organizations.
The modern software delivery organization has a solid CI/CD infrastructure and can push an update to production in minutes. This same pipeline can take in upstream library updates and block zero-day exploits. At scale, delivery systems can simultaneously ingest and update software from the hundreds of projects typical to modern application architecture. The scale is incredible.
The article then captures the following:
- Focus the backlog on experiences
- Complete unit and integration testing
- User research focused on users
- Focus on differentiation
- Behavior economics, from adoption to end of life
The Software Chaos Loop affects many software development organizations and prevents them from delivering better products. It also reduces the amount of rework and revisiting of past deliverables that are required.
[Read More]