AGILE TRAINING ASSIGNMENT

1. How is Agile Testing methodology different from the other testing methodology. Also, what
are benefits if we opt for Agile Testing methodology.

Ans : One of the difference is that agile testing isn’t linear and sequential like other methodology,it
continues iteration of the development process and testing process.

- It is also known for its flexibility and its incremental approach.

- It is a flexible method which allows changes to be made in the project development according to
the requirements even if the initial planning is already been done.
- The agile testing team is interchangeable , which means the work is faster and there is no need
of project manger as the entire project is managed by the whole team .
BENEFITS 1) This type of testing method saves a lot of time and money
2) Reduces the cost of documentation. 3) Agile testing is highly flexible to any kind of changes .
4) Since the team is interchangeable there is determination of work and channel issues through
daily meetings being conducted .

2. What are the three points that are discussed in a Daily StandUp Meeting?
Ans : The three points which are discussed in the meetings are – a) What did the team do
yesterday? b) What are we going to do today ? c) Where there any blockers ?

3. Explain Product Backlog in Scrum? Also, who is responsible for prioritizing a Product Backlog?
Ans: Product backlog it is kind of sorted listed of all the products that we need and the only
source of product that demand changes . The product owner is only responsible for the content
and, availability of the product is termed as product backlog.
Scrum Product Backlog The items which are present in product backlog having higher ranking
are clearer and more specified than those with lower ranking. More accurate estimation
estimation of those items can be made on clearer contents and more detailed information.
In simple word , the lower the priority the items in the product backlog , the less details they are
.
- The Scrum is main person responsible for prioritizing the product backlog, but at the end it is
the development team that decides the priority list .

4. Define BurnDown Chart : It is the graphical representation of amount of work left to do versus
the time . The chart represents how much work has the team done , how much work is left ,
how much time is left, it basically helps us to visualize the entire project time frame required or
needed to complete the give work.
Lower the line of the chart the better the work is going (it means), it should never remain
constant , or the higher the line is means more danger and lot of work is still left to do .

5. Define the following terminologies -

a. User Stories: It is an informal language description of the features of a software system . It is
the starting point of any work and its purpose is to articulate how the work will be delivered too
the customer
b. Definition of Done: It is basically a shared understanding that the team has on a piece of work
that is to be completed . It is the agreed list of activity necessary to get a product increment
from done state to the end state .
c. Scrum Master: Is the one who facilitate scrum to a larger team by ensuring the scrum frame
work is followed.
d. Sprint Planning: It is the planning to define what can be delivered and how can that work be
achieved .
It is the estimated time span needed for getting things done say for example a QA team requires
medium time and developer team requires medium time , so we can conclude that the will
require medium time .
This type of process is called as T-shirt sizing which is of three types a)small b) medium c)large