We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
Architecture Modernization: Aligning Software, Strategy & Structure • Nick Tune • GOTO 2024
Learn key success factors for modernizing software architecture while aligning business strategy, team structure & org change. Practical tools & techniques from Nick Tune.
-
Architecture modernization requires balancing multiple aspects: software/tech, business strategy, team structure, and organizational change
-
Key success factors in the first 3-6 months:
- Deliver concrete improvements to build trust
- Focus on listening and understanding stakeholder needs
- Map current state and desired future state
- Identify the 20% of system that needs modernization vs 80% that can remain
- Build alignment through collaborative workshops
-
Tools recommended for modernization planning:
- Event storming to map business processes
- Wardley mapping to understand component evolution
- Impact mapping to connect business objectives to technical changes
- Process modeling to design future state
-
Architecture Modernization Enabling Team (AMET) should:
- Have strong technical and coaching skills
- Help identify and remove modernization barriers
- Support teams in making progress
- Focus on sustainable long-term improvements
-
Common pitfalls to avoid:
- Trying to modernize everything at once
- Not completing modernization efforts
- Focusing only on technical aspects
- Ignoring business strategy alignment
- Making people feel bad about current solutions
-
Success requires:
- Clear link between business strategy and modernization
- Domain-aligned architecture
- Empowered teams
- Balance between new features and modernization work
- Concrete steps and ownership for implementation
-
Modernization drivers include:
- Competitive pressure from newer companies
- Changed business requirements
- Technical debt slowing development
- Need for faster innovation
- System complexity and maintenance costs
-
Workshop recommendations:
- In-person sessions when possible
- Mix of business and technical stakeholders
- Focus on concrete outcomes and next steps
- Use visual collaboration tools
- Build shared understanding of current/future state