Extra documentation in SCRUM

Hi Pams,

Scrum does not require any specific documentation, the documentation required is defined by the Scrum Team and its stakeholders/organization.  There is no reason that you cannot use UML diagrams as you suggest, it is not required by Scrum, but can certainly defined by your team and in your Definition of Done.

I would suggest that any required documentation be a part of your Definition of Done and therefore known by all as needed and given a shared agreement to that need a a requirement for the item being delivered.

BTW, Scrum is a framework, not a methodology.  A methodology is highly descriptive as a process and will tell you exactly what is needed whether it makes sense to your team or not, while Scrum provides a framework that allows the Scrum Team to define the process as they continually learn while doing through inspection and adaption. 

What documentation scheme can I leave in a project following SCRUM and also with sequence diagrams and use cases?

What documentation I have to leave in the all project following this methodology?

Have you thought about test documentation, including automated test cases which help assert the quality of each increment as it is delivered?

If Test Driven Development techniques are used, these test cases can also express requirements, promote clear design, and assist in traceability.