Agile methods, Dynamic System Development Method

• Each phase of the Spiral Model is divided into four quadrants as shown in the
above figure. The functions of these four quadrants are discussed below:

1.Objectives determination and identify alternative solutions: Requirements are

gathered from the customers and the objectives are identified, elaborated, and analyzed
at the start of every phase. Then alternative solutions possible for the phase are
proposed in this quadrant.

2.Identify and resolve Risks: During the second quadrant, all the possible solutions are
evaluated to select the best possible solution. Then the risks associated with that
solution are identified and the risks are resolved using the best possible strategy. At the
end of this quadrant, the Prototype is built for the best possible solution.

3.Develop the next version of the Product: During the third quadrant, the identified
features are developed and verified through testing. At the end of the third quadrant,
the next version of the software is available.

4.Review and plan for the next Phase: In the fourth quadrant, the Customers evaluate
the so-far developed version of the software. In the end, planning for the next phase is
started.
Agile Software Development Methodology

• Agile Software Development Methodology is a process of software development similar to other software
development methodologies like waterfall models, V-models, iterative models, etc. Agile methodology
follows the iterative as well as incremental approach that emphasizes the importance of delivering of
working product very quickly.
• In English, Agile means ‘the ability to move quickly and easily’ and respond to change rapidly this is an
important aspect of Agile software development.

• Agile methodologies are iterative and incremental, which means they’re

known for breaking a project into smaller parts and adjusting to changing
requirements.
1.They prioritize flexibility, collaboration, and customer satisfaction.

2.Major companies like Facebook, Google, and Amazon use Agile because of its
adaptability and customer-focused approach.
Types of Agile Methodology

• Following are the types of Agile methodology:

1.Kanban
2.Scrum
3.Lean
4.DSDM or Dynamic Systems Development Method ·
5.XP or Extreme Programming
6.FDD or Feature Driven Development
7.Crystal
8.Scaled Agile Framework (SAFe)
• The Agile methodology is a popular approach to software development that emphasizes flexibility, collaboration, and customer
satisfaction. It breaks projects into smaller, manageable parts, allowing teams to get customer feedback and make iterative
changes quickly. Here are some key advantages of the Agile model:
• Focus on Customer Value
• Agile prioritizes delivering value to customers by addressing their requirements and preferences. By breaking down work into
small tasks, Agile ensures that the most important features are developed first and iterative changes are driven by customer
feedback1.
• Enhanced Team Morale and Motivation
• Agile empowers teams to own their work and make decisions collectively. This autonomy, combined with a focus on delivering
value and continuous improvement, boosts team morale and motivation1.
• Stakeholder Collaboration
• Agile promotes strong coordination between product owners, developers, and other stakeholders throughout the development
process. This collaboration fosters better communication, a shared understanding of objectives, and continuous feedback, leading
to higher quality results and increased stakeholder satisfaction1.
• Early and Continuous Delivery
• Agile encourages small, incremental releases of functional software. This provides early access to visible progress and facilitates
early feedback and validation from stakeholders. Continuous delivery helps identify and address issues early, reducing risks1.
• Delivering High-Quality Software
• Agile emphasizes delivering high-quality software through techniques like continuous integration, automated testing, and frequent
inspection and adaptation. By integrating quality assurance throughout the development process, Agile ensures that the software
meets the required standards and reduces the likelihood of defects1.
• Increased Employee Input
• Agile fosters a culture where employees have more input and ownership over their work. This leads to higher job satisfaction and a
sense of purpose, as developers feel more connected to the end customers and their needs2.
• Faster Fixes and Solutions
• Agile allows for quicker identification and resolution of issues. If a customer is struggling with a feature, Agile teams can
implement a fix and deliver it within a short timeframe, enhancing customer satisfaction2.
• More Cross-Functional Collaboration
• Agile encourages cross-functional teams with diverse expertise to work together on projects. This reduces delays
caused by handing off tasks between different departments and ensures that all aspects of the project are addressed
simultaneously2.
• Better Risk Management
• Agile's iterative approach helps manage risks by delivering small increments of functional software and getting
feedback early. This reduces the chances of working on features that may not meet customer expectations2.
• Increased Room to Pivot and Experiment
• Agile provides the flexibility to adapt to changing customer needs and market conditions. Teams can experiment with
new ideas and pivot quickly based on feedback, fostering a culture of innovation2.
• Customized Company Solutions
• Agile allows organizations to tailor their processes to fit their specific needs and goals. This customization ensures that
Agile practices align with the company's unique requirements and challenges2.
• Decentralized Communication
• Agile promotes decentralized communication, where team members from different departments collaborate directly.
This improves efficiency and reduces the need for extensive documentation and approval processes2.
• Bigger Focus on Relationships
• Agile emphasizes the importance of relationships over processes. By prioritizing communication and collaboration,
Agile teams build stronger relationships with stakeholders and create a more cohesive work environment2.
Dynamic Systems Development
technique (DSDM)
• The Dynamic Systems Development technique (DSDM) is an
associate degree agile code development approach that provides
a framework for building and maintaining systems. The DSDM
philosophy is borrowed from a modified version of the sociologist
principle—80 % of An application is often delivered in twenty
percent of the time it’d desire deliver the entire (100 percent)
application.
• DSDM is An iterative code method within which every iteration
follows the 80% rule that simply enough work is needed for every
increment to facilitate movement to the following increment. The
remaining detail is often completed later once a lot of business
necessities are noted or changes are requested and
accommodated.
•The DSDM tool (www.dsdm.org) could be a worldwide cluster of member companies that put together tackle
the role of “keeper” of the strategy. The pool has outlined AN Agile Development Model, known as the DSDM
life cycle that defines 3 different unvarying cycles, preceded by 2 further life cycle activities:
1.Feasibility Study:
It establishes the essential business necessities and constraints related to the applying to be designed then
assesses whether or not the application could be a viable candidate for the DSDM method.
2.Business Study:
It establishes the use and knowledge necessities that may permit the applying to supply business value;
additionally, it is the essential application design and identifies the maintainability necessities for the
applying.
3.Functional Model Iteration:
It produces a collection of progressive prototypes that demonstrate practicality for the client.
(Note: All DSDM prototypes are supposed to evolve into the deliverable application.) The intent throughout
this unvarying cycle is to collect further necessities by eliciting feedback from users as they exercise the
paradigm.
4.Design and Build Iteration:
It revisits prototypes designed throughout useful model iteration to make sure that everyone has been
designed during a manner that may alter it to supply operational business price for finish users. In some
cases, useful model iteration and style and build iteration occur at the same time.
5.Implementation:
It places the newest code increment (an “operationalized” prototype) into the operational surroundings. It
ought to be noted that:
1.(a) the increment might not 100% complete or,
2.(b) changes are also requested because the increment is placed into place. In either case, DSDM
development work continues by returning to the useful model iteration activity.