apkarthick 's Bookmarks tagged links →  View Popular

AMDD is a critical strategy for scaling agile software
development beyond the small, co-located team approach

Through initial, high-level modeling you can gain the knowledge that you need to guide the project but choose to wait to act on it.

your
goal is
to build
a shared
understanding,
it isn’t
to write
detailed
documentation. 
A
critical
success
factor
is to
use

inclusive modeling techniques which enable

active stakeholder participation.

 

The secret is to keep things simple.  You don’t need to
model a lot of detail, you simply need to model enough

Why does
model
storming
on a JIT
basis
work
much
better
than
trying
to

model
everything
up front? 
First,
like it
or not,
the

requirements
are
going to
change
throughout
the
project. 
Second,
by
waiting
to
analyze
the
details
JIT, you
have
much
more
domain
knowledge
than if
you had
done so
at the
beginning
of a
project. 
For
example,
if a
requirement
is to be
implemented
three
months
into a
project,
if you
explore
the
details
of that
requirement
at that
point
you have
three
months
more
domain
knowledge
than if
you had
done so
at the
beginning
of the
project,
therefore
you can
ask more
intelligent
questions. 
Third,
if
you've
been
delivering
working
software
on a
regular
basis
your
stakeholders
now
have
three
months
worth of
experience
with the
system
that
you've
built. 
In other
words,
they can
give you
better
answers. 
Fourth,

modeling
everything
up front
appears
to
result
in
significant
wastage.

test-driven design (TDD) is the combination
of TFD and refactoring

where your team
will spend the majority of its time,