In this video, we are going to learn about the Top 21+ Agile Testing Interview Questions and Answers.
Agile Testing Interview Questions and Answers will help you prepare for Agile methodology and agile process interviews for testers or developers.
Learn:
Question 1: What is Agile Testing?
Its a software testing practice that follows the principles of Agile software development.
It is an iterative software development methodology where requirements keep changing as per the customer needs.
Testing is done in parallel to the development of an iterative model.
Test team receives frequent code changes from the development team for testing an application.
Question 2. What is Agile Manifesto?
Agile manifesto defines 4 key points:
i. Individuals and interactions over process and tools
ii. Working software over comprehensive documentation
iii. Customer collaboration over contract negotiation
iv. Responding to change over following a plan
Question 3: How is Agile Testing different from other traditional Software Development Models?
It is one of the common Agile Testing Interview Questions.
In Agile Methodology, testing is not a phase like other traditional models.
It is an activity parallel to development in the Agile.
The time slot for the testing is less in the Agile compared to the traditional models.
The testing team works on small features in Agile whereas the test team works on a complete application after development in the traditional models.
Question 4: When do we use Agile Scrum Methodology?
i. When the client is not so clear on requirements
ii. When the client expects quick releases
iii. When the client doesn’t give all the requirements at a time
Question 5: What are Product Backlog and Sprint Backlog?
Product Backlog: Product Backlog is a repository where the list of Product Backlog Items stored and maintained by the Product Owner.
The list of Product Backlog Items are prioritized by the Product Owner as high and low and also could re-prioritize the product backlog constantly.
Sprint Backlog: Group of user stories which scrum development team agreed to do during the current sprint (Committed Product Backlog items). It is a subset of the product backlog.
Question 6: What is the difference between Burn-up and Burn-down chart?
Burn Down Charts provide proof that the project is on track or not. Both the burn-up and burn-down charts are graphs used to track the progress of a project.
Burn-up charts represent how much work has been completed in a project whereas Burn-down chart represents the remaining work left in a project.
Question 7: What are the types of burn-down charts?
i. Product burndown chart
ii. Sprint burndown chart
iii. Release burndown chart
iv. Defect burndown chart
Question 8: What is Product Burndown Chart?
A graph which shows how many Product Backlog Items (User Stories) implemented/not implemented.
Question 9: What is Sprint Burndown Chart?
A graph which shows how many Sprints implemented/not implemented by the Scrum Team.
Question 10: What is Release Burndown Chart?
A graph which shows List of releases still pending, which Scrum Team have planned.
Question 11: What is Defect Burndown Chart?
A graph which shows how many defects identified and fixed.
Question 12: What is a Daily Stand-up Meeting?
Daily Stand-up Meeting is a daily routine meeting. It brings everyone up to date on the information and helps the team to stay organized.
Each team member reports to the peers the following:
What did you complete yesterday?
Any impediments in your way?
What do you commit to today?
When do you think you will be done with that?
Question 13: What is a Sprint Planning Meeting?
The first step of Scrum is the Sprint Planning Meeting where the entire Scrum Team attends. Here the Product Owner selects the Product Backlog Items (User Stories) from the Product Backlog.
Most important User Stories at the top of the list and least important User Stories at the bottom. Scrum Development Team decides and provides effort estimation.
Question 14: What is a Sprint Review Meeting?
In the Sprint Review Meeting, Scrum Development Team presents a demonstration of a potentially shippable product.
Product Owner declares which items are completed and not completed. Product Owner adds the additional items to the product backlog based on the stakeholder’s feedback.
Question 15: What is a Sprint Retrospective Meeting?
Scrum Team meets again after the Sprint Review Meeting and documents the lessons learned in the earlier sprint such as “What went well”, “What could be improved
Question 16: What is a Task Board?
A task board is a dashboard which illustrates the progress that an agile team is making in achieving their sprint goals.
i. User Story: Actual Business Requirement (Description)
ii. To Do: All the tasks of current sprint
iii. In Progress: Any task being worked on
iv. To Verify: Tasks pending for verification
v. Done: Tasks which are completed
Top comments (0)