TESTINGMANTRA - BLOG
Blog
Testing Types
Usability Testing
Smoke Testing
Load Testing
Stress Testing
Domain Testing
Exploratory Testing
Recovery Testing
Scenario Testing
Regression Testing
User Acceptance Testing
Alpha Testing
Beta Testing
Unit Testing
Static & Dynamic Analysis Testing
Functional Testing
Ad-hoc Testing
Volume Testing
System Testing
Sanity Testing
Black Box Testing
Interoperability Testing
Volume Testing Techniques
Gray Box Testing
White Box testing
Articals
Agile Development
Coverage Criteria for GUI Testing
Release Life Cycle
Quality Concept
TQM - Total Quality Management
When are the Test Plan written
Unit Testing Advantages & Techniques
Classification of Defect
Requirement Testing Techniques
When is Testing Complete?
Quantative Project Management
Software Configuration Management
When to use Regression Testing?
V-Model Concept of Testing
Activity of Software Test Engineer
Risk Management
Sanity Testing A Overview
Website Security Smoke Test Template
Software Testing Techniques
Requirements & Specifications
Traceability Matrix
Test Plan - Objectives and Benefits
Agile Testing - Master the new game
Testing Vocabulary
SQL Tutorial
Test Strategy
Error Handling Testing
SDLC - Concept
Steps of Software Testing Life Cycle
Why to use Metrics?
Defect Tracking
SyncML
Mobile Testing
GSM Basic
Cellular Network Architecture
Mobile Communication Overview
Mobile & handheld usability testing
Why Mobile Testing is different
True BREW Testing
VOIP Testing
SIP Testing - An overview
SIP Messages
Structure of SIP Protocol
SIP Important terms
SDLC Model
Software Development Life Cycle
Waterfall model
Spiral Model
V-Model
Iterative Model
Big Bang Model
RAD Model
Prototype Model
SOFTWARE TESTING
Test Plan
Test Case & Test Design techniques
Templates
Software Project Template
Software Testing Template
Automated Testing Tools
QTP
Winrunner
JUnit
Selenium IDE
LoadRunner
JMeter
Estimation Techniques
Using Use Case Points
Quick Estimation Technique
Testing Estimation Process
Certifications
CSQA
CSTE
                                                                                                                                                                  Usability Testing      Smoke Testing      Load Testing      Stress Testing      Domain Testing      Exploratort Testing       Recovery Testing      Scenario Testing      Regression Testing      User Acceptance Testing      Alpha Testing      Beta Testing      Unit Testing      Static & Dynamic Analysis Testing                                                                                             







Share
Follow us at Twitter
Follow us at Facebook
Share
Agile development is a software development method in which the software is developed in short timeboxes. Each timebox is called as Sprint. Each sprint is usually 30 days. Small feature or small change will be developed in each sprint. We have to plan the sprint activities at the start of the sprint. Also before exiting each sprint, new code has gone through some testing.
A small team of people will be working on a specific features only. Each team consists of atleast 1 Project Manager, 1 Developer, 1 Tester. One of them will be assigned as a virtual Feature Team Manager. They will build the feature seperately. And the feature will be merged into the Main only if the developed feature is stable. It is not necessary for a team member to work on the same feature. Once they are done, they can move on to another feature team.

  Pros of Feature Team:

       - Clear PM, Dev, Tester ownership on each feature
       - Quick turnaround(Once the feature is completed, cant go back)
       - Bugs are found earlier
       - Main build unlikely be destabilized too long
       - Alpha/Beta builds are ready very early

  Cons of Feature Team:

       - It is difficult for the direct manager to evaluate performance
       - Since we can move to another feature once we completed, it is hard if any failure occurs in our previous feature.

Scrum meeting:

There will be a daily meeting called the scrum meeting where the team members will meet. The scrum meeting should be held daily and it is usually not more than 15 mins. They have to make quick decision on everything.

Eg: This requires a change of spec, can we do that?
      I finish early, What should I do to help? 
      I cant finish writing all P2, P3 test cases. can I move them to next sprint?
The meeting go around with each person saying:

      1. What they have done since last meeting?
      2. What they are working on?
      3. Are they blocked by other work or anything?

A person will be assigned as a scrum master. The scrum master have to make sure that discussion does not take too long. And the scrum master will update the scrum tools like task-estimation and product backlog.
Pros of Agile development:

      - Not so far to ship at anytime since atlease a single feature is developed in every sprint
        - Easier to estimate what can be achieved since each sprint is a short period
        - Regression bugs can be found immediately
        - Less duplicated work to waste
        - Constant communication in the group because of the scrum meeting
        - More collaboration and better morale
        - Higher productivity
        - Less big surprises
        - Take changes efficiently

Cons of Agile development:

        - Difficult to determine the shipping date ahead
        - May be caught in infinite sprint loops
        - No clear requirement, design or test spec
        - Product backlog can grow too big
        - Lower priority to develop test automation
        - Need to allocate time for System testing
        - Need to break down big feature. It will be complicated to develop the big feature in a single sprint
        - Difficult to apply in V1 (Version 1)
 
 
Comparison between Waterfall and Agile method:

        Waterfall:
          
                 - More planning. Will plan for the entire period
                 - Develop big features at a time
                 - Long shipping cycle
                 - Milestones set from planning to ship
                 - More features or work got wasted some times
                 - Customers pay a lot during upgrade
                 - Examples: MS Office(Earlier versions), Windows Vista
         Agile:
  
                 - Less planning. Will plan for every sprint
                 - Develop small changes
                 - Short shipping cycles (includes Alpha/Beta)
                 - Less but more realistic milestones set
                 - Less features or work got wasted sometimes
                 - Easy deployment and dont affect customers
                 - Example: MSN, Messenger, Web Applications like EBay, Amazon, Google.
Agile Development