Business concerns sessions

Software engineers usually find themselves changing hard-coded content on the presentation layer, changing a paragraph here and there; that’s difficult to maintain and hard to scale. Now imagine you have to support and apply the same changes on the website and other devices. Edwin Maldonado provides the tools you need to design a reusable information architecture. Read more.

Ray Mitchell provides valuable insight on how to move an existing system to an improved architecture while keeping the system up and running during the process. Read more.

Communicating (about) architecture to non-IT/business stakeholders is a valuable skill for architects. After all, many architectural-relevant decisions are made by others, so they need to be informed with clear, honest, intelligible, and actionable information/advice. Jochem Schulenklopper shows theory, examples, and useful tips on eight different facets of visual communication of architecture. Read more.

Architecture standards change in months, not years, bringing new capabilities, but taking advantage of them requires constant monitoring and tight feedback loops. We’ve embraced continuous delivery, but how do we enable continuous evolution? Paula Paul and Cassandra Shum explore architecture as code as a means to enable continuous evolution. Read more.

Enterprise organizations are attempting to use managerial mechanisms from previous ages to direct software delivery in this one. The problem is that the principles of modern software-delivery approaches are not translating to the business. Mik Kersten presents the Flow Framework—a new approach to software delivery bridging the gap between business strategy and technology delivery. Read more.

A loosely coupled software architecture and an organizational structure to match is one of the biggest predictors of continuous delivery performance. Nick Tune explains why technical leaders must adopt a sociotechnical mindset to minimize dependencies and maximize team autonomy, optimizing end-to-end value creation and delivery speed. Read more.

Reactive software development is becoming essential to implementing responsive, resilient, elastic, and message-driven solutions. Vaughn Vernon shows you how, by aligning scale and throughput with business-driven model fluency of your core initiatives, you can achieve critical differentiating competitive advantage. Read more.

Every software system has an architecture. Many are little more than the result of circumstances, rather than deliberate decisions. Helping teams think about software architecture is a key to helping them grow well. James Thompson demonstrates how to assess approaches and make decisions based on what matters to your team and your projects. Read more.