Architecture Modernization: Aligning Software, Strategy, and Structure - Nick Tune

Interesting. speech About software modernization in large companies that face difficulties in legacy systems:) Such companies often have steep advantages: market share, brand reputation and customer loyalty. Therefore, it makes sense to modernize the system and the author speaks with the definition

Architecture Modernization is about converting architecture from a competitive disadvantage to a competitive advantage. His approach then contains three points.

1. Architecting for flow Design to improve the flow of value creation and the relationship of change
2. 5 Essential tools for architecture modernization Tools for Modernizing Architecture
3. Kickstarting and enabling architecture modernization How to start upgrading

In the first part, the author talks about stream-aligned teams from team topologies that form around value-stream. Separately, it should be noted that sometimes there are dependencies between command systems that affect the flow. Everyone wants to create autonomous teams. (There was a lot about this in the report I was talking about. told yesterday):)

Next, the speaker talks about full-stack modernization at all levels

• User interface - modernize the UI to enable a better UX improving user happiness and productivity
• Software - modernize tech and alignment to domain model for code that is easier to understand and evolve.
• Domain model (conceptual) - modernize the conceptual domain model, creating a better shared understanding and language improving collaboration & innovation
• Domain - modernize the domain by adding new and better capabilities which create new business and customer value.

The following are the tools:

1. Active hearing It helps to understand business goals and stakeholder concerns
2. Impact mapping Strategic business objectives - actor - impact - deliverables. You can read more about the book Impact Mapping. wrote earlier
3. Wardley mapping The components of the architecture are related to the value chain as well as the stages of the product life cycle. Interesting. conceptIt's an architecture that I first learned about and can be used to determine the current state and evolution of architecture components.
4. Event storming - this is an interesting approach lkz workshops for collaborative study of a complex business domain. You can read more about it in mine. post
5. Modernization strategy selector - a schedule for discussing modernization options through platform modernization and product, domain, software modernization At the end of the book, the author remembers. CodeScene A tool for behavioral code analysis.

Next, the author tells how to start the modernization and shows the matrix 2x2 (risk-effect). In the end, we have

1. "low fruit" (The risk is small and the effect is significant.)
2. Projects for those who avoid risk (Risk and effects are minor)
3. Projects for those who are ready for a big bet n (risks and effects)
4. "last pasta in the tube" (low-impact risk projects) This is often never done at all:)

As a result, it is necessary to pick low-hanging fruits and give results in the first 3 Six months, but continue to work on major changes in parallel. During modernization, it is necessary to make a support team for the modernization process, but then it must be disbanded in time. A successful company has its pros and cons, such as complexity and inherited processes, but this is the price of success. But startups don’t have such problems and can innovate faster. Also, modernization must be more than just technical improvement, and that technology alone will not solve all problems. And finally, the speaker is the captain of the obvious and says that it is important not to overestimate investments in the wrong areas and not underestimate them in the right areas.

#Processes #Management #Performance #Engineering #Software #SoftwareDevelopment