Stakeholder management
Before we fully understood how vital architecture and its evolution were within a product’s life cycle, we felt that architecture wasn’t something that teams should consider. Once the AGILE method of doing things gained popularity, how we shaped a system’s structure changed. If in most cases, architecture was discussed from the start in the first place and followed carefully during development, things evolved in a more organized direction. The need for change was perceived more and more. Products changed while being developed. There were two main reasons for this:
- The tech stack changes terribly fast. Approaches and tools evolve quickly and we must create the best user experiences and solid systems for our stakeholders.
- Alongside the evolution of the tech stack, requirements also evolved. Users change their minds, the competition in the same market is enormous, and new features appear constantly.
Considering this, we...
