Class

Description

Agile has long shunned up-front design. When Agilists force themselves to do up-front work, it usually is limited to a symbolic use of User Stories for requirements and metaphor for architecture, with much of the rest left to refactoring.

Experience and formal studies have shown that incremental approaches to architecture can possibly lead to poor structure in the long term. This course shows how to use domain analysis in a Lean way to build an architecture of form that avoids the mass of structure that usually accompanies big up-front design, using only judicious documentation.

The course will guide you specifically how to fit architectural planning into your Scrum framework. While these principles apply broadly to any Agile development shop, we will go into Scrum specifics according to the interest of the attendees. Build on what has been proven to work instead of figuring it out yourself! (For a teaser, see: http://www.leansoftwarearchitecture.com/home/engaging-the-stakeholders)

It will also show how architecture can accommodate incremental addition of features using Trygve Reenskaug’s new DCI (Data, Context and Interaction) approach, and how it maps elegantly onto C++ implementations.

The course is based on the Wiley book of the same title (http://eu.wiley.com/WileyCDA/WileyTitle/productCd-0470684208.html).

  You will be redirected to www.trifork.dk