Do you….UML?

UML or not UML….that is the question. At least that is what I’m questioning today.

I believe that good, detailed, functional documentation is important, and UML give us that. Standard, and understandable, documentation on which we can trust (if we use it correctly). But, does UML gets along with agile methodologies?

How much time should I use to create class and use cases diagrams? Better yet…Should I spend time creating them?

Since Sprint Planning focuses on estimating and selecting stories, it doesn’t seem the right moment to do UML diagrams. After that, we need to break down stories into tasks. And after that, well, start developing.

I’ve heard about teams that have a “functional analyst” role, this person creates all the diagrams and documents needed. It’s duty is to design and document. This way developers don’t loose time. But…I’m really not convinced if it’s OK to introduce this role into a Scrum team. Doesn’t this sounds like a non-agile role?