Agile

What is Agile?

Agile is a project management style that applies a cross-functional approach throughout the software development lifecycle (SDLC). Involving multiple methodologies, Agile describes a set of values and principles for software development under which requirements and solutions evolve through the collaborative effort of self-organizing cross-functional teams.

The Manifesto for Agile Software Development describes the central values and principles applied in an Agile approach. It is a popular evolution of more traditional project management styles, such as the waterfall model. It emphasizes cross-functional teams, communication, collaboration, and self-accountability rather than siloed, progressive teams. Agile allows teams to quickly and proactively respond to changes and problems. Two of the most popular Agile approaches adopted are Xp (eXtreme Programming) and Scrum.

Why Agile? 

• Customer satisfaction by rapid, continuous delivery of useful software.
• People and interactions are prioritised over processes and tools. Customers, developers and testers constantly interact with each other.
• Working software is delivered frequently.
• Close, daily cooperation between businesspeople and developers.
• Continuous attention is paid to technical excellence and good design.
• Developers regularly adapt to changing circumstances.
• Even late changes in requirements are welcomed.

12 Principles of Agile 

The following 12 Principles are based on the Agile Manifesto. 

1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. 

2. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage. 

3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. 

4. Businesspeople and developers must work together daily throughout the project. 

5. Build projects around motivated individuals. Give them the environment and support they need and trust them to get the job done. 

6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. 

7. Working software is the primary measure of progress. 

8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. 

9. Continuous attention to technical excellence and good design enhances agility. 

10.  Simplicity–the art of maximizing the amount of work not done–is essential. 

11. The best architectures, requirements, and designs emerge from self-organizing teams. 

12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly. 

Best Practices of Agile 

• Agile advocates that entire teams should function like closely integrated units. This includes teams like project management, developers, quality assurance, and the customer.
• The functioning method involves conducting daily meetings so as to decide on the day’s work and dependencies. This is because constant communication is considered as one of the most important factors essential to team integration.
• The typical delivery cycle ranges from two to four weeks. This implies that deliveries are short-term. They are commonly called 'sprints.' Sprint is a scrum terminology. Scrum is the most popular agile framework. Its approach entails assembling the project’s requirements and using them to define the project. The necessary sprints are then plannedplanned, and each sprint is sorted into its own list of requirements.
• One of the most important principles relates to regularly inspecting and adapting at the end of each sprint. This means that the team inspects its own practices and then decides as to what to change and how to adapt to the change.
• Teams that follow agile management principles typically tend to have open communication tools, which enable team members and customers to put forth their suggestions and feedback openly and quickly. These remarks are considered and incorporated when shaping the requirements and implementing the product.