Continuous Architecture in Practice

What we'll do
Bio: Pierre Pureur is an experienced software architect, with extensive innovation and application development background, vast exposure to the financial services industry, broad consulting experience and comprehensive technology infrastructure knowledge. His past roles include serving as Chief Enterprise Architect for a major financial services company, leading large architecture teams, managing large-scale concurrent application development projects and directing innovation initiatives, as well as developing strategies and business plans. He is coauthor of the books "Continuous Architecture in Practice: Scalable Software Architecture in the Age of Agility and DevOps" (2021) and "Continuous Architecture: Sustainable Architecture in an Agile and Cloud-Centric World" (2015) and has published many articles and presented at multiple software architecture conferences on this topic.

Links:

• Blog: https://continuousarchitecture.com/blog/
• Web Site: https://continuousarchitecture.com/
• Twitter: https://twitter.com/PGP60
• Linkedin: https://linkedin.com/in/pierre-pureur

The What & Why of Continuous Architecture
In the two-decade-old conflict between ‘big upfront design’ and ‘emergent architecture', software architects and engineers have often had a hard time finding a meaningful compromise. Continuous Architecture provides them with a proven path. There is almost certainly less value in defining up-front architecture today, but systems still must meet their challenging quality attributes; stakeholders still have complex, conflicting, and overlapping needs; there are still many design tradeoffs to understand and make; and perhaps more than ever, there are crosscutting concerns that need to be addressed to allow a system to meet the needs of its stakeholders. These challenges are the same ones that have always preoccupied software architects and engineers; however, the way that we practice software architecture to meet them in today’s environment needs to change. Agility and DevOps practices are fundamentally altering the way IT professionals are working. The modern approach to software delivery needs architectural work to be performed by more people, in smaller increments, with more focus on early delivery of value, than has often been the case historically. Software architecture may change in how it is practiced, but it is more important now than ever.