So I've been toying with the idea of doing software architecture in an "agile" or "lean" way. Sounds like a great way to spend a week in mad 'dicussions' with various people about the semantics of architecture and solution design and how little of it you should really do in order to be "lean".
Excuse the puns for the moment, but I have come across a number of cases of differing case for differing purposes in the case of software development.
This, therefore, is a case study of the true meaning of the term. Just in case you needed to know. So why not write about it.
Now the other day I had a colleague of mine refer to the need to get "out" of the development industry (software development, that is) because of a variety of reasons, mostly centred around the need to report through the artificial introduction of agile, scrum, lean, whateveryoucallit methodologies.
Whilst I don't want to discuss the merits and pitfalls of said methods (it could go to great lengths), no the purpose of this blog is something a little more personal.