Agile Real-Time Questions and Answers

1) As a tester, what should your approach be when requirements

change continuously?

● When requirements keep changing, a continuously agile tester should take the
following approach:
● Write generic test plans and test cases that focus on the intent of the requirement rather
than its exact details.
● To understand the scope of change, work closely with the product owners or business
analysts.
● Make sure the team understands the risks involved in changing requirements, especially
at the end of the sprint.
● Until the feature is stable and the requirements are finalized, it is best to wait if you are
going to automate the feature.
● Changes can be kept to a minimum by negotiating or implementing the changes in the
next sprint.

2) What are epics, user stories, and tasks?

Epic: A customer-described software feature that is itemized in the product backlog is known as
an "epic. Epics are subdivided into stories.
User Stories: From the client perspective, user stories are prepared that define projects or
business functions, and they are delivered in a particular sprint as expected.
Task: Further down, user stories are broken down into different tasks.

3) Mention the key difference between sprint backlog and

product backlog.
Product backlog: It contains a list of all desired features and is owned by the product owner.
Sprint backlog: It is a subset of the product backlog owned by the development team and
committed to deliver in a sprint. It is created in the Sprint Planning Meeting.

4) Explain in Agile the burn-up and burn-down charts.

To track the project's progress, burnup and burndown charts are used.
Burnup Chart: It shows the progress of stories over time.
Burndown Chart: It shows how much work was left to do overtime.

5) What are story points, efforts, or scales?

It is used to discuss the difficulty of the story without assigning actual hours. The most common
scale used is a Fibonacci sequence (1,2,3,5,8,13,...100), although some teams use a linear scale
(1,2,3,4....), powers of 2 (1,2,4,8....), and cloth size (XS, S, M,L, XL).

6) What testing is done during Agile?

The primary testing activities during Agile are automated unit testing and exploratory testing.
Though, depending on project requirements, a tester may execute functional and non-functional
tests on the application under test (AUT),

7) What is the velocity of a sprint and how is it measured?

Velocity is one of the planning tools used to estimate the speed of the work and the time of
completion of the project. The calculation of velocity is done by reviewing the work the team has
successfully completed during earlier sprints; for example, if the team completed 5 stories during
a two-week sprint and each story was worth 3 story points, then the team’s velocity is 15 story
points per sprint.

8) What are the qualities a good agile tester should have?

A good agile tester should have the following qualities:

● It should be able to understand the requirements quickly.

● Agile testers should know Agile principles and concepts well.

● As requirements keep changing, testers should understand the risks involved in them.

● Based on the requirements, an agile tester should be able to prioritize the work.

● Continued communication between business associates, developers, and testers is a must.

9) Who are all involved in the Agile team?

In Agile, the two main leads are
Scrum Masters: It coordinates most of the inputs and outputs required for an agile program.
Development Managers: They hire the right people and develop them with the team.

10) Mention in detail what the roles of a scrum master are.

The Scrum Master's key responsibilities involve

● Understand the requirements and turn them into working software.

● Monitoring and tracking

 ● Reporting and Communication

● Process Check Master

● Quality Master

● Resolve Impediments

● Resolve Conflicts

● Shield the team and performance feedback

● Lead all the meetings and resolve obstacles.

11) Mention what the difference is between Scrum and Agile.

Scrum: In scrum, a sprint is a basic unit of development. Each sprint is followed by a planning
meeting, where the tasks for the sprint are identified and estimated. During each sprint, the team
creates a finished portion of a product.
Agile: In Agile, each iteration involves a team working through a full software development
cycle, including planning, design, coding, requirement analysis, unit testing, and acceptance
testing when a product is demonstrated to stakeholders.
In simple words, agile is the practice, and scrum is the process of following this practice.

12) Explain how you can implement scrum in an easy way for
your project?
These are the tips that can be helpful in implementing scrum in your project.

● Get your backlog in order.

● Get an idea of the size of your product backlog.

● Clarify the sprint requirements and duration to complete the sprint backlog.

● Calculate the team sprint budget and then break the requirements into tasks.

● Collaborate workspace: a center of all team discussion, which includes plans, roadmaps,
key dates, sketches of functionality, issues, logs, status reports, etc.

● Sprint: Make sure you complete one feature at a time before moving on to the next. A
sprint should not be aborted unless there is any other option.
 ● Attend a daily stand-up meeting. In the meeting, you need to mention what has been
achieved since the last meeting, what they will achieve before the next meeting, and if
anything is holding up their progress.

● Use a burndown chart to track daily progress. From the burndown chart, you can estimate
whether you are on track or running behind.

● Complete each feature well before moving on to the next.

● At the end of the sprint, hold a sprint review meeting and mention what was achieved or
delivered in the sprint.

13) Agile management tools and software

