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.
- Agile developers wanting to become more disciplined in their approach
- Architects/Architecture Owners wanting to gain an understanding of how modeling fits into disciplined agile techniques
- Product Owners wanting to gain a working knowledge of Agile Modeling techniques
- Increase the chance of agile project success through better project initiation
- Learn how to align your agile team’s strategy with that of your organization, increasing value and improving time to market
- Discover how to streamline your approach to modeling and documentation on agile teams
- Learn how to enhance TDD with just-in-time (JIT) model storming
- Reduce the costs and risks associated with documentation on IT teams
What is Agile Modeling?
- Who is Doing This? Results from Industry
- What are Agile Models?
- What is Agile Model Driven Development (AMDD)?
- Agile Modeling for Project Inception
- Agile Modeling Practices for Construction
- Agile Modeling and Test-Driven Development (TDD)
- Agile Documentation Practices
- AMDD at the Enterprise Level
- Length: One day – 7 hours of classroom time plus breaks.
- Approach: For each major topic in the agenda there will be instruction followed by group work.
Class size: Ideally 10 to 15, although up to 20 if the room allows.
- Classroom requirements: For the students a table layout is preferred. Ideally there should be tables of 4-6 people with sufficient space between them so that students can easily move about the room. For the instructor a screen, projector, and writing space (whiteboards or flip charts).
PrerequisitesAn appreciation of the Disciplined Agile mindset. People who are new to agile, or who need a refresher, should watch the Agile Mindset and Disciplined Agile Mindset videos on the Recorded Presentations page.