Agile Methodologies

Agile method proposes an incremental and iterative approach to software design. The design process is broken into individual models that designers work on. There is no pre-determined course of action or plan with the Agile method.

Development flows incremental and iterative approach with several different stages: Planning, Requirement Analysis, Designing, Building, and Testing. The most popular agile methods include: RUP – Rational Unified Process (1994) and Scrum (1995).

Agile is a development mindset focus on delivering customer value. If you work in Agile, you Mitigate Risk and Involve Customer.

Agile-Scrum:

Scrum is an Agile process that allows focusing on delivering the highest business value in the shortest time. It is considered as lightweight and people-based / skill based rather than plan based.

Agile Scrum produces the highest business value in the shortest time by developing products in Iterative Incremental manner.

Sprints: Each Iteration or short development cycle is called Sprint. Each Sprint typically a few weeks long and involves – Requirements Definition, Product Design, Coding and Testing.

The end result of every Sprint is potentially a shippable product. Each Sprint improves the product more and more incrementally top of each other.

But how long each sprint lasts is something for the team to decide, who must weigh the advantages or disadvantages of a longer or shorter sprint for their specific development environment. The important thing is that a sprint is a consistent duration.

Agile Vision:

  • Backlog Grooming – Managing of the product backlog is called the Backlog Grooming.
  • Product Backlog – Product Backlog outline is the projects Timeline and Priorities.
  • User Story – A requirement to an Agile is called the User Story. Because there focus on work the customer for user needs. They are presented in a canonical form that emphasizes the customers.

How Sprint Works?

  1. Sprint Planning
  2. Daily Stand-up Meeting
  3. End-of-Sprint Review
  4. Retrospective

1. Sprint Planning:

Gathers the team together, including the Scrum Master. Scrum Master attempted to facilitate Scrum planning. He also in-charge of removing any obstacles that prevented the team for doing a work. The first Sprint focus on getting a basic application up and running so that the owner can start making money as soon as possible.

The team reduced the product backlog by priorities backlog and asked the product owner for details user story. They also size the user story in order to determine what’s story are fits into the sprint.

Sprint Backlog: Scrum team moved the high priority stories from the product backlog into the Sprint Backlog. Sprint backlog defines the scope of Sprint1. The team determines that they can work on four high priority stories. For example – creating a website, developing description pages, creating a checkout page, and building a smart phone app for mobile purchases.

2. Daily Stand-up Meeting:

Once the Sprint backlog is complete the Scrum team working on the user stories. Everyday scrum team attend the Daily Stand-up a quick meeting. Everybody asked three questions:

  1. What did you do yesterday?
  2. What will you do today?
  3. What obstacles are impeding your progress?

Sprint Burndown Graph: Tell me records all progress in Sprint Backlog. As the team does their work he/she updates and shares the Sprint Burndown Graph with the team. This graph highlights the progress made in Sprint and how much work is remaining.

3. End-of-Sprint Review:

When the entire Sprint works has been completed, the Scrum team presents the first Sprint to be deliverable to Product Owner in the End-of-Sprint Review meeting. After reviewing everything, all are agree the website is ready to go live. Now the customer can shop on the internet. Product owner and Business Analyst talk to the customer in order to get feedback to their experiences. This information is used to identify new requirements for upcoming Sprint.

4. Retrospective:

As final action of the Sprint, team conducted the Retrospective meeting. Systematically discussed what went well and what didn’t well during the Sprint. Identified the areas of improvement in future. The Retrospective complete the Sprint.

After that meeting Sprint2 start and consists of the same process Sprint Planning, Daily Stand-up Meeting, End-of-Sprint Review, and concluding with the Retrospective.

Benefits of Agile:

  • Time to Market.
  • Certainty.
  • Suitable for fixed or changing requirements.
  • Little or no planning required.
  • Increase revenue by focusing on customer value.

About the Author

Leave Comment