Results
Less time spent updating diagrams
Stakeholders understand system design
Faster architecture decision making
Introduction
Alphabet is a BMW group company that provides global business mobility specializing in leasing and fleet management. They offer a wide range of services at every stage of cooperation - from consultancy and financing to service support, as well as comprehensive fleet management programs of all car brands.
Business Pains
- What are we building?
- What do we connect to in the existing landscape when we roll out a new service?
- How can I steer product development without a view of the technical structure of my development?
- Why are there so many different views, formats, and templates?
- Why is it so much effort every time to draw from scratch?
Engineering Pains
- How does the low-level user story I am working on fit into the solution design?
- What is the solution design actually? Where is it? Do I have to hunt it down in confluence (other wikis available)?
- How does my domain link to other domains?
- Where should this object belong?
- Why can't I have a visualization of my services?
- Do I have any dependencies upcoming with the changes I will work on?
- What is a simple way to communicate all these designs?
"All stakeholders now easily digest the complexity of our landscape."
Application architect
Conclusion
- Alphabet has increased visibility between the engineering, product and business teams using IcePanel as a central resource for visualizing their architecture.
- This increased visibility means the teams have a shared understanding and make more informed decisions from a common knowledge base.
- The accessibility and ease of use mean anyone can jump in and learn from richer visual information, meaning teams and stakeholders understand more about how their systems work and the state of the architectural design.
Is IcePanel for your team?
Try it out for free and see what you think.
