An Overview of the Agile Processes

 Agile processes

•             What is Agile?

•             Agile Manifesto

•             Agile Development Life Cycle

•             The Agile Processes

What is Agile?

The term "Agile" in short means the ability of response to change from requirements, technology and people. Agile does not make decisions for you instead it gives you the foundation for teams to make decisions that result in a better software. When a team is developing a project, the client, staff working on that project can adapt to change and that change is done here using the agile methodology which is easy and efficient.

What is the Agile Manifesto?

The agile manifesto says that we are uncovering better ways of developing software by doing it and helping others do, through this work we have come to value:

- Individuals and interactions over processes and tools

- Customer collaboration over contract negotiation

-Responding to change over following a plan

-Working software over comprehensive documentation

The Agile development Life cycle

The Agile development life cycle, much like the Agile process in general, is very versatile and flexible in nature. When compared to lifecycles of more conventional methods like the waterfall, the Agile SDLC(Software Development Life Cycle) is much more dynamic. Different teams may make changes to the lifecycle based upon their personal preferences and experiences.

Agile Processes

The agile process refers to a software development approach based on iterative development, the agile process breaks tasks into smaller iterations hence if any changes are needed then in the next iteration they are applied.
Lets take a look at the Agile Processes

1. Daily stand up meetings checklist : Daily Stand up, where all the team members meet every day to make sure that no team member is stuck on any problem for more than few hours, keeping a check on the progress of the sprint and taking care of any problem.

2. Sprint Turnover: Sprint Turnover is a process when every two weeks, the last sprint comes to a close; as newsprint is planned, this process is documented in order to avoid any overlooked or unassigned issue.

3. Sprint Retrospective: the team talks about three points:

• Positive of Sprint Cycle
• Negative of Sprint Cycle
• How to Improve the Process

4. Sprint Estimation: The planning Poker method is used so that the issues are carefully estimated and assigned so that Sprints consists of a balanced and achievable amount of work. Each team member’s estimations are equally weighed.

5. Pull request procedure: To avoid any risks to pull requests, a lot of emphasis is given by the development team to make sure that it is done with care.

6. Pull request review failed procedure: The checklist in this procedure helps the developers to follow if their pull request has failed review by strictly rectifying the reasons for rejection, answering back with information showing how you have re-checked and solved the issues, and then again assigning the problem to a manager for a next review.

7. Pull Request Merge Process: Merge Procedure is used for proving that it will not break anything and only fix the issue before a pull request can be merged and approved.