>That time was mostly wasted as I've never used any of it and never met anyone who has used it. So here's the conflict: if we agree that planning is good, comm

>That time was mostly wasted as I've never used any of it and never met anyone who has used it. So here's the conflict: if we agree that planning is good, communication is good, and that it is faster / cheaper to design before we build rather than rushing in to build something, then is it not a good idea to have something like UML in our tool kit? Perhaps UML was too complicated or overbearing, but I've always felt like a universal tool to describe aspects of the software we are building is fundamentally a good concept. Further, it feels like the right idea to document / designing up front in a way that increases buy-in and communicates what we are doing. So if not UML, then what?