Location visible to members
How often do you get to work on completely isolated systems? It is seemingly more and more common that your system needs to talk to another system to function, whether that be a legacy system, an external API or even one that has not been developed yet. Every system that you talk to adds risk to your project; technical risk, quality risk and delivery risk. But never fear - help is at hand.
Come to this talk and you will hear about how to design your system to decrease this risk, how to ensure the quality of the overall system and how to manage the successful delivery of the system. Not only that, but you will hear real-life cases, some success stories but also many failures and you too can learn from the mistakes I witnessed. Have questions around the integration points in your ecosystem? Fire them up, and lets see if we can work through them together.
Sarah Taraporewalla is a Senior Consultant working for ThoughtWorks, where she specializes in developing robust software for the future, delivered today. She has acted as developer, software architect, technical lead and agile coach at many projects and has spoken at both internal and external conferences and geek nights. Although primarily focused on software design, she also has a lot to say about how software can be developed to accommodate the changing pace of business. Sarah occasionally writes her thoughts down at http://sarahtaraporewalla.com (http://sarahtaraporewalla.com/) , and whinges about the world via @sarahtarap. To learn how to say her name correctly, have a look at http://sarahtaraporewalla.com/uncategorized/how-many-os-in-woolloomooloo/ (http://sarahtaraporewalla.com/uncategorized/how-many-os-in-woolloomooloo/);