Agile Testing Interview Questions:
Agile Testing Interview Questions will help you to prepare for Agile Testing interviews.
Here is the list of 20 Agile Testing interview questions.
Agile Testing Interview Questions 1 – 10:
1. What is Agile Testing?
Agile testing is 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.
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
3. What are the principles of Agile Software Development?
1. Highest priority is to satisfy the customer through early and continuous delivery of business valuable software
2. Welcome changing requirements, even late in development
3. Deliver working software frequently
4. Business people and developers must work together with transparency on daily basis throughout the project
5. Build projects around motivated individuals
6. The best form of communication is to do face-to-face conversation
7. Working software is the primary measure of progress
8. Able to maintain a constant pace
9. Continuous attention to technical excellence
10. Simplicity – the art of maximizing the amount of work not done – is essential
11. Self-organizing teams
12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly
4. What are the main roles in Scrum?
Scrum consists of three main roles:
Product Owner: Product Owner usually represents the Client and acts as a point of contact from the Client side. The one who prioritizes the list of Product Backlogs which Scrum Team should finish and release.
Scrum Master: Scrum Master acts as a facilitator to the Scrum Development Team. Clarifies the queries and organizes the team from distractions and teach the team how to use scrum and also concentrates on Return on Investment (ROI). Responsible for managing the sprint.
Scrum Development Team: Developer’s, QA’s. Who develops the product. Scrum development team decides the effort estimation to complete a Product Backlog Item.
Scrum Team: A cross-functional, self-organizing group of dedicated people (Group of Product Owner, Business Analyst, Developer’s and QA’s). Recommended size of a scrum team is 7 plus or minus 2 (i.e, between 5 to 9 members in a team).
5. What approach do you follow when requirements change continuously?
In Agile methodology, change in requirement is possible. It’s not like other traditional methodologies where the requirements are locked down at the requirement phase. Every team member should be ready to handle the changes in the project.
The team should work closely with the Product Owner to understand the scope of requirement change and to negotiate to keep the requirement changes to a minimum or to adopt those changes in the next sprint. Based on the requirement changes Test Team could update the Test Plan and Test Cases to achieve the deadlines. The team should understand the risk in the requirement change and prepare a contingency plan. It is a best practice not to go for the automation process until requirements are finalized.
6. 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.
7. In what way does agile development methodology differ from other development methodologies?
In Agile methodology, the code is broken down into small branches and only one branch is developed and tested at a time. At one particular time, only one particular branch is developed and tested. Agile teams follow several processes in the agile methodology like continuous communication with the team, frequent changes to get the optimal results etc. This makes the agile process more flexible and focused. This is not the case with other development methodologies.
8. 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
9. What is a Sprint?
In Scrum, the project is divided into Sprints. Each Sprint has a specified timeline (2 weeks to 1 month). This timeline will be agreed by a Scrum Team during the Sprint Planning Meeting. Here, User Stories are split into different modules. The end result of every Sprint should be a potentially shippable product.
10. 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.
11. 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.
Check below video to see “Agile Testing Interview Questions”
Please be patient. The video will load in some time.
If you liked this video, then please subscribe to our YouTube Channel for more video tutorials.
Agile Testing Interview Questions 11 – 20:
12. What are the types of burn-down charts?
There are four popularly used burn down charts in Agile.
i. Product burndown chart
ii. Sprint burndown chart
iii. Release burndown chart
iv. Defect burndown chart
13. What is Product Burndown Chart?
A graph which shows how many Product Backlog Items (User Stories) implemented/not implemented.
14. What is Sprint Burndown Chart?
A graph which shows how many Sprints implemented/not implemented by the Scrum Team.
15. What is Release Burndown Chart?
A graph which shows List of releases still pending, which Scrum Team have planned.
16. What is Defect Burndown Chart?
A graph which shows how many defects identified and fixed.
17. 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?
In general, it’s not a recorded meeting. Reporting will be between peers not to Scrum Master or Product Owner. It is normally timeboxed to a maximum of 15 minutes. It is aka 15 Minute Stand-up Meeting.
Here is a screenshot from Slack Application on daily standup meeting.
18. 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.
19. 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.
20. 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”. It helps the Scrum Team to avoid the mistakes in the next Sprints.
21. 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.
In general, the columns used in a task board are as follows
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
22. What is DevOps?
The term DevOps was formed by combining “Development” and “Operations”. DevOps is an operational philosophy that promotes collaboration between development and operation teams. DevOps focuses on bringing development and operations team together in order to build, test, and release software faster and more reliably.
23. What is the difference between Agile and DevOps?
|Agile focuses on collaboration, small releases and customer feedback.||DevOps focuses on bringing development and operations team together.|
|Agile is developed for faster productions and immediate delivery.||DevOps is developed for faster productions and immediate delivery.|
|Agile usually breaks big modules into smaller one to achieve the goal.||DevOps combines tools and cultural practices to provide faster delivery.|
|Agile focuses constant change. It addresses the gap between customer need, development and testing teams.||DevOps focuses on constant testing and delivery. It address the gap between development, testing and operations.|
|Each team member should be able to what’s required for the progress of the project. All the team members should have equal skill set in Agile.||Development teams and operational teams are different in DevOps. Different teams have different skill set in DevOps.|
|Agile teams are usually smaller in size. Agile teams move faster with fewer people with minimum complexities.||DevOps believes that bigger is better. Many teams work together in DevOps.|
|It believes in constant feedback and daily team meetings to make the teams more productive and efficient.||It follows modern documentation approach to communicate with all the team members rather than conducting daily meetings.|
|Agile takes an iterative approach to Software Development.||DevOps targets end-to-end business solution.|
|Agile doesn’t believe in automation.||Automation is at the core of DevOps. Automate almost everything.|
|Its goal is to address the gap between customer needs and development & test teams.||Its goal is to address the gap between Dev (development and testing) and Ops (Operations).|
|Some of the tools used widely are JIRA, Kanboard, Bugzilla.||Some of the tools used widely are Puppet, Ansible, Chef, AWS, TeamCity OpenStack.|
|Agility in development only.||Agility in both development and operations.|
|Involves in Agile Scrum, Agile Kanban etc.,||Involves in Continuous Integration (CI), Continuous Development (CD), Continuous Testing (CT), etc.,|
|Priority goes to timeliness.||Priority goes to both timeliness and quality.|
|It helps in managing complex projects.||It helps in managing end to end engineering processes.|
|It allows constant changes.||It allows constant testing and delivery.|
|The focus is on functional & non-functional readiness.||The focus is on operational & business readiness.|
|It supports shift left principles.||Its supports both shift left and shift right principles.|
|The target areas of Agile are quick delivery and end to end business solution.||The target area of DevOps is Software development.|
|Agile teams are cross functional.||DevOps has separate development and operational teams and cannot be cross-functional.|
|Easy communication due to daily scrum meetings.||Communication is complex compared to Agile.|
24. What is the difference between Agile and Waterfall model (Agile vs Traditional Project Management)?
|Testing is done in parallel with the development activity which means that as the development progresses so does the testing||Testing is generally done at the end of the development|
|Agile is an iterative and incremental approach||It is a sequential design process where design, development, testing and other phases happens one after another in a sequential way|
|Testing is performed concurrently with software development||"Testing" phase comes after the "Build" phase|
|Requirements are collected even late in development.||Requirements are collected before starting the development in Waterfall model.|
|Agile teams participate in changing requirements.||Waterfall teams were not involved in changing requirements.|
|Agile methodology is known for its flexibility||Waterfall is a structured software development methodology, and often times can be quite rigid|
|It believes in constant feedback and accepts changes to requirements||Customer feedback is usually not collected until the very end of the project, and changes are discouraged|
|Agile focuses on collaboration, small releases and customer feedback||Team coordination is very limited|
|Agile divides the project into sprints.||The waterfall divides the project into stages.|
|Self-motivated and self-organizing teams drive the project||Project manager drives the project as a central controlling authority|
|It allows us to complete multiple small active projects.||It allows us to complete a single project.|
|Testing phase starts in parallel with development in Agile.||Testing phase starts only after the development in Waterfall model.|
25. How long were your sprints?
An ideal sprint length is anywhere between 1 week to 4 weeks. 2 week-long Sprints are most common for IT and software product development.
26. What are the disadvantages of the agile model?
Some of the disadvantages of using the agile model are as follows:
- It is not easy to predict. When you encounter a large project, it becomes more problematic to estimate the amount of effort needed in the project
- In case the guidelines given by the customers is not understood properly, then the final outcome of the project will not meet the customer requirements. It leads to the customer dissatisfaction
- It is not possible to properly focus on the design and documentation of a project sometimes
- Basically, High-level decision making is in the hands of the higher authorities. The team members with little or no experience are not involved in decision-making, thus they don’t get a chance to advance their knowledge
27. What is an impediment in Scrum?
Impediments are the obstacles faced by the scrum team. Any obstacle that keeps the team from getting work done and that slows velocity is known as Impediment. Scrum Master is responsible for removing impediments.
In Agile Scrum interviews, you may be asked to give some examples of impediments.
28. What are the examples of impediments?
Impediments come in many forms. Some of the impediments are mentioned below
- Resource unavailability (Sick team member)
- Lack of management support
- Business issues
- Lack of skill
- Technical, operational issues
- Even external issues such as weather
29. What kind of impediments should a scrum master remove?
Scrum Master’s main responsibility is to identify, track and help remove impediments. Scrum Master shouldn’t remove impediments initially even though Scrum Master can remove impediments on behalf of the Scrum team. The Scrum Master should not pamper nor overrule the Scrum Team. Scrum Master should motivate the Scrum team to become independent enough to face problems and take a decision and perform every task by themselves. The Scrum team should be able to make their own decisions. The Scrum master supports and guides the Scrum Team to operate as efficiently as possible. Sometimes, impediments are beyond the ability of the Scrum Team to remove. In such cases, the Scrum Master may get support from outside of the Scrum Team.
30. What is Velocity?
Velocity is a key metric that is calculated at the end of each sprint by addition of all effort estimates associated with user stories completed in a sprint. It predicts how much work an agile software development team can successfully complete within a sprint and how much time will it need to finish a project. Points from partially-completed or incomplete user stories should not be counted in calculating velocity.
Apart from Agile Testing Interview Questions, earlier I have posted a detailed post on “Agile Scrum Methodology”. If you haven’t gone through it, you can browse by clicking on the link.
Like this post? Don’t forget to share it!
Here are a few hand-picked articles for you to read next: