The rise of the agile architect
•Download as PPTX, PDF•
1 like•253 views
My talk from Agile Cambridge 2017. There has been a necessary evolution of architects since the publication of the Agile manifesto. The traits and qualities of the agile inspired architect has become the standard bearer of architects everywhere. In this talk I go through those traits that make the Agile architect such an important addition to any team
More Related Content
Similar to The rise of the agile architect
Similar to The rise of the agile architect (20)
More from Reda Hmeid MBCS
Recently uploaded
Recently uploaded (20)
The rise of the agile architect
- 2. The Rise of the Agile Architect
- 3. Who am I • Software architecture consultant, helping organisations to lay foundations for digital and agile transformation • Started professional software career in 1999 on fledgling ba.com • Currently Interim Head of Solutions @ HMRC Digital • Father of 4 • Love sports
- 5. Working software over comprehensive documentation Agile Manifesto
- 6. The best architectures, requirements, and designs emerge from self- organizing teams. Principles behind the Agile Manifesto
- 8. The Greatest
- 10. Working software is the primary measure of progress Principles behind the Agile Manifesto
- 11. Continuous attention to technical excellence and good design enhances agility Principles behind the Agile Manifesto
- 12. Architectural styles are not a defined set of pros and cons but a defined set of characteristics.
- 13. The Democrat
- 15. The best architectures…….emerge from self-organizing teamsPrinciples behind the Agile Manifesto
- 17. The Coder
- 19. Working software is the primary measure of progress. Principles behind the Agile Manifesto
- 20. To understand the developer, you needed to have been one.
- 21. There is no difference between architectural principles and coding principles. It’s all just software development principles.
- 22. The Artist
- 23. Simplicity is the ultimate sophistication. Leonardo da Vinci
- 24. Simplicity - the art of maximizing the amount of work not done - is essential. Principles behind the Agile manifesto
- 25. Simplicity is about having the minimum components, systems or technologies needed to meet functional and non-functional requirements within constraints
- 26. Keeping things simple • Evidence based architecture – avoid dogma or assumptions • Flash architecture – what affect does removing components have • Introduce new systems to add functionality, not solve a problem • Use well established technologies wherever possible • Avoid CV driven architecture • Just enough is still enough
- 27. The Genius
- 28. The true sign of intelligence is not knowledge, but imagination
- 29. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Principles behind the Agile Manifesto
- 30. Sustainable development is development that meets the needs of the present without compromising the ability of future generations to meet their needs The Report of the Brundtland Commission via Kevlin Henney
- 31. Final Thoughts….
- 32. Q&A
Editor's Notes
- Last year was a bad year for celebrity deaths. Amongst them was my hero growing up - Muhammed Ali.
- Watch this. This is Muhammed Ali at his peak. In fact, it’s boxing at it’s peak. Graceful, poetic, beautiful. This fight took place in 1966 against Cleveland Williams, who was a huge puncher. 3 rounds, Muhammed Ali knocking his man down 6 times, in the process landing 100 punches and being hit by just 3. In parlance we’d all understand, what you’re seeing here is industry best practice. If this was a text book, this would be Sam Newman’s Building Microservices, Jim Webber’s Rest in Practice or Eric Evans’ Domain Driven Design. What I never really grasped growing up watching Muhammed Ali videos, was that Ali’s style of fighting was not chosen because of aesthetics. It wasn’t a case of style over substance. It was chosen because it was his belief that fighting this way was going to bring him the most success. It was what was going to make him the greatest heavyweight of all time. And like the young me watching Ali’s fights, we sometimes misconstrue why we try to stick to an architectural style in a purest way. It can appear that these styles are nothing more than academic exercises, built upon theory, but we forget that these were forged from the experiences of others within our industry. We lose sight of the reasons behind the defined architectural styles and start to use phrases such as pragmatic REST to describe RESTFul APIs sans HATEOAS. We start to define as pragmatic, approaches that are not aligned to industry best practice. And architects fear being called purists because of the connotations behind the phrase. Blindly following something without determining it’s suitability for the problem at hand. And this may have once been true. But for the Agile architect, being a purist is nothing more than
- When Agile first entered into BA, the whispers around the place was that
- Controversial view – the role of the architect these days is to serve the developer. Make the life of the developer easier. Why
- Ultimately, working software requires someone to write code. And while
- 2 reasons These days it’s important What is architecture? Where does architecture start and design ends? Simplicity
- Published in 1988, a report in pursuit of producing sustainable economic development
- This, in many ways, is a tribute to the architects I’ve had the pleasure of working with.