Examples of the Agile methodology

Agile methodology is an adaptable and collaborative project management approach that prioritizes iterative development and customer focus, empowering teams to swiftly adapt to changing requirements and deliver valuable outcomes.

Note: To learn about the basics of Agile, check out the following Educative Answer: What is Agile?

In this Answer, we will discuss examples that depict the working of the Agile methodology in real-world scenarios.

Example 1: Flyover construction

Imagine we’re in charge of a significant traffic congestion alleviation project at an important junction in a large city. To enhance traffic flow, the project temporarily changed the road configuration. Can we detail the procedures involved in our strategy and list the benefits of implementing such modifications for the building process and the daily lives of commuters in the area?

Traditional approach

• Step 1: We build two-way temporary roads adjacent to the main junction for traffic flow.

• Step 2: We begin the construction on the flyover from both directions.

• Step 3: After about 18 months of construction, we remove the temporary road and make the two-way flyover available for traffic dispersion.

The solution above takes a lot of time to construct a two-way flyover to reduce the traffic flow on the crossroad. This can be made optimal using the Agile-based approach.

Agile approach

• Step 1: We construct a temporary road for one-way traffic flow.

• Step 2: We build a one-way flyover. Meanwhile, the temporary road serves to reroute that traffic.

• Step 3 After completing the one-way flyover construction, it is now open for two-way traffic, significantly improving the previous traffic conditions without any flyovers. Commuters—the end customers—experience the benefits of this incremental delivery.

• Step 4: The temporary road continues to be utilized in conjunction with the original road, and the construction begins on the flyover for the second direction.

• Step 5: The construction of the second-direction flyover concludes.

The incremental delivery approach significantly accelerates the project completion, enabling customers to access the flyover within nine months. This substantially reduces the originally estimated timeline, even accounting for anticipated delays.

Key benefits

• The one-way flyover is completed in nine months, showcasing exceptional efficiency.

• We introduce a divider on the flyover to facilitate two-way traffic, effectively mitigating cross-road congestion.

• Although traffic flow at the junction remains somewhat sluggish during peak hours, there is a noticeable improvement.

• Implementing two-way traffic on the flyover eliminates the necessity for constructing a temporary road.

• The construction of the second flyover proceeds without undue pressure, thanks to the already operational first flyover, significantly streamlining the process.

• End users can benefit from the flyover in half the originally projected time frame, gaining access within just nine months instead of the initial estimate of 18 months.

Example 2: Software application

The target timeline for the project’s completion and launch is ten months from now.

Traditional approach

In a broad overview of the project, the allocated time for various phases would be distributed as follows:

• 15% for requirements gathering and analysis (equivalent to 1.5 months)

• 20% for design (equivalent to 2 months)

• 40% for coding and unit testing (equivalent to 4 months)

• 20% for system and integration testing (equivalent to 2 months)

Additionally, toward the project’s conclusion, there is a provision for two weeks dedicated to user-acceptance testing conducted by the marketing teams.

It’s important to note that with this approach, the final product remains concealed from the customer until the project’s conclusion, limiting the ability to implement significant changes at that stage.

Project schedule

The image below depicts the project timeline.

Agile approach

The traditional approach allocates fixed percentages to distinct phases such as requirements gathering, design, coding, and testing. This structured allocation reflects a predetermined, linear progression, emphasizing the completion of each phase before advancing to the next — characteristics synonymous with the waterfall methodology. The decision to follow the waterfall model in this scenario is driven by the understanding that the requirements for the interactive user website are thoroughly known and not anticipated to undergo significant changes. Therefore, the traditional approach aligns with the principles of the waterfall model, providing a systematic and step-by-step framework that suits the project’s predictability and well-defined nature.

The following illustration shows the project schedule using the waterfall method in an agile environment.

1. Iterations in the Agile methodology: Agile breaks down projects into manageable segments called Iterations. These iterations are time-boxed, meaning they have a fixed duration, typically 2 to 8 weeks. This time-boxing ensures that the team works on a specific set of tasks within a defined period.

2. Delivery at the end of each iteration: After each iteration, the Agile team delivers a functional product or increment of the project. This means that even after a short period, a tangible result can be reviewed and adjusted if necessary.

3. Organizing projects into releases: Agile planning often involves dividing a project into multiple releases. For instance, if each iteration lasts around four weeks, a project might be divided into approximately ten releases. This approach allows for frequent assessment and adaptation of the project’s direction.

4. Prioritizing core features: Rather than dedicating a significant amount of time (e.g., 1.5 months) to gathering requirements, Agile encourages the team to identify and prioritize core features. During the initial iteration, the team decides which features can be developed, focusing on delivering value early in the project.

5. Handling unfinished features: Agile acknowledges that not all features can be completed in a single iteration. Features that can’t be accommodated in the current iteration are prioritized and scheduled for future iterations. This adaptive approach ensures that the most important features are addressed first.

6. Incremental enhancement: At the end of each iteration, the team delivers a functional version of the website. This working software is enhanced incrementally with features specifically chosen for that iteration. Over time, the software evolves, and each iteration adds value to the product, ultimately leading to the desired result.

Conclusion

The agile approach is a powerful tool for teams, enabling them to consistently produce tangible results. By dividing projects into manageable iterations, focusing on essential features, and addressing any outstanding tasks in subsequent cycles, Agile offers a flexible and adaptable path to project success. This methodology promotes swift adaptation to evolving requirements and ensures stakeholders witness tangible progress at the end of each iteration, ultimately facilitating the efficient delivery of top-notch software products.