Developing Software architectures is a demanding task that is usually quite rewarding (aka "fun")
## Missing requirements
The whole thing would be even better, if somebody told the development team what exact problem they are supposed to solve.
In other words: Teams urgently need better requirements as the basis of their development work.
In our 20+ years of architecture and development experience, we consistently encountered teams around the world to complain about missing, incomplete or contradicting requirements.
Our brief and fast-paced tutorial summarizes some important and pragmatic approaches that architects and development teams can follow to improve their requirements. It starts with better stakeholder management, more efficient overview, elegant formulation of functional requirements and, last not least, a pragmatic approach to handling quality requirements.
## Technical and other Debt
Which leads to the second recurring issue: The existing systems which most of us regularly work on often carry a load of technical and organizational debt.
In other words: These existing systems are in serious need of improvements, to become maintainable and future-proof.
But how to start? Management does not listen to your pleas and demands more features.
Small refactorings don’t solve the root causes of evil problems.
That’s where systematic architecture improvement comes into play: A pragmatic and simple approach to methodically address all kinds of problems, technical and organizational.
In our workshop, we demonstrate the fundamental techniques and methods for architecture improvement, technology-agnostic and applicable to all kinds of development projects.