UML diagrams
Can you use diagrams in Scrum? Could it be useful or simply not allowed? Where is this defined in Scrum?
Scrum does not specify methodologies or technology to develop great software. Neither how you are supposed to design and/or document your software. It is up to your scrum team. :)
I like, as an example, when I see my teams using UML diagrams to clarify their ideas and find common sense. Used that way increases transparency.
+1
Scrum does not prescribe a particular method of technique. Teams are free to choose the ones that work well for them. I had been in teams that used uml heavily to communicate design and ideas and also in teams that almost had no clue about UML. And all these teams still were able to deliver.
Take 2 UML and call me in the morning :). Seriously, this the beauty of Scrum. Within the transparency, inspection and adaptation of an empirical process framework, you have complete freedom to try out whatever you want!
Take a moment to revel in the freedom and creative liberty....ahhhhh!
Use this freedom to encourage developers to scratch their itch for UML. The Scrum Master should be faithful to observe the effect of the new activity and measure it's effect. During the retrospective, the effect is examined and found to be helpful, neutral, or a hindrance. The developers decide to continue, adapt, or jettison the new practice. What an ecstasy of self-actualization!
If UML is being foisted on the developers, the SM should step in. He/she should look to the source of the well-intentioned if misguided request and search for the objective or goal of the request. If necessary, he/she should consider taking the accountability on him/herself and ask the team to satisfy the need in their own way. This is the SM being the heat shield for the team. If the UML ask is harmful interaction with the team, the SM coaches the asker, teaches why the ask is harmful, or ultimately says (in the voice of Gandalf) "You shall not pass!!"
Does that help?
Go to this scrum.org page and scroll to the bottom. You will see an example of a diagram being used.
http://courses.scrum.org/classes/show/3418
A couple of things to note:
- The diagram isn't UML, but it could have been. Perhaps in this case UML was unnecessary.
- The diagram provided context for a value-generating time-bound activity which has now been completed.