Map Software to A3
The A3 website states that there are a number of steps to an A3. These are
The C programmers will appreciate the starting count.
An Example
Ok so all that may or may not sound good. So let’s take an example and see how the pieces fit together
We are working on Product X, which will be fantastic, once we know what it is. The Product Team told us this was so. We are going to use agile techniques to create this, but we come from more traditional backgrounds. We want to have a process that is:
- Rigorous, but agile.
- Documented, but flexible.
- Has a lead architect, me, but includes everyone through collaboration
- Is tried and proven
- Allows people’s good ideas to be utilised
- Is UML even Agile?
Note UML is discussed by Craig Larman of LeSS and Dean Leffingwell of SAFe. They both see that is can make a contribution to driving conversations and decisions. So I conclude UML is entirely compatible with Agile as a collaboration tool. Also note Ivar Jacobson and Ian Spence have released Use Case 2.0 to show how this works in an Agile world. In this case it is UML as a communication tool and nbot as a code generation technique. Any other drawing type is encouraged if it provides value. The objective is clarity.
Let’s look at the steps and an A3 template. this one is for example purposes and includes only a few categories of information. the story leader should not feel constrained, but there should be an agreement on what core topics are needed.
Summary
Using Agile; design, test and coding become part of the development activity. This requires continual conversations to ensure all views are considered, and is supported through frequent feedback. Using A3 as a means of recording the key decisions and techniques used creates a complete trail from EPIC -> Feature -> Story -> Task -> Test –> Design and represents a very disciplined and auditable approach to software creation.
Leave a Reply