Agile Development Lifecycle

Agile Development Lifecycle

The Agile Development Lifecycle is a series of phases that a project goes through right from planning to launch. One of the common approach of Agile Lifecycle is to work through sprints. A sprint can last from one to four week based on the project requirement and releases. Let’s have a look at the different stages of the Agile lifecycle.

  1. Plan/Requirement Gathering: This phase involves defining project goal, understanding the scope, plan and estimate the roadmap of the project.
  2. Design: The team will design wireframes/low fidelities to lay down the project architecture. The Product Owner works with the design team to incorporate the scope and finalise the theme of the user interface. This phase involves going back and forth to improve the user experience of the project.
  3. Development: The developers work on the assigned tasks based on the user stories created on each sprint. This includes code review, code quality and unit testing..
  4. Testing: At the end of every sprint, the QA team tests the entire scope of the user stories based on the defined acceptance criteria. This can also take place between the development phase based on how the builds are sent to the QA team. The Agile life cycle incorporates various types of testing including integration testing, acceptance testing, system testing, load and performance testing.
  5. Deployment: After successful testing, the product is deployed on the specific host/domain. This can be automated using CI/CD pipelines.
  6. Delivery/Release: Once the product is built, tested and reviewed internally, it’s prepared for launch.
  7. Maintenance: After every release, the launched product is reviewed to improvise based on user’s feedback.

Git Workflows For Agile Development Teams

Git Flow is a branching model that involves the use of different types of branches based on the objective of the task.

GitFlow Workflow

Table of Content

  • The Git Flow strategy consists of the following branches
  • Agile Development Lifecycle
  • Steps to Integrate Git In Your Agile Workflow
  • Choosing the Right Git Workflow
  • Benefits of Git for Agile Teams
  • Frequently Asked Questions on the Git Workflows

Similar Reads

The Git Flow strategy consists of the following branches

Main: This branch is used for production deployment. Develop: New features are merged into this branch. Feature: A branch was created to develop a new feature. Release: This branch prepares code for a production release. Hotfix: A branch for critical production fixes....

Agile Development Lifecycle

Agile Development Lifecycle...

Steps to Integrate Git In Your Agile Workflow

Let’s see above flow through an example....

Choosing the Right Git Workflow

There are three types of Git Workflows to choose from:...

Benefits of Git for Agile Teams

Task Git branch. During the sprint planning, the Product Owner, Product Manager along with the Development team decide the scope of the upcoming sprint along with the user stories. These user stories consist of tasks and sub-tasks which are allocated to developers. Consider each task as a Git branch. With the help of code review, each task – each branch can be reviewed separately which helps in maintaining code quality. Once the development phase of a branch is complete, it can move to the next stage of the Agile Life Cycle; testing. The developer can inform the QA team that a particular feature has finished and can be tested. This helps testers to start with their work without waiting for the entire sprint tasks to be completed. The DevOps team can set up automated tests – continuous integration or continuous delivery which can be executed after every merge. Using Git strategy gives an overall transparency to the team to identify the work done on any feature and even track the changes made for any releases, bug fix or hotfixes....

Frequently Asked Questions on the Git Workflows

What is git fetch vs git pull?...