● Zephyr is the #1 selling test management tool, providing end-to-end solutions for agile
teams of all sizes. Get the flexibility, visibility, and insights you need to release better
software. FASTER
● Sprints is a tool that helps you manage your team and product with ease. It enables you to
track your progress without hassle. This software can be used to find bottlenecks and
discover ways to generate business value.
● Backlog :- is an all-in-one project management tool built for developers. Agile teams use
Backlog to work with other teams for enhanced team collaboration and high-quality
project delivery.
● Bug shooting is a useful tool for software developers as well as agile testing. It provides
an easy way to create screen captures and attach them to items in a bug tracking or issue
management system for reporting bugs.
● Snagit :- is a popular screenshot-capturing tool. It provides powerful tools to edit,
annotate, and share screenshots. It can also be used to submit and push screenshots
directly.
● JIRA :- is a defect tracking tool that is used for agile testing as well as project
management. This tool is not only used for recording and reporting but is also integrated
with the code development environment.
● SoapUI :- is an agile testing tool for service-oriented architectures (SOA) and REST. Its
functionality includes web service inspection, invoking, development, functional testing,
and load testing.
● J meter :- The Apache JMeter application is an open-source agile performance testing
tool. It is used to load functional tests and measure the performance of the website.
● Selenium WebDriver is an automation and agile testing tool. It aims to mimic the
behavior of a real user and, as such, interacts with the HTML of the application.
● Appium :- is an open-source and free Agile tool. It is helpful for automating mobile web,
iOS, Android, and hybrid applications. Native apps are those written using Android, iOS,
or Windows SDKs.
● Usersnap is an agile testing tool that allows web developers to get screenshots of bugs.
This tool helps testers and developers communicate bugs easily.
14) How is agile methodology different from traditional
waterfall processes?
In agile methodology, features of the software are delivered frequently, so the testing activity is
done simultaneously with the development activity. Testing time is shortened as only small
features need to be tasted at once.
In the waterfall model, testing activities take place at the end of the entire development process.
Testing time, in this case, is as long as the entire product is to be tested in one go. Waterfall
methodology is a closed process where all stakeholders are not involved in the development
process, whereas agile methodology requires the involvement of various stakeholders, including
customers.

15) What kinds of projects are suitable for the Agile

Methodology?
The traditional methodology is suited for projects with predefined, clearly stated requirements,
while the agile development methodology is suitable for projects with dynamic requirements
where frequent changes in the product come up on a regular basis.

16) What is the ideal duration of a Scrum Sprint?

The duration of a Scrum Sprint or Scrum Cycle primarily depends on the size of the project and
the team working on it. A Scrum team may consist of 3–9 members, and it takes about 3–4
weeks to draught and complete a Scrum script. Going by this calculation, the average duration of
a Scrum sprint is four weeks.

17) What do you understand by Daily Stand-Up?

Ans: You may surely get an interview question about daily stand-up. So, what should be the
answer to this question? The daily stand-up is an everyday meeting (most preferably held in the
morning) in which the whole team meets for almost 15 minutes to find answers to the following
three questions:

● What was done yesterday?

● What is your plan for today?

● Is there any impediment or block that prevents you from completing your task?

The daily stand-up is an effective way to motivate the team and make them set a goal for the day.

18) Is there any drawback to the agile model? If yes, explain.

Ans - Yes, there are some drawbacks to the Agile model; some of them are as follows:
 ● It is not easy to make a prediction about the effort required to complete a task. It becomes
more problematic in the case of large projects, as it becomes difficult to get an idea of the
total effort required.

● Sometimes, it’s not possible to properly focus on the design and documentation of the
project.

● If the requirements of the client are not understood properly, the final project will not
meet the customer's requirements. Thus, it will lead to customer dissatisfaction.

● Only a leader who has considerable experience in agile methodologies is capable of

taking important decisions. The team members with little or no experience are not
involved in decision-making, so they don’t get a chance to advance their knowledge.

19) What do you know about a story point in Scrum?

Ans - A story point in Scrum is the unit for the estimation of the total efforts that are required to
perform or complete a particular task. So, here is how you can answer such agile scrum interview
questions on a single line:

20) State some major principles of agile testing (advantages).

Some major principles of agile testing are:

● Customer satisfaction

● Face-to-face communication

● Sustainable development

● Quickly respond to changes

● Continuous feedback

● Successive improvement

● Self-organized

● Focus on essence.

● Error-free, clean node

● Collective work
21) How is an agile testing methodology different from other
testing methodologies?
The agile testing methodology involves the division of the whole testing process into multiple
small segments of code. In every step, these segments of code undergo testing. There are a
number of additional processes involved in agile testing methodologies, such as team
communication, strategic modifications for optimal results, and many others.

22) How do you manage if the story is high priority and

resources are left before the last day of sprint completion?
Ans - First, analyze the pending tasks and their impact on the overall sprint. According to that,
try to find an alternative solution to manage the situation. As a leader, you can decide to work
some extra hours to complete the sprint and can also ask (remember to ask, not to tell) other team
members to do so. And this way, you can complete the sprint on time.
In case more or all the members leave just before the sprint's completion, the situation can be
handled as follows:

● Analyst the amount of pending work and its impact on the overall sprint.

● Check if you can manage the situation and finish the task by yourself, or try to get some
other resources to work. (Although this won’t be feasible as you will have to first explain
everything about the sprint and task done to the new team; of course it won’t be possible
in a day.) So, if you can’t manage to complete the sprint by yourself, it’s better to tell
your product owner. You can ask him to give you some more time to complete the sprint,
so you can get a new team or get it done by yourself by working extra hours.

23) 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's needs. Testing is done in parallel with the development of an
iterative model. The test team receives frequent code changes from the development team when
testing an application.

24) What approach do you follow when requirements change

continuously?
In Agile methodology, changes in requirements are 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 the 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, the test team could update the test plan and
test cases to meet the deadlines. The team should understand the risk of the requirement change
and prepare a contingency plan. It is best practice not to go for the automation process until
requirements are finalized.

25) How is agile testing different from other traditional software

development models?
- In agile methodology, testing is not a phase like in other traditional models. It is an activity
parallel to development in Agile. The time slot for testing is shorter in Agile compared to
traditional models. The testing team works on small features in Agile, whereas the test team
works on a complete application after development in traditional models.

26) When do we use the 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 once

27) 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 upon by the 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.

Sprint Backlog: A group of user stories that the scrum development team agreed to do during the
current sprint (committed product backlog items). It is a subset of the product backlog.