Agile Methodology

In V module once requirement is finalized > development Team focuses on the product
development
Also known as planned driven methodology

Where as in agile module,

Requirement are changes frequently, so it is not planned driven

In Agile, customer request for change in requirement at any point of development stage

Customer can request for change at any stage

DIT - SIT – UAT - production

This change in the requirement do not affect development of any other module

Customer does not have to pay extra money for CR

If any CR(change request) / RFC comes at any time so we will accept & we can’t apply any extra
charge

If any CR(change request) / RFC from client, it don’t impact on deployment Or Testing OR
production

1. If impact is more then we will inform to client.

2. If impact is less then we will development & do testing and deploy to client

Agile delivery/ deployment duration of  2 week or 3 week

It is a value driven methodology (Priority for Client) & Module driven methodology

In agile method, project is divided into number of modules/phases & releases

Release I Release II Release III

 V Module Agile Methodology
Customer Stake Holder

BA Product /Project Owner

BRS Product Backlog

SRS Sprint Backlog

Functional Requirement / Use Cases User Stories

Release Sprint

Project manager Scrum master

Extra money No extra money

In Agile requirements are not planned if any change in request occurs it can be fulfilled
i.e. It’s not planned driven methodology

 Agile will contains different modules or Agile has subtypes/ methodology/frameworks

1. Kanban - Support team
2. Lean - Support team
3. XP - Extreme programming(only development)
4. Scrum - Sprint wise delivery to client with 2 week (Sprint 1)
5. FDD - Feature driven development
 I have worked in Scrum Agile methodology

Agile will contains different modules/Agile Type /Agile Frameworks/Flavor

Kanban Support Team

Lean Support Team

Scrum Project Team

XP Project Team
FDD Project Team
Architecture of Agile Methodology

Stake Holder

Project Owner

Product Backlog

Estimation

Sprint Backlog

User Stories

Test Case Design

Maintenance/ Support
1. Stake Holder

Stake holder – is Client/ Customer

They came with / have bunch of requirements
In Agile methodology stack holder is nothing but customer & he is the member of top most
body of company
At any phase – Development/ Testing/ production they can request for change in requirements

Eg. E comers site

application Amazon

2. Product Owner

Project owner gather requirements from Stake holder

He collects requirements from stake holder & prepare product backlog
Project owner is responsible for creating product backlog
Also, Project owner is team member of sprint planning meeting

3. Product Backlog

In the product backlog total requirements of entire product/ Application gathered

together

Receives list of requirements from product owner sent by the Stake Holder

It includes requirements of all modules

4. Estimation

Estimation converts Product backlog to sprint backlog=20/25

In agile module we focus on module-based release / delivery
So, once we get all requirements- it is not related to any one specific module
Estimation means sorting of requirements for development

Estimation – It is a process to check how we can deal with problems when obstacle occurs
1. Estimation of number phases / modules in the projects-200
So, we can assign number of developers & Testers according to that

2. Priority based module---15 & 45

Depends on client’s requirement

3. Estimation is one kind of parameter of sprint planning meeting

Peoples involved
Project owner
Development lead
Test Lead

Main Factors in Estimation

1. Knowledge
2. Efforts
3. Complexity

1. Knowledge
Checked knowledge of project domain
Once Team formation is done – each member of team should have knowledge of
project domain
Experienced or non-experienced – so how he can deal with project

2. Efforts
Here authority decides how much efforts are required for this project,
& according to that how much resources we are required
Selection of modules & user stories

Example
10 Modules: 15 D & 5 T = Low & Low
100 Modules 15 D&5 T = High & High
 3. Complexity

Harder to design – Modules

Less resource allocation
Communication Bet DEV & Tester is less
Communication Bet DEV & BA is less – Then execution of task critical challenge

Complexity of project measures in Terms of – Time, Cost & Resources

5. Sprint backlog

Sprint backlog means – User stories of modules

