DSDM: of project and commitment is ensured. The Project

DSDM:
Dynamic System
Development Method

DSDM was
developed in invented 1995 as a response to the lack of discipline in the Rapid
Application Development methodology. It was invented to provide more advanced
version of a RAD framework and in  had
agile principles was used , although the term “Agile” was not Exactly the
formal marker that it is today.

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

It is different from
other agile method because of its reporting format and techniques tracking requirements.
But it is least preferred method as compare to agile. DSDM mainly focus on pre –development
and post development instead of focusing only the development of process. But it
become complex while focusing on two development phases. Well some organization
gives priority to choose DSDM because of its close and brief description of any
process. System is developed dynamically .DSDM is relay on independent tools. It can be used with fully approached
such as structured analysis and object oriented approach.

·       
It is
not like waterfall model where overlap is not possible.

·       
In which
design, analysis and development phase can be overlapped.

·       
DSDM
some time worker work on changing requirements and while other work on
development phase.

Life cycle of DSDM:

The Pre-Project: In which clients requirements are defined .Project
budget completion of project and commitment is ensured.

The Project life-cycle: it describes the five different stages of project
development. Initial two stages are feasibility study and business study are
the sequential .after completion of these stages the system is generated
iteratively and incrementally in next functional model iteration, then design and
implantation is done.

v
Feasibility Study

v
Business Study

v
Functional Model Iteration

v
Design and Build Iteration

v  Implementation

 Post project: The post-project phase ensures the system operating
effectively and efficiently. This is realized by maintenance, enhancements and
fixes according to DSDM principles. The maintenance can be viewed as continuing
development based on the iterative and incremental nature of DSDM. Instead of
finishing the project in one cycle usually the project can return to the
previous phases or stages so that the previous step and the deliverable
products can be refined.

 

Principles of DSDM

There are
eight principles underpinning DSDM. These principles direct the team in the
attitude they must take and the mindset they must adopt in order to deliver
consistently.

1.   Focus
on the business need

2.   Deliver
on time

3.   Collaborate

4.   Never
compromise quality

5.   Build
incrementally from firm foundations

6.   Develop
iteratively

7.   Communicate
continuously and clearly

8.   Demonstrate
control

 

 

 

Core Techniques of DSDM:

v Time boxing: Time boxing is interval to complete any task. It not
less than 6 weeks, within 6 weeks project must be completed.

v Moscow:

             Moscow rules are:

v Must have

v Should have

v Could have

v Want to have

      

                                    

 

v Prototyping: Prototypes are to implement critical
functionality fist to discover difficulties early in the development process,
they also allow having very early deliverables to get user feedback

v
Testing:
testing is just like testing of system in which all the modules are tested  and then passed to Workshop.

v
Workshop: In
which again discuss the project requirements and discussion of anything changed
and required.

v
Modeling:
helps visualize a business domain and improve understanding. Produces a
diagrammatic representation of specific aspects of the system or business area
that is being developed.

v
Configuration management:
with multiple deliverables under development at the same time and being
delivered incrementally at the end of each time-box, the deliverables need to
be well managed towards completion.

Scrum: Scrum is a framework within which people can
address complex adaptive problems, while productively and creatively delivering
products of the highest possible value.

Scrum itself is a simple framework
for effective team collaboration on complex products.  Scrum co-creators
Ken Schwaber and Jeff Sutherland have written The Scrum Guide to explain Scrum clearly and succinctly.  This
Guide contains the definition of Scrum. This definition consists of Scrum’s
roles, events, artifacts, and the rules that bind them together. 

·        
Product
Owner: The Product
Owner should be a person with vision, authority, and availability. The Product
Owner is responsible for continuously communicating the vision and priorities
to the development team.

·        
Scrum
Master: The Scrum Master
acts as a facilitator for the Product Owner and the team. The Scrum Master does
not manage the team. The Scrum Master works to remove any impediments that are
obstructing the team from achieving its sprint goals..

·        
Team: According to Scrum’s founder, “the team
is utterly self managing.” The development team is responsible for self
organizing to complete work. A Scrum development team contains about seven
fully dedicated members (officially 3-9), ideally in one team room protected
from outside distractions.

                          DSDM

                   SCRUM

·       
In DSDM,
development work is termed the ‘engineering activity’ and the output of each
iteration is called the ’emerging solution.
·       
The DSDM guidance does advise that any ‘definition
of done’ work upfront during the Foundations phase should be reviewed
regularly throughout the project lifecycle.
·       
DSDM
originally sought to provide some application to the rapid application
development method.
·       
Simple
and extendable
·       
Project
based
·       
Robust
scalable ,governable agile
 

·       
In Scrum
the output is termed a ‘potentially releasable increment.
 
 
·       
In Scrum an increment is described as “Done” when
it meets a “Definition of Done” for the Scrum Team. 
 
·       
It is an iterative software development model used to manage complex
software and product development.
 
·       
Difficult
to master
·       
Team
focused
·       
Light
empirical agile
 
 

 

 

x

Hi!
I'm Santiago!

Would you like to get a custom essay? How about receiving a customized one?

Check it out