Re: SCRUM & UML
- A pair of ponderings on about UML:
IMHO, UML is a useful way of communicating about software when you want
to be just a little bit more specific in your communication than
undefined-semantics-boxes-and-arrows scribbles (also very useful of
Worrying about it feels a bit like some maths guys worrying about
whether to use the "f'(x)" or "df(x)/dx" notation for derivatives; who
cares as long as everyone understands it?
Again only an opinion, but I think UML *notation* has two distinct uses:
(1) to notate UML *models* (which are abstract entities for which the
different UML diagram types represent views) and (2) to help software
people talk about software.
Unless you are doing (1), where the diagrams need to be "correct and
complete" for the underlying model to be consistent and complete, using
"correct and complete" UML is a bit like putting serifs on characters
when you draw them by hand.
I've never heard of anyone doing UML modelling in an agile context
(mostly because we don't live in a world where the tools are good enough
that a UML model is just an alternative to code). A lot of teams I've
seen use it (to whatever degree of detail/correctness is appropriate at
that instant) to talk to each other about software though...
> I'm implementing Scrum for the first time and we're going to try to
> incorporate UML notation with it. I know in reading the Scrum
> resources that it's best to have the team determine what artifacts
> will guide them in their development effort. To always remember that
> when we're documented to answer the question, "How is this helping us
> code?" But my issue is how do I move forward? In my first sprint,
> I've been asked, "What should the developers be doing while the BA's
> are writing Use Cases?" I have responded by saying that the
> developer should be working right alongside the BA's and coding while
> the Use Cases are being documented. Is this the correct approach??
> Does anyone have some advice for me in moving forward? I'm starting
> to feel that maybe we should spend more time upfront with Use Case
> modeling, writing Use Cases and specs, but then I feel that's not
> being very agile.
- Hi ----,
I do have four Scrum Teams runningn in sync and we will using MDSD in
> not yet worked with a Scrum team that used UML in a ModelSo I hope I will be able to answer this question in future with more insight.
> Driven Architecture context to generate code from UML models,
> but I'm very interested if anyone has done so.
What I will try to find out ist to see in which way we will be able to
build an "incremental" archtitecture that emerges by using MDSD and
the tools for this.