The IT industry is either taking giant leaps ahead or it's in deep turmoil. On the one hand we're pushing forward, reinventing the way that we build software and striving for craftsmanship at every turn. On the other though, we're continually forgetting the good of the past and software teams are still screwing up on an alarmingly regular basis.
Software architecture plays a pivotal role in the delivery of successful software yet it's frustratingly neglected by many teams. Whether performed by one person or shared amongst the team, the architecture role exists on even the most agile of teams yet the balance of up front and evolutionary thinking often reflects aspiration rather than reality.
If we really do want to succeed, we need to get over our fascination with shiny new things and starting asking some questions. Does agile need architecture or does architecture actually need agile? Have we forgotten more about good software design than we've learnt in recent years? Is emergent design really just about foolishly hoping for the best? Does any of this matter if we're not fostering the software architects of tomorrow? How do we move from frustration to serenity?
YOU MAY ALSO LIKE:
- The lost art of software design (SkillsCast recorded in December 2019)
- Invitation to Systems Thinking with Jessica Kerr and Kent Beck (Online Course on 21st - 23rd June 2021)
- Domain Models in Practice with Marco Heimeshoff (Online Course on 9th - 13th August 2021)
- CloudNative eXchange Forum 2021 (Online Conference on 21st - 23rd June 2021)
- The Study of Enterprise Agility Community: Global Enterprise Agility Month — Leadership and Strategy Week (Online Conference on 6th - 8th July 2021)
- Product Elevation June (Online Meetup on 22nd June 2021)
- Product Elevation July (Online Meetup on 27th July 2021)
- Test Lead in an Agile Transformation (SkillsCast recorded in June 2021)
- Managing Commercial Platforms: The Architect’s Emerging Skill (SkillsCast recorded in June 2021)