882516
DSDM
- About
- Dynamic Systems
Development Method
- DSDM is an organised,
common-sense process focused
on delivering solutions quickly
and effectively
- Focuses on the delivery
of a business solution
rather than team activity
- Relies heavily on prototyping
- Dynamic Systems
Development Method
- Functionality is
categorised according
to importance
- 1. Must Have
- Things that are absolutely essential
and fundamental to the system
- Things that are absolutely essential
and fundamental to the system
- 2. Should Have
- Things that are important for the business solution
- Things that are important for the business solution
- 3. Could Have
- Things that are useful, but can be done without for a short while
- Things that are useful, but can be done without for a short while
- 4. Won't Have
This Time
Around
- Things that can easily wait until later
- Things that can easily wait until later
- Prioritisation is important because
there is not enough time to do
everything, and those things that are
essential must be put before things
that are not
- 1. Must Have
- Advantages
- Users are actively involved in the development of the system
- Results of development are directly and promptly visible
- Basic functionality delivered quickly, more functionality delivered at regular intervals
- Constant feedback from users - more likely to meet needs
- Early indicators of whether project will work or not
- System can be delivered on time and on budget
- Users can affect the project's direction
- Users are actively involved in the development of the system
- Active User
Involvement
- Users must be actively
involved in its development.
Product will therefore be more
useful to them
- Users must be actively
involved in its development.
Product will therefore be more
useful to them
- Team should be able to
make rapid and informed
decisions
- Frequent Releases
- Allows for user input at
crucial stages in the
product's development
- Allows for user input at
crucial stages in the
product's development
- Development
done in iterations
- Allows for frequent
user feedback
- More functionality
added in later iterations
- Allows for frequent
user feedback
- Changes must
be reversible
- Allows for backtracking
if a certain change
does not work out well
- Allows for backtracking
if a certain change
does not work out well
- Requirements
initially defined at
a high level
- Details worked out
during the course of
the development
- Details worked out
during the course of
the development
- Meeting the business
needs is more
important than
technical pefection
- Testing done
continuously throughout
development
- All parties must
collaborate and
cooperate
- 20% / 80%
Rule
- 80% of the solution can be developed in
20% of the time that it would take to
produce the total solution
- Extra 20% done in
later iterations
- 80% of the solution can be developed in
20% of the time that it would take to
produce the total solution
Want to create your own Mind Maps for free with GoConqr? Learn more.