2.2.2. Agile Model

An iterative and incremental model where development is broken into sprints (usually 1–4 weeks), promoting flexibility, collaboration, and continuous delivery.

The Agile Model is designed to be flexible and adaptive to change. Unlike traditional models like Waterfall, Agile organizes work into short cycles called sprints, which typically last between one to four weeks. This allows development teams to adjust quickly based on feedback and changing requirements.

Imagine a chef who is preparing a new dish. Instead of planning out the entire menu and making it all at once, the chef prepares a small plate first (a sprint) to taste and adjust the flavors based on feedback from guests. After each plate, the chef can make adjustments before serving the final dish, ensuring it meets the guests' preferences.

Sprint activities include:

• Sprint Planning: Define user stories and sprint goals
• Development & QA: Dev and QA work in parallel during the sprint
• Daily Stand-up: Share progress and blockers
• Sprint Review: Demonstrate completed features
• Retrospective: Reflect on what went well and what can improve

In the Agile Model, each sprint consists of several key activities. During Sprint Planning, the team outlines what they aim to achieve. Development and QA work concurrently rather than sequentially, which fosters collaboration. Daily stand-up meetings help the team track progress and discuss challenges. At the end of the sprint, a Sprint Review is held to showcase the completed work, followed by a Retrospective to evaluate the process and identify areas for improvement.

Think of a basketball team practicing for a game. They plan their practice session (Sprint Planning), train together (Development & QA), have quick huddles to discuss what's working or what's not (Daily Stand-up), demonstrate their plays during scrimmages (Sprint Review), and then analyze their performance to improve for the next game (Retrospective).

QA is involved from the beginning of each sprint:

• Writes test cases alongside user stories
• Performs continuous testing (manual or automated)
• Participates in backlog grooming, reviews, and retrospectives

In Agile, Quality Assurance (QA) is an integral part of the process from the start of each sprint. This means QA writes test cases at the same time as user stories are created, ensuring that quality is built in from the ground up. Continuous testing occurs throughout the sprint, allowing for quick identification and resolution of defects. Furthermore, QA is involved in the planning processes, which helps clarify requirements and ensure that testing aligns with user needs.

Consider an architect working on a new building. Instead of waiting until the building is completed to check for issues, the architect collaborates with engineers throughout the construction process, checking for design and structural flaws as each part is built. This approach saves time and resources by catching problems early.

• Pros: Early and continuous QA involvement, faster feedback, better defect prevention
• Cons: Requires high collaboration and adaptability

The Agile Model offers several advantages, particularly in terms of QA involvement and responsiveness to feedback. Early and continuous involvement from QA leads to a lower number of defects in the final product. Additionally, the rapid feedback loops allow teams to make necessary changes quickly. However, Agile also has its drawbacks. It demands a high level of collaboration and adaptability among team members, which can be challenging in some work environments.

Think of a sports team that practices regularly and adjusts strategies based on the opponent's play. While this approach can lead to victory and improvement, it requires that all members work well together and adapt to changing game situations. If one player struggles to communicate or adapt, it can impact the whole team’s performance.

--