AGILE

Over the past several years, a new way of creating software has taken the software development and testing world by storm: Agile.
In 2017, 94% of organizations practice Agile in some form.
Agile is a time boxed, iterative approach to software delivery that builds software incrementally from the start of the project, instead of trying to deliver it all at once near the end.

 AGILE is a methodology that promotes continuous iteration. 
Agile is a term used to describe approaches to software development emphasizing incremental delivery, collaboration and continual learning.
Agile is a disciplined project management process that encourages frequent inspection and adaptation, strong leadership, defined engineering practices, etc.

Agile methodologies all started based on four core principles as outlined in the Agile Manifesto.
These methodologies are rooted in adaptive planning, early delivery and continuous improvement, all with an eye toward being able to respond to change quickly and easily.

 Agile principles are all about being collaborative, flexible and adaptive.

 To succeed, testers need to be flexible and able to adapt to moving targets.

It works by breaking projects down into little bits of user functionality called user stories, prioritizing them, and then continuously delivering them in short two week cycles called iterations.

http://www.agilenutshell.com/how_does_it_work

Agile is Not One-Size-Fits-All

Every organization is unique and faces different internal factors (i.e. organization size and stakeholders) and external factors (i.e. customers and regulations). To help meet the varying needs of different organizations, there are various Agile methodologies and several different types of testing you can do while working within one of those Agile methodologies. Which mix is right for your team will depend on your internal and external factors, needs and goals.

• Agile Methodologies
  • Scrum
  • Kanban

• Testing Methods
  • Behavior Driven Development (BDD)
  • Acceptance Test Driven Development (ATDD)
  • Exploratory Testing
  • Session Based Testing

https://www.qasymphony.com/blog/agile-methodology-guide-agile-testing/
  

2 Agile Methodology Types

1) Scrum:

Scrum takes a highly iterative approach that focuses on defining key features and objectives prior to each sprint. It is designed to reduce risk while providing value quickly.
The team then cycles through a series of sprints to provide small bursts of value quickly. 

who should be involved when taking a Scrum approach include:

• Product Owner
• Scrum Master
• Developers
• Automation Engineers
• Testers
• Stakeholders

 

2. Kanban is a very simple Agile based methodology rooted in manufacturing

At it’s core, Kanban can be thought of as a large, prioritized to-do list. Like with Scrum, requirements in Kanban are tracked by their current stage in the process (to-do, in development, in test, done).  

Key team members who should be involved in a Kanban environment include:

• Product Owner
• Project Manager
• Developers
• Automation Engineers
• Testers