Agile Software Development
What is Agile?
The first thing we must know about agile which means is a group of methodologies based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams.
- Individual, team interactions over processes and tools.
- Working software over comprehensive documentation.
- Customer collaboration over contract negotiation.
- Responding to changes than following a plan.
A distributed development project, defined as a group of members actively collaborating on a common software/ systems project separated by Distance, Time Zone and Culture. The interesting thing about this is that people from different cultural and language backgrounds team up and contribute to develop a unified product this helps them understand each other’s needs a little better and provides new perspectives.
There are 12 basic principles of Agile Project Management development approach. These principles are based on the Agile Manifesto.
- Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
- Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
- Deliver working software frequently, from a couple of weeks to a couple of months, with a preference for the shorter timescale.
- Business people and developers must work together daily throughout the project.
- Build projects around motivated individuals. Give them the environment and support they need, then trust them to get the job done.
- The most efficient and effective method of conveying information to and within the development team is face-to-face conversation.
- Working software is the primary measure of progress.
- Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
- Continuous attention to technical excellence and good design enhances agility.
- Simplicity — the art of maximizing the amount of work not done — is essential.
- The best architectures, requirements, and designs emerge from self-organizing teams.
- At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Agile vs Traditional Waterfall Models
The Key Difference between Agile and Waterfall Model:
In the software development process traditionally, they follow the waterfall model. Before going to study the agile methodology, we must know the difference between waterfall model and agile project development method.
|It is Flexibility||It is Structured Software development methodology, sometimes it may be quite rigid.|
|Improving the overall software quality with feedbacks from users or the QA team||Software development is to be completed as one single project, which is then divided into different phases, with each phase appearing only once during the SDLC.|
|It allows the changes for the requirement of project development even after the initial planning has been completed.||Once the project development starts, no chance to changing the development requirements.|
|Highly Collaborative Software development process||Stringently Sequential approach from|
|Testing is typically performed concurrently with programming||Testing” phase comes after the “Build” phase.|
|Focuses on Customer Satisfaction||It is an internal process and does not require the participation of customers.|
|Strictly focuses on the completion of project development||Focuses on ensuring that the developed product satisfies its end customers.|
|Agile model is considered unstructured compared to the waterfall model||Waterfall model are more secure because they are so plan oriented|
|For large project difficult to estimate the development time||All types of project can be estimated and completed.|
|Documentation attends less priority than software development||Documentation is a top priority and upgrade the software with another team.|
In a nutshell, agile is an iterative and an unstructured model that is flexible and provides better solutions for comparatively small projects that focuses on customer satisfaction and development.