You are on page 1of 32

AN OVERVIEW

Agile Methodology
Agile is Software Development Methodology that follows Iterative
approach, building and releasing Software incrementally from Start
of Project rather than delivering all at one. It involves planning a
development iteration, implementing work planned for iteration,
delivering a version of product at end. Feedback is used to plan
next iteration. And it continues until product is published. it allows
team to adapt to change requests as feedback comes early. These
changes can be kept in next iteration. The overall development is
adaptive and flexible.

2
About JIRA

JIRA is Work Management tool that helps you to manage projects, track
issues, and administer support. It is mainly used for Agile Project
Management and Bug/ Issue Tracking
It’s a software from Atlassian, an Australian company.
What can you do in JIRA?
Create Backlogs
Create Sprints
Create Tasks
Update Status on the Board
Manage Releases
Code Integration
Managing Workflows

*JIRA can be integrated with different 3rd party applications, Zoom, Zendesk, IT
Service Management etc.
JIRA Terminology
ISSUES Something that your organization needs to track.
• Any work item that requires an action. In JIRA, Epics, stories, Tasks, all are issues of different
types. Each issue has a Title, Desc, Due Date, Priority, Start Date etc.

PROJECTS Collection of Issues


• In JIRA, a Project is a collection of issues. It can be Software Development Project, Helpdesk
System etc.

WORKFLOWS Set of Statuses that an issue in a project can have


• It’s a set of statuses that an issue in a project can have along with the transitions between these
statuses. A simple workflow is- To Do-In Progress-Done
JIRA Workflow Stages
JIRA workflow has the following stages to track as soon as an issue is created −
• Open Issue − After creation, the issue is open and can be assigned to the assignee to start
working on it.

• In Progress Issue − The assignee has actively started to work on the issue.

• Resolved Issue − All sub-tasks and works of that Issue are completed. Now, the issue is
waiting to be verified by the reporter. If verification is successful, it will be closed or re-
opened, if any further changes are required.

• Reopened Issue − This issue was resolved previously, but the resolution was either
incorrect or missed a few things or some modifications are required. From Reopened stage,
issues are marked either as assigned or resolved.

• Close Issue − The issue is considered as finished; resolution is correct as of now. Closed
issues can be re-opened later based on the requirement.
JIRA Terminology
VERSIONS Set of features released together as a single update
• In Jira Software, versions represent points in time for a project. They help you to organize your work by
giving you milestones to aim for. You can assign issues in your Project to a specific version, and organize
your sprints around completing work in that version
Subcategory within a project that allows you to break down the project into smaller
COMPONENTS parts
• For Example-Interface, Database, API etc. Each issue will then belong to not only a Project, but a component
within that Project too.

OTHER AGILE TERMS


• Epic, Stories, Scrum, Sprint, Kanban, Backlog, Board…

• Stories, also called “user stories,” are short requirements or requests written from the perspective of
an end user.
• Epics are large bodies of work that can be broken down into a number of smaller tasks (called stories).
• Resolution: Field that JIRA uses to determine if its closed|Resolved|Unresolved; Status tells state of
issue with respect to workflow
Sample Project
Simple Project
Epic
As a customer, I want to pay for
my orders through online wallet

Story1 Story 2
As a customer, I want to pay for As a customer, I want to pay for
my orders through Paytm my orders through Phonepe

Task1 Task2 Task3

Add “Pay using online option” Integrate with Paytm API Integrate with Phonepe API
Creating JIRA Instance
Creating JIRA Instance

Follow Instructions…
Creating JIRA Instance
Creating JIRA Instance
JIRA User Interface and Navigation Bar

Apps -Add Plugins Settings


People Tab –To set up your teams
Dashboards (Page you can create to act as your control panel :
Default Dashboard/Create Dashboard using Gadget’s)
Filters (Allow you to save your searches: Advanced Issue Search)
Projects (Recent Projects/All Projects/Create Projects)

Your Work Tab (Assigned to me/Recent/Boards))

JIRA Home Page (Your Work is set as Home Page by default)


Grid Icon (Application Switcher-Switch to different App or different JIRA instance)
Switch to Standard Edition
Switch to Standard Edition
Settings
Atlassian Admin options are If you are not admin, you will get
available only if you are logged in Personal Settings options only
as admin.
Project Navigation Page

• Project Name
• Unique Project Key
• Project Type-Team managed (Next Gen) or Company managed (Classic)
• Project Settings… Workflows
Project Page
• Board Switcher-Multiple
Boards can be created for a
Project
• Roadmap
• Backlog
• Active Sprints
• Reports
• Issues
• Components-subsections of a
project. Use them to group
issues within a project into
smaller parts
• Code
• Releases-Versions help you
package and schedule project
deliveries.
• Pages
Issue Navigator

• Advanced Issue Search


• JQL
Agile Boards-Active Sprints

• Create
Board-Scrum/Kanban
• Create Board with
Sample Data
• 1 Project can have
multiple boards, 1
Board can live in 1
Project only
• Cards on Board-Issue
Type, Priority, Issue
Key, Assignee..
Agile Boards-Backlog

• Issues are arranged in


List view
• Sprints at top and
Backlog at bottom
• Versions and Epics
visible
Kanban Board

• Purpose of Kanban Board is to visualize work and ensure that there is


smooth flow of work from left to right.
• Workflow- Backlog >Selected for Development>In Progress>Done
Configure Agile Boards
• Board Settings-Admins only
Dashboard Customization

• Reporting Tool
• Default Dashboard has 4
Gadgets
• Create Dashboard
• You can Edit Layout of
Dashboard(No. of
Columns)
• Add Gadgets
• Pie Chart
• Agile Workboard
Gadget
• Starred Filters
• View as Wall Board
Create Issues
• Fields of create issue
change depending on
Issue Type
• Configure Fields of
Issue
• Search for Issues
• Save Filters
• Access to Filter is
Private
• Subscribe to Filters
Create Epic and Stories
Create Epic and User stories
Assign Stories to Sprint and Start Sprint
Create Sprint
Assign Stories to Sprint and Start Sprint
Create Sprint
Add Subtasks
Other Options
Code

Components

Releases

Workflows
Burndown Charts

You might also like