Why?

In order to get clear picture on why to use Agile process, it is required to know what are the traditional software testing process and its drawback so that we will understand why Agile is preferred over them. Traditional software testing involved following process,

• Project Introduction

• Understanding Functional Requirements

• Creating Test Scenarios

• Creating Test Cases

• Test Execution

• Bug Reporting and Tracking

• Test Sign off

What is Agile?

Now let us learn what is Agile process and the terms used in this process, how to use this JIRA tool. So lets get Started,

Agile is an approach to software development under which requirements and solutions evolve through the collaborative effort of self-organizing and cross-functional teams and their customer/end user.Both development and testing activities are concurrent unlike the Waterfall model.

In a nutshell, Both Developers and Testers will be a part of a single team(i.e, Agile Team) working concurrently at the same time. Collaboration and Communication is import in Agile process.

Terminologies

EPIC - Defines basic requirements. These requirements are defined by the product owners.

STORY - Smaller requirements derived from the EPIC. This is will be usually be the customer needs or feature.

TASK - List of activities assigned between teams for completing the story.

Example :

Epic : As a user I need to use Online Banking Application

Story 1 : As a user I can Login into online banking application.

Dev Task : Review Story, Estimate Story, Design, Code and Unit Testing.

DevTest Task : Review Story, Test Cases, Test Environment, Execute Test and Report Bugs.

Story 2 : As a user I can check my balance in my account.

Dev Task : Review Story, Estimate Story, Design, Code and Unit Testing.

DevTest Task : Review Story, Test Cases, Test Environment, Execute Test and Report Bugs.

Agile Roles

Scrum Master :

• A Scrum master is the facilitator for an agile development team.

• Enable close cooperation across all roles and functions.

Product Owner :

• Getting requirements from the customers and stakeholders.

• Defines features and release dates and content.

• Prioritize features according to market value.

• Adjust features and priority every iteration, as needed

• Accept and reject work results.

Scrum Team :

• Developers and QA.

Definition of Ready (DOR) vs Definition of Done (DOD)

We will under what criteria whether the Story status is DOR or DOD.

DOR - Definition of Ready

• User Story is clear

• User Story is testable

• User Story is feasible

• User Story defined

• User Story Acceptance Criteria defined

• User Story dependencies identified

• User Story is sized for development

DOD - Definition of Done

• Code produced

• Built without error

• Deployed in test environment

• Tested successfully

• UAT passed and deployed.

The Agile : Scrum Framework

With the picture as a reference we will explain how projects in agile works, Inputs are received from Customers by Product owner with these inputs he creates Product backlog, these product backlog contains Epic, Story and Tasks. Based on Each or multiple stories a Sprint is started with a target dates and duration(usually 3 to 4 weeks).

If a new requirements arrive it can be added into the same sprint or move into the next sprint bucket named Sprint backlog. These evaluation is done based on Story point, Story point is noting but a number given to each story based on the time consuming and complexity to both develop and test. Scrum meeting is conducted every 24 hr of the sprint to ensure no blocker which will affect the sprint, and when work is finished product is reviewed and released.

Here is the short example on how a e-commerce will look if it follow Agile process.

Advantages of Agile Scrum

• We can save time and cost of the projects

• The quality can be ensured because each and every sprint will be tested multiple times.

• The requirements change can be accepted at any level of the project maintenance.

• All are participating in Scrum meeting so that transparency can be maintained.

• Each and every sprint we are delivering to the client so we can maintain the customer's satisfaction and we can avoid delivery risk of the projects.

Jira Tool

P