We'll be glad to discuss, please drop us an email.
Everyone involved in software development agrees that architecture is highly important, yet, we try to create it when we have the least understanding of the applications or systems we build. Evolving architecture has risks, but creating one up-front architecture has its own perils. In this class we will discuss the why and how of evolving architecture. We will start with a quick discussion on the reasons and risk. Then we will dive into discussing the principles and practices that can help us to evolve the architectures we create. We will conclude with some recommendations for the approaches we can take.
Dr. Venkat Subramaniam is an award-winning author, founder of Agile Developer, Inc., creator of agilelearner.com, co-founder of the devdotnext software conference, and an instructional professor at the University of Houston.
He has trained and mentored thousands of software developers in the US, Canada, Europe, and Asia, and is a regularly-invited speaker at several international conferences. Venkat helps his clients effectively apply and succeed with sustainable agile practices on their software projects.
Venkat is a (co)author of multiple technical books, including the 2007 Jolt Productivity award winning book Practices of an Agile Developer. You can find a list of his books at agiledeveloper.com. You can reach him by email at email@example.com or on twitter at @venkat_s.
- Reasons to evolve architecture
- Risks of evolving
- Principles and practices to facilitate evolution
- Approaches to evolve architecture
- Monitoring and governance of architecture
- Clearly understand and articulate the reasons to evolve architecture
- Know the benefits and risks of evolving architecture
- Tackle and alleviate issues of evolving architecture
- Apply useful and practical principles to evolve architecture
- Manage and actively govern the evolution of architecture
Programmers, architects, team leaders, technical managers
- Pencil/Pen, Paper to draw
- Git Client