Series: Part 3 – A Fr-Agile Architecture
What makes an architecture agile? Are you ready to accept changes at every level in your design or architecture? What does it mean to be on the bleeding edges?
The following posts look at trying to get the right balance in your role for your organisation.
Part 3.0 – A Fr-Agile Architecture
You want an architecture to be able to respond quickly to changes in requirements or technology. Often the latest cloud services promise simpler architecture patterns, or the latest tech promises faster solution delivery. What those promises don’t cover off is that you need to plan to offset the benefits because they are generally not 100%
Part 3.1 – Riding on the wave of other people’s problems
In surfing, the best place to be is in the “power pocket” or curl of the wave. You have to wait a bit longer to be there, but that extra wait means you get to surf at the maximum speed possible for that wave. Get anything wrong (too soon or too late) and you get
Part 3.2 – The bad old days of architecture
For many years everyone strived for the “perfect design”. Frameworks, such as TOGAF, do allow you to do this. However, unless you are on a multi-million pound budget per quarter, no project has time for this. This drive for perfection, has led to organisational structures that: involve many teams reviewing your design; lots of quality