Developer Tasks
                Under Standing Requirements
                Design
                Coding
                Unit Testing
                Integration Testing
                Code Review
                Bug Fixes
                Team Meetings
 
QA Task
                  Under Standing Requirements
                  Writing Test Scenarios
                  Writing Test Cases
                  Test Case Reviews
                  Test Data Preparation
                  Test Environment Setup
                  Test Execution
                  Re-Testing Bugs
                  Team Meetings
                  Automation
 

Agile Model:

        In An Agile model is a Big project divided into modules, then each module further divided into Smaller components then this Small component will be Implemented In short schedules called Sprints.

           A big project divided into modules first.



  
 
 

 
 Advantages of Agile Model:                                                                                           

v  Agile model guarantee more customer satisfaction by rapid on continues delivery of usable product to the Client.

v  Agile model saves time and money because of less documentation.

v  Daily meeting with the team members and clients results in better product.

Agile Model Terminology:

Scrum:

           A Scrum is the most popular Agile development model where developers and testers work together as a team under the guidelines of Scrum Master.

Scrum Master:

            A Senior person the Lead or Manager who manages entire team is called Scrum Master.

Product Owner:

            Business Analyst finalizes product requirements it’s called Product Owner.

Product Backlog:

            A Product backlog is a list of requirements on features plan to implement in the Product.

 A Product Backlog contains an Epics and User Stories.

Epic: A major Business requirement is called an Epic.

User Stories: A feature to be implemented is called User Stories.

Task: A Planned work Item is called Task.

  Example for Epic, User stories and Task.
 
 
 

JIRA

  • JIRA Introduction
  • How to Install JIRA
  • JIRA Features
  • Creating Scrum Project in JIRA
  • Adding Users to our JIRA Account
  • JIRA Issue types
  • Workflow for a Project
  • Creating Product backlog in JIRA
  • Creating EPICS in JIRA
  • Creating User Stories in JIRA
  • Starting Sprint
  • Writing Test Cases in JIRA
  • Executing Test Cases from JIRA
  • Adding Bugs to the JIRA Project
  • Attaching screenshots of defects in JIRA



JIRA :
        Jira is a cloud based project management tool used by Agil teams Introduced by Atlassion company.
 
Jira is a project management tool used for tracking issues, bugs, and managing tasks, widely adopted in Agile methodologies.    
 
 
JIRA is a versatile tool used for bug tracking, issue tracking, and project management. When it comes to testing, JIRA can be particularly useful for managing test cases and test notes. Here are some key points:
 
Using JIRA for Testing:

1.Test Case Management: JIRA allows you to create,organize, and manage test cases.You can define requirements and test cases directly within JIRA, ensuring that QA and development teams share visibility into a single testing record.

2.Writing Test Notes: You can write test notes to user stories in JIRA. This involves explicitly thinking about testing during sprint planning and documenting test notes for each story.

3.Best Practices: To effectively manage test cases in JIRA, it's recommended to configure your JIRA workflow, use add-ons or external integrations with dedicated test management tools, and follow best practices for writing and managing test cases.

JIRA Workflow:
 
 
     Step1: Scrum Master creates jira Account
                      Login to JIRA
                      Creates New project then invite other team members to access the project.
    Step2: Product Owner(Business Analyst)
                      Login to Jira
                      Creates Product Backlog with Epics and Stories.
    Step3: Scrum master define Tasks then assign to developers and Testers then the Start                       Sprint.
    Step4: Developers, Testers carry out assigned task items then update task status in Jira                        board.
    Step5: If Tasks completed, Scrum Master Stop Sprint.