Modules > User stories > PO-Product owner/project
owner
Project owner decides & creates User stories
Sprint Backlog – User stories – It contains detailed information of requirement

Which we are required while development

6. User stories

This is nothing but functional requirements

User stories decided/divided into estimation phase
Whenever stake holder gives requirements to product owner this are requirement for all
product
In estimation – spring planning meeting members decided which modules are to be
developed & what are the requirements
Sprint – 1,2 3 & 4 week

Rally tool/Jira Tool

SH-CR-BA-Rally tool-Enter CR-Visible to all the team-dev/test

We use JIRA tool in our organization

User stories consist of-pdf

Description Criteria – Description about user stories & desired output

Acceptance Criteria – Preparing scenarios to generate desired output
7. Test cases design
According to user stories test cases designed by tester

Test cases are mapped with user stores

Agile People-

Client  Stake holder

Deliver manager Solution Master
Project manager  Scrum master
Business Annalist  Product Owner
Designer  Designer
Developer  Developer
Tester Tester

Agile meeting/ Agile Ceremonies-

In Agile meeting we have different meeting

a. Grooming meeting

b. Sprint planning meeting

c. Scrum meeting/ Daily stand meeting/Scrum Call

d. Sprint review meeting/Sprint Demo

e. Retrospective meeting
1. Grooming Meeting:

1. Grooming session conducted before the start of sprint

2. Purpose – To understand User stores / functional requirements of

customer

What is the objective of project?

Shares essential information about project

BA gives some important guideline to DL & TT – for Developing & Testing Activity

3. People involved in grooming – Product owner or BA, Design Team, Development Team,

Testing Team

4. Duration – 30 Min to 60 Min

2. Sprint planning meeting

Scrum master conducted Sprint planning meeting on 1st day of Sprint

People involved – Product owner or BA, Design Team, Development Team,Testing

Team

Once Detailed information about user stories are gathered by product owner or BA –

Scrum master – allocate work & user stories in Team

Scrum master allocate work & user stories in Team as per the requirement & priorityto DL

& TL

Ask for the estimation – Task & Hours Calculation /

Day – 8hrs / week – 40 Hrs

Once sprint planning is done – scrum master monitor every activity on daily basis

Duration – 30 Min to 60 Min

3. Scrum Meeting

It is known as every day status call orEvery

day standup call

People involved – Scrum Master,

DevelopmentTeam,

Testing Team

Scrum master is chairperson of the standup call

Every day standup is taken – discussion about projects, Daily Development activity,

testing activity

Duration – 15-30 Min

Timing – 10 Am to 10.30 Am

Topic discussed –

1. What we did yesterday? 15day 15day

2. What we did today?

3. Discussion about any blocker?

Agenda – Discuss progress of project

4. Sprint Review Meeting –

SPRINT review meeting conducted on last day of sprint

People involved – Product owner or BA, SM, Design Team, Development Team, TestingTeam

Duration – 30 min 60 Min

Team prepares the demo about application or product and delivered to product owner or

Client

Cross checks the requirements & put some additional change or suggestions

Taking review to check completeness & correctness of product as per customer’s

requirements

5. Sprint Retrospective Meeting

Conducted by Scrum master on last day of sprint

Scrum master, Development Team, Testing Team are the part of this meeting

Duration – 30 min 60 Min

Discussion about:

What went well – Good? What

not went well bad?

What are the action plans – for module?

Feedback?

This meeting helps to avoid

 Agile Meeting Purpose Involved

Grooming meeting - US / requirement doubt/ Clarity 1hr – BA, Developer,

