1

AGILE METHODOLOGY
1.What is agile ?
Agile is a software development model with
the idea of iterative development, where
requirements and solutions evolve through
collaboration between self-organizing cross-
functional teams. The ultimate value in Agile
development is that it enables teams to
deliver value faster, with greater quality and
predictability, and greater aptitude to
respond to change. Scrum and Kanban are
two of the most widely used Agile
methodologies. 
2.What are the key characteristics of agile?
1. Iterative design process
2. Continuous stakeholder engagement
3. Aims for quality and reliable software
4. Short development cycles (up to a month)
allows to the regular delivery of software.
3.Difference between the agile and traditional
models?or Agile manifestos ?
1.Individuals and interactions over processes
and tools

Prepared by Amaravathi Pokala- Quality Thought

 2

2.Working software over comprehensive

documentation
3.Customer collaboration over contract
negotiation
4.Responding to change over following a plan

Compared to waterfall development,

agile projects are far more likely to deliver
on time, on budget, and having met the
customer’s need.
5.Advantages of Agile ?
-> Customer satisfaction on early delivery of
valuable software.
-> Product is developed fast and frequently
delivered
(weeks rather than months.)
-> It continuously gave attention to technical
excellence and good design.
-> Daily and close cooperation between
business people and developers.
-> Even late changes in requirements are
welcomed.

6.Disadvantages of Agile?
Prepared by Amaravathi Pokala- Quality Thought
 3

-> It is not useful for small development

projects.
-> There is a lack of intensity on necessary
designing and documentation.
-> It requires an expert project member to
take crucial decisions in the meeting.
-> Cost of Agile development methodology is
slightly more as compared to other
development methodologies.
-> The project can quickly go out off track if
the project owner is not clear about
requirements and what outcome he/she
wants.
7.Which projects are suitable for Agile?
Agile is most appropriate on any urgent
project with significant complexity
Especially the one which has frequent
changes in requirements.
8.Frameworks in Agile?
Three popular agile frameworks: Scrum,
Kanban, and Extreme Programming (XP)
Other than these we have some more
frameworks like …
Feature Driven Development (FDD)
Prepared by Amaravathi Pokala- Quality Thought
 4

Lean Software Development (LSD)

Adaptive System Development (ASD)
Dynamic Systems Development Method
(DSDM)
Crystal Clear
9.What is Scrum?
The Scrum is a framework which is primarily
team based, and defines associated roles,
events, artifacts and rules.
10. What are the Roles in Scrum?
1. The product owner who represents the
stakeholders,
2. The scrum master who manages the team
and the Scrum process
3. The scrum team, about 7 developers, who
develop and test the software.
11. What are scrum
ceremonies/events / Meetings ?
4 main ceremonies
1.Sprint planning
2.Daily stand up
3.Sprint review
4.Sprint retrospective
12. What is sprint ?
Prepared by Amaravathi Pokala- Quality Thought
 5

A sprint is a 1 to 4 week time-boxed event

focused on the delivery of a subset of User
Stories taken from the Project Backlog.
13. What is sprint planning meeting?
In Scrum, every project is broken into time
blocks called sprints, usually 2-4 weeks long. A
sprint planning meeting is when the team
(including the Scrum Master, Product owner,
and Scrum Team) meets to determine which
backlog items will be handled in the next
sprint.Any items not completed in previous
sprints might be moved to the product
backlog.
14. Sprint planning checklist ?
1.Come prepared with data and estimated
story points
2.Confirm estimated story points for all items
on the backlog (or, at minimum, in the next
sprint)
3.Agree on the items to move to the new
sprint
4.Determine the team’s capacity for the
upcoming sprint and compare it with the
total story points proposed
Prepared by Amaravathi Pokala- Quality Thought
 6

5.End the meeting with a Q&A to ensure all

team members are on the same page
15. What is daily standup meeting?
5- 15 minutes daily meeting for scrum team
Daily at same time
Not a status meeting
It Facilitates by scrum master
Focus on three main point :
1.What u did yesterday?
2.What u do today?
3.Are there any impediments ?
If further discussion need then takes place
immediately after stand up.
16. What is sprint review meeting ?
The Sprint Review is to inspect the outcome
of the Sprint and determine future
adaptations. The Scrum Team will demo the
results of their work to product owner.
17. What is sprint retrospective meeting ?
The sprint retrospective is a recurring meeting
held at the end of a sprint used to discuss
1. what went well during the previous sprint
cycle

Prepared by Amaravathi Pokala- Quality Thought

 7

2. what need to be improved for the next

sprint.
These retros help the team for self-
improvement.
. 

18. What is the definition of done ?

The definition of done (DOD) means that all
aspects of a user story have been completed
in a sprint backlog.
Done – potentially shippable
19. What are the artifacts in scrum?
1.Product backlog
2.Sprint backlog
3.Burndown chart
4.Product increment
20. What is an epic?

 An epic is a large body of work or

requirement that can be broken down into a
number of smaller stories/ user stories.
21. What are user stories?
The User Story is a one or two line
description of the business need, usually
Prepared by Amaravathi Pokala- Quality Thought
 8

described in terms of features.

User Story in the following format.
As a [role]
I want a [goal/desire]
So that [benefit]
Example : As user , I want a search
suggestions so that I can search easily.

The User Stories describe the set of features

that will satisfy each Information
requirement.
22. What is a story point?
Story points are used to represent the size,
complexity, and effort needed for completing
or implementing a user story.
23. What is technical debt?
Technical debts are the part of requirements
that are omitted, not done, or are at a lower
priority and low importance.
24. What is a task?
Tasks are the activities performed to deliver
a User Story.
25. What is a product backlog?

