What exactly is Agile Methodology?
What is Agile?
Agile is an updated version of the spiral model
Agile is an iterative & incremental approach where requirement keeps on changing as a company we will be flexible enough to take up the requirement changes at any point in time.
We develop and test the changes & we can give quality software to customers within a short span of time.
In Agile there will be good interaction between the customer, business analyst, developer, and Test Engineer where in we directly interact with the customer & get the feedback & develop the changes & Test the changes within a short period, we can give quality software to the customer.
The main goal of Agile is Customer satisfaction through the quick delivery of a working piece of software.
Principles of Agile
1. Customer can change the requirement at any point in the development stage.
2. Releases should be short.
3. Our highest priority is customer satisfaction through quick delivery of a working piece of software.
4. Developer and Test Engineer will conduct a lot of meetings, regular intervals, in order to improve the quality of the process.
5. It is a simple model to adopt.
6. There should be good interaction between Business analysts, Developers, and Test engineers.
What is Agile Testing
Testing the software or Application by following the principles of Agile methodology.
Types of Agile Methodology
1. Scrum methodology (Scrum Process).
2. Feature Driven Development (FDD).
3. Extreme programming.
4. Lean and Kanban.
5. Adoptive software development method.
6. dynamic software development method.
7. Crystal clear.
Scrum Process
· Terminologies.
1. Release
The release is nothing but a combination of sprints.
2. Epic
The complete set of requirements is called Epic. One Epic consists of multiple features or modules. BA or Scrum Master will create an Epic in Project Management Tool.
3. User Stories / Story cards
The Feature or functionality is called User Stories / Story cards.
4. Story points.
It is a rough estimation given by developers and Test Engineers to develop and test every individual story.
5. Swag
It is also a rough estimation given by the Developer and Test Engineer for every individual story in the form of hours.
Q.1. Based on what criteria developer will give an Estimation?
Ans. Understanding requirements, Design (HLD/LLD), Writing the code, Code Review, WBT, and fixing the Defects.
Q.2. Based on what criteria Test Engineer will give an Estimation?
Ans. Understanding requirements, Writing scenarios and Test Cases, Reviewing test cases, Testcase Execution, and Defect Tracking.
6. Sprint
Sprint is the actual time spent by the developers and Test Engineers to develop and Test one or more Stories
7. Sprint planning
It is a meeting conducted by Scrum Master. On the first day of every sprint. Business Analysts, Customers, Developers, Test Engineers, and Scrum Masters will be involved in this meeting.
In this meeting, BA will explain the complete requirements to the (Scrum development team) He will also explain the business flow of the requirement & also how each and every feature should work. The scrum master will prioritize the stories from the customer’s business point of view & he will assign stories to the developer and Test Engineer.
In this meeting, the scrum master will calculate the available hours of every individual engineer in a sprint.
Join us on Telegram for daily QA jobs updates
Also, Join our WhatsApp Community now
Also, check Permanent WFH Software Testing Jobs
FREE download Software Testing Study Materials
Also, check QA Freshers and Experienced Jobs
Also, check Freshers IT Jobs
Also, check Software Testing Courses
Also, check Software Testing Interview Questions and Answers
Also, check Why Cypress is Better than Selenium in 2022?
Q.1. Who is Scrum Master?
Ans. Scrum Master is a person, who is responsible the for delivery of software to the customer within a planned period of time.
He will be mainly involved in creating stories in the project management tool & He will also create the task for the stories.
He will also track the activity done by Business Analyst, Developer & Test Engineer.
Q.2. Who can become Scrum Master?
Ans. Business Analysts, Senior Developers, Senior Test engineers, and even Customers can become Scrum masters.
8. Scrum Meeting (Daily StandUp Meeting)
It is a meeting conducted by the scrum master on daily basis, which is strictly bounded for 15 minutes. Business Analysts, Developers, Test Engineers, & Scrum Masters will be involved in this meeting.
It is also called as Daily StandUp Meeting
In this meeting, we discuss about
1. What you did yesterday?
2. What are plans for today?
3. Are there any obstacles?
9. Sprint Retrospective Meeting
It is a meeting conducted by the scrum master on the last day of every sprint.
Business Analysts, Developers, Test Engineers, & Scrum Masters will be involved in this meeting.
In this meeting, we discuss about
1. What went well?
2. What didn’t go well?
3. Are there any action plans?
10. Release Retrospective Meeting
It is a meeting conducted by the scrum master on the last day of every release.
Business Analysts, Developers, Test Engineers, & Scrum Masters will be involved in this meeting.
In this meeting, we discuss about
1. What went well?
2. What didn’t go well?
3. Are there any action plans?
11. Bug Triage Meeting
It is a meeting conducted by Test Engineer or Scrum Master, one week or two weeks before the Release or a Sprint.
In this meeting, the Test Engineer will get the list of all the pending bugs or open bugs which was not fixed by Developers as a part of the current release and also the previous release.
As a team will reprioritize the bugs from the customer business point of view & we decide which defect should be fixed in the current release & which defect should be moved to the next upcoming releases.
12. Product Backlog Grooming
It is a meeting conducted by Business Analyst or Scrum Master, a week or two weeks before the Release or a Sprint.
Business Analysts, Developers, Test Engineers, & Scrum Masters will be involved in this meeting.
In this meeting, the developer, Test Engineer will get the list of all the Stories which was not implemented in the current release and previous releases. As a team will reprioritize the Stories from the customer business point of view & we decide which story to be implemented in the current release & which story should be moved to the next upcoming releases.
13. Bug Bucket
It is an Epic or a Story which is created by business analyst or scrum master in the project management tool.
This bug bucket will be addressed for every individual releases
Bug bucket consist of :
· new feature test bug (NFT)
· Performance bugs
· Regression bug
· security bug
14. Chickens
Chicken are the people who are not committed to the project and they get business to company and they get work done by team
Example: CEO, Stake holders, Management team
15. Pigs
Pigs are the people who are committed to the project and they work on the project and they complete the project within a given period of time
Example: Test engineer, Developer, Scrum master.
Disadvantages of the Agile model
· It is very difficult to handle long-term projects.
· Least focus on designing and documentation.
· Experienced people in the company will take up the decision with a respective project where in there is no space for fresher to take decision.
Advantages of Agile the model
· Investment done in a proper way.