( Any time- 2week) understand Testing team, Designer, PM
(Before start of Sprint) (optional)
Sprint planning meeting - Current sprint = 20 US added / 30 min/ 1hr – PM,
(1 times – Stat day of work decide  PM, BA & Developer, Testing team,
sprint) (1 Sprint - 2week) Designer Designer, BA
- Estimation provide
Ex. 1US = developer (14hr) +
Tester (10hr)  total = 24h
Daily stand up meeting/ - What you have done yesterday 15 min – PM, BA,
Scrum meeting - What are you doing today Developer, Testing team,
(Daily – 10 am to 10.15am) - Issue/ roadblock Designer
Sprint review meeting - US tester  Tester demo/ review 1hr – Client/ UAT / BA,
to Client/ UAT / BA Developer, Testing team,
(1 times – End day of Designer, PM
sprint)
Sprint retrospective - Current sprint (Sprint 1  2 week 30 min- PM, Developer,
meeting complete)  Sprint 2 work Testing team, Designer, BA
(1 times – End day sprint)
Good & Bad things discuses

Advantages of Agile M –

1. Check points

Every Application/Product having main modules & under Main modules there are number of

submodules

In V module – If defect found in Production phase – Post mortem Testing > which is not feasible

always > Time

Where as In Agile M – after every module there are some check points > so if any defect occurs at

any stage or production stage > in Agile we check , check points not doing PM Testing
Developers click on check points – Code appears for defect code in red color

Avas Tool used by Tester for check points

2. Scrum Meeting

3. Implementation of Automation

We can implement automation in agile Methodology

Now a days 70 % manual 30% automation Testing

Selenium – main Tool for Automation

Advantages –

High Accuracy | Less human resource | Less Time | less cost

4. Sprint wise delivery

Module wise, priority wise delivery is possible in Agile Methodology

In V – Module

Project Duration = 3 months

1 Release = 3 months

3 months = 5 to 6 modules

1 Year = 4 release

In Agile Methodology

1 Release = 1 months or 1 Sprint

1 month = 1 to 2 modules

1 Year = 12 release

Sprint wise delivery so value driven methodology

Last movement CR is excepted & fulfilled

Dis-Advantages of Agile-

 To implement new module in previously developed software, developer & tester should have
a total knowledge about flow of software, scenarios, dependencies & relationship of the
module.

 If developer & tester have knowledge of all this then they can work in agile.
Agile Daily wise plane-

 Project team size – 18 peoples (10 Developer + 4 Tester)

 Agile duration for deployment/ delivery = 2week (5 * 2 = 10 days) (Mon to Friday)
 1 Team = Recharge module  3 developer + 1 Tester
 2 Team = Electricity module  2 developer + 1 Tester
 3 Team = Invest in stock module  3 developer + 1 Tester
 4 Team = Rent module  2 developer + 1 Tester
 Scrum agile  Sprint 1 wise delivery = 18 US  (4 US – assignee 3 Team)

1 Week -
Monday (Start day of Sprint)-
 Grooming meeting (30 min) – US doubt celerity
 Sprint Planning meeting (30min) –
1. Sprint 1 = 18 US  Assignee work/ Task to developer + Tester (4US)
2. Estimation = 1US – Developer (14hr) + Tester (10hr)
2US – Developer (16hr) + Tester (12hr), etc
 1US  3Developer – 1US coding- In-Progress + Tester – 1US TCD (5/6hr)- Complete

Tuesdays-
 Daily stand up meeting(15 min)-
1. What you have yesterday (1US – TCD- Complete)
2. What are you doing today (1US – TCE)
3. Issue/ roadblock
 1/2US  3Developer –1US coding(2hr)- Complete – Build sent for 1US, 2US- Coding -
In-Progress + Tester – 1US TCE (7/8hr)- Complete

Wednesday-
 Daily stand up meeting(15 min)-
1. What you have yesterday (1US – TCE- Complete)
2. What are you doing today (2US – TCD)
3. Issue/ roadblock
  2US  3Developer – 2US- Coding(7/8hr) - Complete + Tester – 2US TCD (5/6hr)-
Complete

Thursday-
 Daily stand up meeting(15 min)-
1. What you have yesterday (2US – TCD- Complete)
2. What are you doing today (2US – TCE)
3. Issue/ roadblock
 2/3US  3Developer – 2US- Build sent to tester, 3US – coding (4/5hr)- In-Progress +
