DA 102: Introduction to Agile Model Driven Development (AMDD)
Have you noticed that teams who are new to agile, and particularly those that have adopted Scrum, tend to get into trouble five or six sprints/iterations into Construction? They discover that they've coded themselves down an architectural path that just doesn't get the job done, and now they need to do a fair bit of rework to get back on track? They could have avoided that with a bit of up-front, light-weight modelling. Or, have your Scrum teams built something that a subset of your business customers like but when they release into production the actual end-users are underwhelmed with what was delivered? Some agile requirements modelling could have avoided that problem.
Requirements, analysis, architecture, and design are so important to Disciplined Agile (DA) teams that we consider this issues every single day. The trick is to know how much effort to put into these activities, when to do so, and when to stop. Disciplined agilists realize that tests are a much more effective way to specify your requirements and design, yet very poor at high-level thinking. Models on the other hand are very effective for thinking things through and communicating your overall strategy. So let's use models for what they're good for and tests for what they're good for.
The techniques of Agile Model Driven Development (AMDD) present an effective approach to exploring the complex problems faced by agile teams and more importantly determining how to address those problems in a straightforward, evolutionary approach. This hands-on workshop explores the values, principles, and practices upon which AMDD is based.