Part 1. Customer satisfaction by rapid delivery of useful software
Last time, we reviewed both the TOGAF and Agile worlds. In this second part, we look at a key principle of the Agile Manifesto and what this means for enterprise scale systems.
It’s key is to live the value of agility, first and foremost. Yet, the Agile Manifesto’s 12 principles can be mapped to TOGAF in something like the following ways (amongst a myriad of other ways):
1. Customer satisfaction by rapid delivery of useful software
The difference with TOGAF only comes to the fore when the definition of ‘customer’ is looked at.
In an enterprise architecture exercise, the customer is internal. Indeed, there may be solution or enterprise architects in the interested stakeholder groups. The value realisation may take months to come to fruition, but the agile development of a piece of functionality by the IT capability may be a small section which only delivers its value when the whole jigsaw is in place. This is in itself, valuable! As the business value has already been assessed by the business participants and this is the reason for the development exercise and it may indeed contribute to the exercise as a whole with a monetary value.
To link TOGAF to Agile, we have to be aware that the product owner is usually the solution architect responsible for the delivery of the solution building block in the solution continuum. It is categorically NOT the development manager and may not even be the business owner. The business owner will have delivered their capability requirements to the enterprise architects who will have delivered their prioritised strategy to the solution architects who in turn will have segmented the solution architecture into software components (which deliver capabilities) which they will pull from each team.
This article first appeared in GoadingTheITGeek in April 2012. It was the most visited article with 4,490 readers.