Scribd
Upload
242 views3 pages

Agile Testing Interview Questions 1

Agile testing is a software testing practice that follows the principles of agile software development. It involves iterative testing where requirements are continuously changing based on customer needs. Testing occurs parallel to development with the test team receiving frequent code changes. The Agile Manifesto defines key principles including prioritizing working software over documentation and responding to change over following a plan. Agile differs from traditional models in that testing is not a separate phase but occurs continuously throughout development in short iterations.

Uploaded by

Sunita
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
242 views3 pages

Agile Testing Interview Questions 1

Agile testing is a software testing practice that follows the principles of agile software development. It involves iterative testing where requirements are continuously changing based on customer needs. Testing occurs parallel to development with the test team receiving frequent code changes. The Agile Manifesto defines key principles including prioritizing working software over documentation and responding to change over following a plan. Agile differs from traditional models in that testing is not a separate phase but occurs continuously throughout development in short iterations.

Uploaded by

Sunita
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

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.

You might also like