What do UML diagrams have to do with scrum methodology? [closed]

Question

Closed. This question is opinion-based. It is not currently accepting answers.

---

Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.

Closed 4 years ago.

Improve this question

I'm working on the conception of a project using the scrum (i.e. Agile) methodology, and I wanted to know what UML diagrams do for this kind of methodology.

After doing some research, I found that the use case and sequence diagrams can be useful, but what else? Should I do these diagrams for the whole project, or iteration by iteration?

Answer 1

UML is an object modelling tool to better express different aspects of your product/project to stakeholders like developers , designers, clients etc. It is not much to do with the project management approach. You can follow Agile or normal waterfall model and still use UML.

But as Agile is iterative approach which keep on evolving so it makes sense to keep your UML docs updated to better take care of changes. So your UML diagrams will be created for each iteration. And as project evolves so are your UML diagrams.

Typically UML diagrams which are useful are : Usecase diagram, Class diagram, sequence diagram, activity diagram.