What an Architect Can Learn from Retrospective Failures
Please log in to watch this conference skillscast.
Based on 15 years of experience with facilitating retrospectives for software developers, I have described the most common challenges in antipatterns.
Antipatterns are like patterns, just more informative in that you first learn what the immediate bad solution is before you get a better solution. Alongside the retrospectives I have facilitated architecture reviews and there are a lot of similarities between these two activities. Both include a shared experience that needs to be reflected on, both include people with pride and shame in what has been created, and both are under the usual time and resource constraints. Join me for a sad and entertaining talk about how your architecture review sessions can improve based on all my mistakes.
YOU MAY ALSO LIKE:
- Retrospectives Antipatterns — Team Meetings That Don't Suck (SkillsCast recorded in July 2020)
- Microservices Architecture with Jorge Ortiz‑Fuentes (Online Course on 15th - 17th February 2021)
- Sociotechnical Domain-Driven Design with Kacper Gunia (Online Course on 18th - 19th February 2021)
- μCon: The Microservices eXchange (Online Conference on 13th - 14th April 2021)
- Evolutionary Architecture (SkillsCast recorded in January 2021)
- Event-Driven Microservices: The Sense, Nonsense and a Way Forward (SkillsCast recorded in December 2020)
Thank you to our sponsors and partners
Platinum
Gold
What an Architect Can Learn from Retrospective Failures
Aino Vonge Corry
Aino Vonge Corry is a teacher, a technical conference editor and retrospectives facilitator. She holds a masters degree and a PhD in computer science. She has 12 years of experience with patterns in software development, and 10 years' experience with facilitation of retrospectives.