DSDM:Dynamic SystemDevelopment MethodDSDM wasdeveloped in invented 1995 as a response to the lack of discipline in the RapidApplication Development methodology. It was invented to provide more advancedversion of a RAD framework and in hadagile principles was used , although the term “Agile” was not Exactly theformal marker that it is today.It is different fromother 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 –developmentand post development instead of focusing only the development of process. But itbecome complex while focusing on two development phases.
Well some organizationgives priority to choose DSDM because of its close and brief description of anyprocess. System is developed dynamically .DSDM is relay on independent tools. It can be used with fully approachedsuch as structured analysis and object oriented approach.· It isnot like waterfall model where overlap is not possible.
· In whichdesign, analysis and development phase can be overlapped.· DSDMsome time worker work on changing requirements and while other work ondevelopment phase.Life cycle of DSDM:The Pre-Project: In which clients requirements are defined .
Projectbudget completion of project and commitment is ensured. The Project life-cycle: it describes the five different stages of projectdevelopment. Initial two stages are feasibility study and business study arethe sequential .after completion of these stages the system is generatediteratively and incrementally in next functional model iteration, then design andimplantation is done. vFeasibility StudyvBusiness StudyvFunctional Model IterationvDesign and Build Iterationv Implementation Post project: The post-project phase ensures the system operatingeffectively and efficiently.
This is realized by maintenance, enhancements andfixes according to DSDM principles. The maintenance can be viewed as continuingdevelopment based on the iterative and incremental nature of DSDM. Instead offinishing the project in one cycle usually the project can return to theprevious phases or stages so that the previous step and the deliverableproducts can be refined.
Principles of DSDM There areeight principles underpinning DSDM. These principles direct the team in theattitude they must take and the mindset they must adopt in order to deliverconsistently.1. Focuson the business need2. Deliveron time3.
Collaborate4. Nevercompromise quality5. Buildincrementally from firm foundations6. Developiteratively7. Communicatecontinuously and clearly8. Demonstratecontrol Core Techniques of DSDM:v Time boxing: Time boxing is interval to complete any task. It notless than 6 weeks, within 6 weeks project must be completed.
v Moscow: Moscow rules are:v Must havev Should havev Could havev Want to have v Prototyping: Prototypes are to implement criticalfunctionality fist to discover difficulties early in the development process,they also allow having very early deliverables to get user feedbackvTesting:testing is just like testing of system in which all the modules are tested and then passed to Workshop.vWorkshop: Inwhich again discuss the project requirements and discussion of anything changedand required.vModeling:helps visualize a business domain and improve understanding. Produces adiagrammatic representation of specific aspects of the system or business areathat is being developed.vConfiguration management:with multiple deliverables under development at the same time and beingdelivered incrementally at the end of each time-box, the deliverables need tobe well managed towards completion.Scrum: Scrum is a framework within which people canaddress complex adaptive problems, while productively and creatively deliveringproducts of the highest possible value.
Scrum itself is a simple frameworkfor effective team collaboration on complex products. Scrum co-creatorsKen Schwaber and Jeff Sutherland have written The Scrum Guide to explain Scrum clearly and succinctly. ThisGuide contains the definition of Scrum. This definition consists of Scrum’sroles, events, artifacts, and the rules that bind them together. · ProductOwner: The ProductOwner should be a person with vision, authority, and availability. The ProductOwner is responsible for continuously communicating the vision and prioritiesto the development team.
· ScrumMaster: The Scrum Masteracts as a facilitator for the Product Owner and the team. The Scrum Master doesnot manage the team. The Scrum Master works to remove any impediments that areobstructing the team from achieving its sprint goals..
· Team: According to Scrum’s founder, “the teamis utterly self managing.” The development team is responsible for selforganizing to complete work. A Scrum development team contains about sevenfully dedicated members (officially 3-9), ideally in one team room protectedfrom 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
