This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
The IDC FutureScape: Worldwide IT Industry 2020 Predictions highlights key trends for IT industry-wide technology adoption for the next five years and includes these predictions: Hasten to innovation. By 2024, over 50% of all IT spending will be directly put towards digital transformation and innovation (up from 31% in 2018).
Get a comprehensive overview and hands-on training on softwarearchitecture's many aspects. There is no single—or clearly defined—path to becoming a software architect. The sessions at the O’Reilly SoftwareArchitecture Conference reflect this fact. Fundamentals of softwarearchitecture (Mark Richards).
A look at the roles of architect and strategist, and how they help develop successful technology strategies for business. I should start by saying this section does not offer a treatise on how to do architecture. It's a given that we must design a system, including a local softwarearchitecture, that actually runs, that is "solid."
If every significant architecture decision has business consequences, then knowing the business model and which trade-offs to choose is maybe the most important skill of architects. But what is the actual relationship between a business model and a softwarearchitecture? A software system is a model of a domain.
From chaos architecture to event streaming to leading teams, the O'Reilly SoftwareArchitecture Conference offers a unique depth and breadth of content. We received more than 200 abstracts for talks for the 2018 O'Reilly SoftwareArchitecture Conference in London—on both expected and surprising topics.
It’s got a selection of free tools you can use for defining your technology strategy, shaping your architectural boundaries, and organising your teams. This means a softwarearchitecture should be purposely designed for the most favourable business consequences. What’s the business vision?
Architecture modernization initiatives aim to convert aging architecture into modern architecture, applying the latest tech innovations and architectural patterns. The architecture becomes easier and cheaper to change, enabling faster flow, and reducing technical debt, fragility and security concerns.
It can guid you through your first few cycles of discovery, strategy, and implementation and then you’ll be in a good place to guide yourself. My advice is to use Simon Wardley’s Strategy Cycle as the basis for your narrative. The Strategy Cycle. Building the Narrative Building a narrative is important for at-least two reasons.
Platforms provide the foundation for higher levels of innovation. Architecture Ownership Patterns for Team Topologies. Part 3: Multi-Team Patterns was originally published in Technology Strategy Ideas and Insights on Medium, where people are continuing the conversation by highlighting and responding to this story.
Typically, there’s a period where modernization is discussed as the pains of legacy systems and/or ways of working are noticed and become ever more prominent, blocking the business strategy. The organization needs to innovate faster to become more competitive. They need a more loosely coupled architecture and empowered teams.
The Nature of Evolution New innovations often become the platform for future innovations. Since then, Google Maps has become the foundation for many other innovations after being opened up to developers via APIs. This is an important leadership and strategy issue. Uber started life as a ride-hailing product.
Product Mode by Sriram Narayan Innovation Portfolio An innovation portfolio is invaluable because it expresses where products and platforms are in their lifecycle, revealing where each fits into the strategy. I’ve been using the Lean Innovation Portfolio for years.
And that in order to achieve this strategy implementing a culture of performance throughout the organization is a must. Another promising browser innovation that we are researching is the content-visibility CSS property. In order to accomplish this, we took a two-pronged approach.
Reading Strategy Patterns One of the techniques I use frequently for visualising business, product, and technology strategy is Core Domain Charts. We’re not investing enough in potential future innovations and sources of revenue. Maybe they weren’t invited for political reasons….
If 95% of your revenue is from Tier 1 customers, you might want to create a Tier 1 context to ensure you can innovate quickly where ROI is greatest. The answer depends on your business model, the levels of co-change and many other factors. Conversely, if 95% of revenue is through credit card deals, you might want to align with products.
One of the key decisions we need to make in softwarearchitecture and in our organisations is when and where to create shared services and organise teams to build them. There are likely to be some big political battles because teams do not want to depend on a shared service for areas in which they need the ability innovate quickly.
It used a proprietary hardware architecture incompatible with its predecessor PC products, and a new operating system (OS/2) that was only partially compatible with DOS, a product strategy not too dissimilar to what IBM did in the 1960s with the System/360 mainframe. We see similar bet-the-business strategies today.
When attempting to explore innovation opportunities, the need for urgent alignment is greater. When the new innovation requires functionality and data from existing products and services, one approach is for the new innovation to be partially owned by each team which the new product cuts across.
Scott Havens, Senior Director of Engineering at Mode Operandi, highlighted the benefits of event-based systems over legacy approaches, and how softwarearchitecture should be just as beautiful as the clothes on sale. Just look at how ugly that service-oriented architecture is!” He had a strategy. Photo credit: @DOES_USA.
The need to keep delivering product enhancements and new innovations while modernization is in process is one big factor, and dependencies between modernization work items is another. This presents technology leaders with one of the most difficult modernization challenges: where to start and in which order to modernize?
Loosely-coupled teams enabled by loosely-coupled softwarearchitecture is one of the strongest predictors of continuous delivery performance and organizational scaling. Where we place boundaries impacts our ability to innovation, the quality of our UX, and execution of our strategy.
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content