Tester – 2US TCE (7/8hr)- Complete

Friday-
 Daily stand up meeting(15 min)-
1. What you have yesterday (2US – TCE- Complete)
2. What are you doing today (3US – TCD)
3. Issue/ roadblock
 3US  3Developer- 3US – coding (4/5hr)- In-Progress + Tester – 3US TCD (4/5hr)-
In-Progress

2 week –
Monday-
 Daily stand up meeting(15 min)-
1. What you have yesterday (3US – TCD- In-progress)
2. What are you doing today (3US – TCD- Complete + 3US - TCE)
3. Issue/ roadblock

 3US  3Developer- 3US – coding (3hr)- Complete- Build Sent, 4US - coding (3hr)- In-
Progress+ Tester – 3US TCD (2hr)- Complete, 3US – TCE (4/5)- In-Progress
 3US – TCE ( 2defects)- Defect we will inform to developer + Developer will fix defects
(2/3hr) + Tester will check defects(2 defects) (2/3hr) - Complete
Tuesday-
 Daily stand up meeting(15 min)-
1. What you have yesterday (3US-TCD-Complete, 3US- TCE- In-progress, 2 defect)
2. What are you doing today (3US – remaining TCE)
3. Issue/ roadblock

 3/4US  3Developer- 4US - coding (5/6hr)- In- Progress+ Tester – 3US TCE (4/5hr)-
Complete

Wednesday-
 Daily stand up meeting(15 min)-
1. What you have yesterday (3US- TCE- Complete)
2. What are you doing today (4US – TCD)
3. Issue/ roadblock

 4US  3Developer- 4US - coding (5/6hr)- Complete + Tester – 4US TCD (5/6hr)-
Complete

Thursday-
 Daily stand up meeting(15 min)-
1. What you have yesterday (4US- TCD- Complete)
2. What are you doing today (4US – TCE)
3. Issue/ roadblock

 4US  3Developer- 4US - coding (1hr)- Build sent + Tester – 4US TCE (4/5hr)-
 Tester 4US – TCE – found 7 defect  Tester will inform to developer  Developer
defect - 1to 5 fixed & developer say defect no. 6 to 7 is not valid (Developer not
accepting defects) + Tester will check/testing defect 1 to 5 –has been Testing (3hr)
Friday (Last day of Sprint)-
 Daily stand up meeting(15 min)-
1. What you have yesterday (4US- TCE- In-Progress, 7 defects, 5 defect -test)
2. What are you doing today (4US – Remaining TCE)
3. Issue/ roadblock (Developer is not accepting defect 6 and 7)

 4US  3Developer- 4US – Defect fix (2/3hr) + Tester – 4US TCE (3/4hr)- Completed,
Defect 5 to 7 check /testing(1hr) – working/ fix - Completed

 Sprint review meeting(1hr)-

1. Tester 4US test – 4US Demo to Client/ UAT/ BA

 Sprint retrospective meeting (30min)

1. Current Sprint (Sprint 1)- Good & Bad discussion

Agile Term-
 Burn Down Chat- These graph that defines how much work will be remaining w. r. t
date/time
 Burn up Chat - These graph that defines how much work will be completed w. r. t
date/time
 EPIC- Main module which contains multiple User story in it
 Ex. Paytm- Recharge Module – 30 US to 35 US
 Velocity- Velocity term defines how much US we are deploying or delivering to client
w.r.t Sprint
 Estimation/ Story point- Estimation is defines time span of every US, How much time
will required for development & for testing.
 Estimation will be decide by using the Voting method
 In my project, SM, PO & designer will roughly estimation / Story point to every US.
 In Sprint planning meeting, If estimation want to change then I will talk with SM
 While giving the estimation which parameter will be considered,
1. How much knowledge, we have about the US
2. How to complex for Testing
3. How much effort will be required