Table of ContentsWhy use DSDM?The DSDM Development ProcessMust have hadSCRUMDSDMDSDM stood for "Dynamic Systems Development Method", but as the method became widely used in areas that were not just for computing and computing. systems development”, it was decided to remove the acronym. DSDM no longer stands for anything, although the slogan “Driving Strategy, Delivering More” appears often. DSDM was developed to solve common problems encountered by projects such as delivery delays, cost overruns or the final deliverable not being completely fit for purpose. DSDM involves all stakeholders, such as business representatives, throughout an iterative and incremental lifecycle. Why use DSDM? The development results are directly and quickly visible. Since users are actively involved in the development of the system, they are more likely to adopt it and Core functionality is delivered quickly, with more features at regular intervals. Eliminates bureaucracy and breaks down communication barriers between interested parties. With constant user feedback, the system being developed is more likely to meet the requirements. need for which it was ordered. Early indicators of whether the project will work or not, rather than an unpleasant surprise halfway through development. The system is delivered on time and on budget. Ability of users to influence the the direction of the project.The DSDM development processThe 9 principles of DSDM: The entire method is based on nine principles which must all be applied, the first four define the foundations on which DSDM was built and the other five provide the principles basis for the structure of the method. Say no to plagiarism. Get a tailor-made essay on “Why violent video games should not be banned”?Get an original essayActive user involvement is essential. This is the great principle. DSDM teams must be empowered to make decisions. The frequency of goods deliveries is of essential importance. Fitness for commercial purposes is essential for product acceptance. The principle means that the developer does not stay at one point because he wants to create a gold-rimmed solution. Suitability for commercial purposes has a starting point, some technical issues can be deferred. Iterative and incremental development is mandatory. All changes during development are reversible. Requirements are set at a high level. Requests collected during business analysis to determine project scope. These requirements must be clearly defined. Testing is integrated throughout the lifecycle. A collaborative and cooperative attitude of all stakeholders is essential. Must have Should have Could have Couldn't have didn't have this time The reason we use MoSCoW at Atern is that the problem with just saying that If the requirements are high, medium or low importance is that the definitions of those priorities are missing. Using MoSCoW means that the priorities are specific. Specific use of Must, Should, Could, or Won't Have implies the result of failure to comply with this requirement. v Comparison between Scrum framework and DSDM: Scrum is good for building the strength of a team. It enables autonomy, self-direction, immediate feedback and true collaboration. Here are some other benefits that Scrum can bring to a team: SCRUMProvides a conducive environment for happy team members,..