Series: Part 1 – We’re Here for the Business, Not Purity
I’m fed up with architecture being the perceived blocker. I want to help the business build and ship faster, which means the tech teams have to move faster too. This part surfaces the overall scene and some root causes of the mismatches, and offers practical ways for architects and dev teams to work better together.
Part 1.0 – We are here for the business not for purity
Whenever I work for a business, and meet with the customers or staff wanting technology, I want to help them – my mind explodes with ideas and possibilities. I can see a path through the technology options to deliver something quickly. However, over the years, I have been constantly frustrated by the lack of ways
Part 1.1 — First challenge: Technology Isn’t Mature
First of all there is technology itself, despite the years that have gone by, it still isn’t mature. A consequence is that the very foundation of solutions/ products are changing constantly. Delivering a mature solution has got quicker over the years, but the multitude of new hardware and software solution keeps on “resetting” the maturity
Part 1.2 – Second challenge: The Business
Expectation mismatch Quite rightly, the business community doesn’t understand the technology. The icon on a phone screen, and a few pages once the app is open – how hard can it be? The root problem is that there are orders of magnitude differences what the user sees, compared to the vast complexity of delivering a
Part 1.3 Third Challenge: Us – the techies
The final area of challenge is the difficulty of delivering at a faster pace technology is the technology people… The mindset of techies impacts our ability to communicate with the business – what seems obvious to the developers and techies is not obvious to the business and vice versa. Often the tech community doesn’t help