By this point in the architecture-cycle, we would hope to have achieved something. But what did we achieve? With what benefits, and for whom? What can we learn from what we’ve done? And what should we do next?
So we here return to architecture-governance to do a “lessons-learned” review – a Retrospective, in Agile terms – in relation to the respective business context, and identify any needs for further related architecture work.
In a conventional large architecture-project, this would be a major phase ...