Q.1. What do you understand by Agile Testing?
Agile testing is a software testing methodology that follows the principles of agile software development. It is an iterative software development methodology where requirements are constantly changing according to customer needs. Testing is done in parallel with iterative model development.The test team receives frequent code changes from the development team and tests the application.
Q.2.What are the Agile Manifesto?
The Agile Manifesto defines four key points:
- Individuals and interactions across processes and tools
- Working software with comprehensive documentation
- Customer collaboration in contract negotiations
- Respond to change instead of following a plan
Q.3. What are the principles of agile software development?
- Customer satisfaction through timely and continuous delivery of software with business value is our top priority
- Embrace changing requirements, even late in development
- Deliver working software frequently
- Business people and developers should collaborate transparently on a daily basis throughout the project.
- Build projects around motivated people
- The best form of communication is face-to-face
- Working software is the primary measure of progress
- can maintain a steady pace
- Continuous Attention to Technical Excellence
- Simplicity – the art of maximising the amount of unfinished work – is essential
- Self-organising teams
- Periodically, the team considers ways to be more effective and adjusts its actions accordingly
Q.4. What are the main roles in Scrum?
Scrum consists of three main roles: Product Owner:
The Product Owner typically represents the customer and acts as the customer’s point of contact. The person who prioritizes the list of product backlogs that the Scrum team needs to complete and release.
Scrum Master: The Scrum Master acts as a facilitator for the Scrum development team.Clarify questions,organize your team to avoid distractions, teach your team how to use Scrum, and also focus on return on investment (ROI). Responsible for Sprint operations.
Scrum Development Team: Developers,QA.who will develop the product;The Scrum development team determinesan effort estimate to complete the product backlog items.
Scrum Team: A cross-functional, self-organizing group of dedicated people (productowners,businessanalysts,developers,QAgroups).
Q.5. What is the Sprint Planning Meeting?
The first step in Scrum is the Sprint Planning Meeting, in which the entire Scrum Team participates. Here, the Product Owner selects Product Backlog Items (User Stories) from the Product Backlog. The most important user stories are displayed at the top of the list and the least important user stories are displayed at the bottom. The Scrum development team determines and creates an effort estimate.
Q.6. What is the Sprint Review Meeting?
At the Sprint Review Meeting, the Scrum Development Team demonstrates a shippable product. The Product Owner indicates which items are complete and which are incomplete. The Product Owner adds items to the Product Backlog based on feedback from stakeholders.
Q.7. What is a Sprint Retrospective Meeting?
The Scrum Team meets again after the Sprint Review Meeting to document the lessons learned from the previous Sprint, such as ‘what went well’ and ‘what could be improved’. It helps Scrum teams avoid mistakes in the next sprint.
Q.8. What is the product burn-down chart?
A chart that shows how many product backlog items (user stories) are implemented/unimplemented.
Q.9. What is the Sprint Burndown Chart?
A chart showing the number of sprints implemented/not implemented by the Scrum team.
Q.10. What is the release burn-down chart?
A graphic showing the list of pending releases planned by the Scrum team.
Q.11 What is an error burn-down chart?
A graph that shows the number of bugs identified and fixed.
Q.12. What is a sprint?
In Scrum, a project is divided into sprints. Each sprint has a schedule (2 weeks to 1 month). This schedule is agreed upon by the Scrum Team during the Sprint Planning Meeting. Here the user story is divided into different modules. The end result of each sprint should be a shippable product.
Q.13. What are the Product Backlog and Sprint Backlog?
Product Backlog: The Product Backlog is a repository where the list of Product Backlog items is stored and maintained by the Product Owner. The list of backlog items for a product is divided into high priority and low priority by the product owner. You can also always re-prioritize your product backlog. Sprint Backlog: A group of user stories (committed Product Backlog items)that the Scrum development team has agreed to do during the current Sprint.This is a subset of the Product Backlog.
Q.14. What types of burn-down charts are there?
There are four burn-down charts commonly used in Agile.
- Product burndown chart
- sprint burndown chart
- SharedBurndownChart
- Error burndown chart
Q.15. What is the Daily Standup Meeting?
The Daily Standup Meeting is a daily meeting. It keeps everyone up to date and helps your team stay organized. Each team member reports to colleague:
- what did you finish yesterday
- Are there any obstacles on the way?’
- What do you promise today?
Below are some of the other Useful blogs:
https://softwaretestingleaders.com/interview-qa-for-agile-testing-you-should-know/
https://softwaretestingleaders.com/agile-vs-waterfall-know-the-difference-between-methodologies/
7 Replies to “Interview QA for Agile Testing: You should know”