Agile Methodology explained by real time experienced. Agile Testing methodology, process, challenges are explained in this tutorial with live examples.

1. Job Oriented - Instructor Led - Face2Face-True Live Online I.T. Training for Everyone Worldwide
http://www.H2KINFOSYS.com || Training@H2KInfosys.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
Agile Methodology
What is Agile methodology?
 Agile methodology has Customer or Client as part of theirteam.
 In this type the whole product or the application is divided or categorizedintovarious modules, and eachmodule is
developed and tested and delivered in increments hence it is also termedto be incremental model.
 After eachmodule is developed and testedit gains feedback from the client and only when the client is satisfied it
moves on to next module.
 It has different approaches extremeprogramming, SCRUM, etcalways extremeprogramming is used (Below is all
about extremeprogramming)
How Agile is processed:
 It starts up initially with therequirements phase, in this phase all therequirements are gatheredfrom theclient.

2. Job Oriented - Instructor Led - Face2Face-True Live Online I.T. Training for Everyone Worldwide
http://www.H2KINFOSYS.com || Training@H2KInfosys.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
 After gathering the requirements teamstartsdiscussing about the Scope of the project which means what we are
going to do, how we aregoing to start etc.
 After discussing they categorizethefunctionality and breaks thewhole application into several modules.
 Once the module is decided, the Development teamstartswriting thecodes and develops the particular
application, in the project environment(Please scroll down toknow the definition)
 After themodule is been developed, QA teamstartstesting themodule, if they find any issues they report it to Dev
teamand fix theissues before releasing it to client
 Once testing part is successful it is implemented on real time environment and delivered to theclient.
 After it is been delivered to client, Client has theirexclusive QA team who does theirtesting, and let the company
knows if they haveany issues, or if they need any modifications.
 Once the customer is satisfied with that particularmodule that particularmodule is signed-off(Client is satisfied
hence closing that module work) and we will move on to next module.
 If client is not satisfied we will work on same module until he says OK.
Features:
o Eachmodule separateuser story, the requirements in Agileis termedto User story.
o Eachmodule is considered to be separateproject.
o Developer and tester work in pairs for e.g. one developer writescodes and other verifies it, in similar wayone
tester writes test case and other reviews it and execute it.
When do we use Agile:
 When the customer does not have a clear understanding of the details of the new system. The developers
interact continuously with the customer, delivering small pieces of the application to the customer for
feedback, and taking corrective action as necessary.
 When the technology used to develop the system is new compared to other technologies. Frequent test
cycles
 in Extreme Programming mitigate the risk of incompatibility with other existing systems.
 When you can afford to create automated unit and functional tests. In some situations, you may need to
change the system design so that each module can be tested in isolation using automated unit tests.
 When the team size is not very large (usually 2 to 12 people). Extreme Programming is successful in part
because it requires close team interaction and working in pairs. A large team would have difficulty in
communicating efficiently at a fast pace. However, large teams have used Extreme Programming
successfully.
User Story:
A user story is a short, simple description of a featuretold from theperspective of the person who desires the new
capability, usually a user or customer of the system.
For Example: User story for login describes
A user needs tologin to pay their bills online so that it makes easy mode of payment.
 Login appears in the right corner of the page.
 Login page looks something like this.

3. Job Oriented - Instructor Led - Face2Face-True Live Online I.T. Training for Everyone Worldwide
http://www.H2KINFOSYS.com || Training@H2KInfosys.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
Example of Agile:
ABC Bank is the client who needs customer to login and view their account summary. It is giving this
project
to H2k Infosys Company.
The requirements of this project are as follows:
1. Customer should login with valid username and password.
2. After logging in he has links called account summary, funds transfer, receivefunds, pay credit cardbills, etc
3. He cantransfer $ 10000 per day.
4. He canreceive $5000 per day.
User story for Login:
1. User Name: It should be alpha numeric containing one alphabet and numbers
2. Password :
 It should be case sensitive
 It should contain one higher case, one special character, oneor more lower case, one more number.
 It should be minimum of 6 values and max of 10
Module:
After categorizing, since each performs different functionality each will be considered as modules. In this ABC
Bank the modules will be
 Login
 View summary
 Transfer
 Pay Bills
 Receive
 In this first login login is createdand testedin project environment i.e dummy environment and after testing is
done and making sure login is working fine, meeting all the requirements, all the scenarios mentioned in User story
passes, then it is implemented on realtime environment.
 After this process H2k will deliver this particularmodule to ABC Bankand gains feedback and make it sure whether
they aresatisfied.
 Once the customer is satisfied the LOGINmodule is finalized and move on next module accounts summary.
What is Dummy / QA TEST environment or / TEST BED/ project environmentand what is Real time environment?

4. Job Oriented - Instructor Led - Face2Face-True Live Online I.T. Training for Everyone Worldwide
http://www.H2KINFOSYS.com || Training@H2KInfosys.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
Dummy / QA / TEST BED or Project environment which will be virtual application for example if it is a
WWW.ATT.COM website, we have the virtual website of ATT like www.alpha1.att.com which has the exact
functionality and features that real ATT.com is having.
Why do we need a Dummy Environment?
Let us take an example like, ATT client is now serving with IPHONE4 connection, and in the next few months it
needs IPHONE4S information to be added in their website including features about phone, how to take new
connection etc .
Now the ATT client gives this project to XYZ Company.
Now let us assume if this XYZ Company does not have a project environment and works directly on
WWW.ATT.COM website and makes some alterations in the existing website.
Here if something goes wrong while writing codes to this IPHONE 4S information available on this website and if
that code changes corrupts the entire system and results in when we www.att.com it displays error “ Sorry the
server is down”.
In this scenario in affects the entire environment and disables the existing user to use that website until this issue
this fixed.
To avoid this situations we use Dummy or QA project environment, so that we will make sure that this changes is
working good and do not affect existing application.
Difference between Waterfall, V-Model, Agile
Waterfall:
After theapplication is developed on realtime environment the testing phase starts.
There exists only one Test design for whole project.
No changes can be made if customer requires it in future.
V-Model:
In V-Model, thewhole application is divided into modules and each module has separatetest design.
After eachis eachmodule is testedand next module is created.
After next module is createdthis module and previous module is integrated, after integrating allthemodules the
whole the application is tested and implemented on real time and testedfor acceptancei.etesting as real timeuser
Agile:
The whole application is divided into modules.
Eachmodule is developed and tested, each module is implemented separately on real timeand gain feedback from
customers and once attaining customer satisfaction wemove on next module development.
Register for FREE DEMO Class
http://www.h2kinfsoys.com
Email: h2kinfsoys@gmail.com
US: 770 777 1269
UK: 020 3371 7615