Prepared by Amaravathi Pokala- Quality Thought

 9

The backlog contains all the User Stories

(features) for the product. The Product Owner
is responsible for defining the User Stories,
and assigning each with a priority for delivery.
The order may also be influenced by Story
dependencies or business value e.g. a lower
priority Story may need to be done first
before a higher priority Story can be started.

26. What is a product backlog refinement ?

All the backlog items will be prioritized in
order of importance
27. What is a sprint backlog?
The sprint backlog is the part of the product
backlog that the team will be working on in
their sprint. Think of it as the to-do list for the
sprint.

The sprint backlog is further broken down into

tasks for the team to execute. Every item on
the sprint backlog needs to get developed,
tested, and documented. The product owner
helps the scrum team come up with a sprint
backlog during their sprint meeting.
Prepared by Amaravathi Pokala- Quality Thought
 10

28. What is a taskboard/sprint board?

The sprint backlog is often represented as a
task board, which is broken up into columns
that represent the workflow. They tend to
have the following titles:

To-Do, which are tasks that have yet to

start
Doing, where the work has begun
To Verify, which are completed tasks that
are waiting for verification by another scrum
team member
Done, which means no more work is
required.

29. What is sprint backlog refining ?

Work is discussed regularly at the daily scrum
and the sprint backlog is modified as
needed.The estimate for what work remains
to be done is updated. If there are items that
become unnecessary, they are removed. This
is known as backlog refining.

Prepared by Amaravathi Pokala- Quality Thought

 11

But, again, only the scrum team can do this.

They have ownership over the sprint backlog
and this process. The sprint backlog is highly
visible and provides a picture of the sprint as
the team is working on it.

30. What is a sprint burndown chart?

A burndown chart plots the estimation points
you "burn" in your sprint across time. At one
glance, an agile burndown chart shows you
how much work you've completed, how much
work you have left.
It's a simple and powerful report to forecast
how much you need to complete each day if
you are to complete your goals .
Burndown: A burndown chart maps the
remaining amount of work left against a
timeline.
Burn up : A burnup chart maps the the
amount of work completed over a timeline.
Both charts can be mapped for a sprint, an
epic, or a release.
Prepared by Amaravathi Pokala- Quality Thought
 12

Scrum master updates burn down chart.

31. What is a sprint velocity?

The rate of progress of a scrum team is called

velocity, which is the number of story points
in the user story that have been completed
during the sprint. Partially finished work isn’t
calculated into velocity.
32. What is a product increment?
The product increment is all the product
backlog items that have been done over the
last number of completed sprints.this is
transparency not only for the team but for the
stakeholders in terms of where the product is
at the moment.
33. What are the responsibilities of a
product owner?
->Represents the stakeholders
-> Collaborates with the Stakeholders and the
Scrum Team.
-> Manages product backlog
Explains the product backlog items.
Prioritizing the work items.
Prepared by Amaravathi Pokala- Quality Thought
 13

Makes sure that the product backlog is easily

understandable & transparent.
Clearly defines what items to work on.
-> Ensures that the development team
understands the
item in the product backlog
-> Take a decision on when to release the
work items.
34. What are the responsibilities of a scrum
master?
-> Makes sure that the Scrum is clearly
understood and adopted by the team.
-> Removing Impediments
-> Facilitating Scrum events whenever
requested.
-> Ensures that the meetings are time boxed.
Ensuring a good relationship between the
team and product owner as well as others
outside the team.
-> Protecting the team from outside
interruptions and
distractions.
35. What are the responsibilities of a scrum
team?
Prepared by Amaravathi Pokala- Quality Thought
 14

-> Delivers a potentially releasable Increment

of “Done” product at the end of each Sprint.
-> They are self-organizing and cross-
functional.
-> No one tells the Development Team what
and How to do.
-> No Titles are allowed. All are developers on
the team.
-> No sub-teams can be created.
-> They stay accountable to work on the
Sprint Items.
-> Development Team is responsible for
tasking and providing the estimates.
36. How to do Story estimation ?
Once you have your backlog of items, it’s
important to estimate the time or effort it will
take to complete each item (user story).
37. Team capacity ?
Your team’s capacity is a measurement of
how many story points or backlog items they
can complete during a sprint under normal
circumstances. To find your team’s capacity,
multiply the number of team members by the

Prepared by Amaravathi Pokala- Quality Thought

 15

number of hours they can productively work

in a day.
38. What is the difference between agile and
scrum?
Agile is one of the sdlc methodologies with
constant increments and iterations, whereas
scrum is one of the process or framework
which implements agile.

39. Why scrum compared to other frame

works ?
Scrum…

 Can be implemented easily

 Works for both simple and complex projects
effectively
 Aids in providing fast response to changing
requirements
 Ensures customer satisfaction and employee
satisfaction
 Promotes flexibility and adaptability
 Reduces time to market
 Motivates team members and gives them a
sense of satisfaction

Prepared by Amaravathi Pokala- Quality Thought

 16

40. What are benifts of agile methodology

for testing ?
Agile testing improves product quality and
enables development teams to release
software on shorter cycles. And effective test
case management helps Agile testers.

You’ll find and fix errors faster. So, you’ll

lower the risk of finding a bug at the very end
of testing — and missing a deadline.

You’ll make customers happy by delivering

regular releases. So, you’ll improve customer
retention rates.

And you’ll manage the scope of each release.

That helps you prioritize features for each
iteration and deliver the most important ones
first.

Prepared by Amaravathi Pokala- Quality Thought

 17

Prepared by Amaravathi Pokala- Quality Thought