On Sat, Jun 23, 2012 at 8:44 PM, Steve Dalton <[address removed]>
I used to do UML when I did Big-Design-Up-Front waterfall stuff 5-10 years ago - but these days you don't really see them much. They might still have a place in some projects.
Its interesting that you almost seem to imply that UML is mainly associated with waterfall.
It's not that we don't do design in Agile - just not *that* kind of design..... fully automated tested working code is a far better use of time than creating diagrams that's all. Good specs and code that can be linked directly to these specs through tests are the best documentation you can have.
Yes but you do not have that here.
Just my opinion - there are probably others that could explain it much better than I can.
I do not see any problem with the clarity of your explanation of your understanding and perspective.
I also find it sad that so many good practices, badly used, have fallen out of favour, not because the concepts were bad, but simply because too few people did it well, and so the concept got bad press but the herd of useless or mediocre practitioners never do. Some things never change.