Agile methods are a family of development processes, not a single approach to software development. Agile follows ‘adaptive’ planning rather than ‘predictive’ planning in conventional Waterfall Process.

• Customer satisfaction by rapid, continuous delivery of useful software.
• Working software is delivered frequently (weeks rather than months)
• Working software is the principal measure of progress.
• Even late changes in requirements are welcomed.
• Close, daily, cooperation between business people and developers
• Face-to-face conversation is the best form of communication.
• Projects are built around motivated individuals, who should be trusted
• Continuous attention to technical excellence and good design.
• Simplicity
• Self-organizing teams
• Regular adaptation to changing circumstances

Before going to the People Challenges, I would like to reiterate Few Useful Points on Role of Software Testers:
– Testing is finally recognized as a profession which needs specialized skills set and qualifications. – Also it is convinced testing will not start once the development is completed.
– Testing needs to be start in every stage of the software development Life Cycle.
– Testers need to validate whether the requirements specification documents is developed based on the needs of the organization.

– Testers need to be ensuring that the design documents developed based on the requirements specifications.
– Testers need to be ensure that the test cases and test plan are created based on the requirements specifications.
– Testers need to be ensuring that the defects need to find out before the test cycle starts so that the cost spends will gradually decreases.
– Testers need to be ensuring that the defects can be reproducible by developers.
– Testers need to be ensuring that they are finding defects of the high priority scenarios first.
– If you are in Agile methodology, then testers need to make sure that defects are getting fixed on priority.
– Finding out defects in the later stage of the product will leads the cost spend to rectify the defects is very costly.

The top 10 people challenges have been identified:

• Training in Testing
• Good Relationship with Developers.
• Good Relationship with Customers.
• Managers need to understand about testing. [Think – Do your Company has Culture of Testing?]
• Using of Tools.
• Time on Testing
• Fighting a lose-lose situation
1. Having to say No
• Testing “Over the wall” Software
1. Having to say “no”

[Update: April Fools! Gmail Motion doesn’t actually exist. its merely an April Fools prank from Google]

How it works

Gmail Motion uses your computer’s built-in webcam and Google’s patented spatial tracking technology to detect your movements and translate them into meaningful characters and commands. Movements are designed to be simple and intuitive for people of all skill levels.

Motion Guide

Familiarize yourself with some of the basic functionality of Gmail Motion using this printable guide of sample gestures. With it, you’ll be able to start writing and responding to emails

Try Gmail Motion Here – http://mail.google.com/mail/help/motion.html

This is a very useful book for Load Test Professionals and for developers. This guide shows you an end-to-end approach for implementing performance testing. Whether you are new to performance testing, or looking for ways to improve your current performance testing approach, you will find insights that you can tailor for your specific scenarios.

This guide is related to our Performance Testing Guidance Project. – J.D. Meier, Carlos Farre, Prashant Bansode, Scott Barber, Dennis Rea

Download the Guide/Ebook

Start using the guide today, while we continue to make improvements.

• Download the Performance Testing Guidance for Web Applications Guide

Parts

• Part 1, Introduction to Performance Testing
• Part II, Exemplar Performance Testing Approaches
• Part III, Identify the Test Environment
• Part IV, Identify Performance Acceptance Criteria
• Part V, Plan and Design Tests
• Part VI, Execute Tests
• Part VII, Analyze Results and Report
• Part VIII, Performance Testing Techniques

Chapters

• Introduction

Part 1, Introduction to Performance Testing

• Chapter 1 – Fundamentals of Web Application Performance Testing
• Chapter 2 – Types of Performance Testing
• Chapter 3 – Risks Addressed Through Performance Testing

Part II, Exemplar Performance Testing Approaches

• Chapter 4 – Web Application Performance Testing Core Activities
• Chapter 5 – Coordinating Performance Testing with an Iteration-Based Process
• Chapter 6 – Managing an Agile Performance Test Cycle
• Chapter 7 – Managing the Performance Test Cycle in a Regulated (CMMI) Environment

Part III, Identify the Test Environment

• Chapter 8 – Evaluating Systems to Increase Performance-Testing Effectiveness

Part IV, Identify Performance Acceptance Criteria

• Chapter 9 – Determining Performance Testing Objectives
• Chapter 10 – Quantifying End-User Response Time Goals
• Chapter 11 – Consolidating Various Types of Performance Acceptance Criteria

Part V, Plan and Design Tests

• Chapter 12 – Modelling Application Usage
• Chapter 13 – Determining Individual User Data and Variances

Part VI, Execute Tests

• Chapter 14 – Test Execution

Part VII, Analyze Results and Report

• Chapter 15 – Key Mathematic Principles for Performance Testers
• Chapter 16 – Performance Test Reporting Fundamentals

Part VIII, Performance-Testing Techniques

• Chapter 17 – Load-Testing Web Applications
• Chapter 18 – Stress-Testing Web Applications

Download the Guide/Ebook

Start using the guide today, while we continue to make improvements.
• Download the Performance Testing Guidance for Web Applications Guide