The document outlines a guest lecture given by Abhishek Prasoon on introducing Jira project management software. It provides an overview of Prasoon's background and credentials, as well as an agenda for the lecture that includes explaining the need for project management software, key aspects of Jira like epics, user stories, and scrum rituals, and how to perform tasks in Jira like creating projects, tracking issues, and running sprints. The document aims to educate attendees on using Jira for agile software development and project management.

1. Apeejay School of Management, Dwarka, New Delhi
Introduction to Jira
Guest Lecture by Abhishek Prasoon
Chief Scrum Master, Coforge
19th September 2023
1

2. About Me
• 18 years of experience in IT industry. Have been working
with companies like NIIT, HCL, Mastek and Coforge
• 25+ IT Industry Certifications and Winner NEXT 100 and
Innovative CIO Award
• Author: The Forefront Manager and The Infallible
Weapons
• Published 120+ articles on Technology and Management
• Orator on various platforms, avid traveler and Yoga
enthusiast
LinkedIn - https://www.linkedin.com/in/abhishekprasoon/
Contact Me – aprasoonin@yahoo.com
Mobile - 9891819681
2

3. Disclaimer
Any views or opinions represented in the lecture are my own and do not represent those of the
people, institutions, or organizations that I may or may not be associated with in professional or
personal capacity, including past, current, and future employers unless explicitly stated.
Image Credit
Google Image Search Results
3

4. Workshop Agenda
4
Duration – 60 min.
Sr No. Topics Timeboxing
1 Introduction to Jira 05 Minutes
2 Navigating the Jira Interface 10 Minutes
3 Creating and Managing Issues 10 Minutes
4 Searching and Filtering Issues 10 Minutes
5 Managing work in an agile context 10 Minutes
6 Class Assignment 10 Minutes
7 Q&A Session 05 Minutes

5. Why we required Project
Management Software ?
5

6. 6

7. 7

8. Why Jira?
8

9. Unit of work in Agile
9

10. Epic (Example - www.amazon.in)
10
 Product Search
 Product Listing
 Product Details
 Shopping Cart
 Place Order
 Online Payment
 User Details
 Order History
 Return Request
 Feedback
 Suggestion Engine
 Create a Wishlist
 Your Accounts
 Your Orders
 Recommendations
 Prime Membership
 Language.
 Sell on Amazon
 Amazon Business
 Social Connect
 Digital Content
 Sign In
 Careers
 Help and Settings

11. User Story
11
Title: Product Search Enhancement
Story: As an online shopper, I want the product search functionality to provide real-time suggestions as I type in
the search bar. This will help me find products more quickly and accurately, improving my overall shopping
experience.
Acceptance Criteria:
1. When I start typing in the search bar, a dropdown list of relevant product suggestions should appear.
2. The suggestions should update dynamically as I continue typing or editing my search query.
3. Clicking on a suggestion should take me directly to the corresponding product page.
4. The search suggestions should be based on product names, descriptions, and categories.
5. The feature should be responsive and work smoothly on both desktop and mobile devices.
Definition of Done (DoD):
• Real-time search suggestions are implemented and tested.
• User interface updates are integrated.
• Suggestions are based on relevant product data.
• Cross-device compatibility and performance are validated.

12. Scrum Rituals
12

13. Scrum Artifacts
13

14. 14

15. 15
While conducting Sprint Planning Meeting
 Add more details with attachments.
 Add DoS and DoD
 Add Acceptance Criteria
 Add Estimated Story Point
 Add task and sub task and link it with the
Story.
 Assign a task to Users.
 Start the Sprint
While Conducting Daily Standup Meeting
 Login as a separate user to view assigned
items.
 Update work status
 Add comments (if required)
Conduct Demo
 Use Acceptance Criteria for reference.
 Update Product Backlog
Close the Sprint
Corelate with Scrum

16. 16
Some common built-in fields in Jira
1. Summary: A brief description of the issue.
2. Description: A more detailed explanation of the issue.
3. Reporter: The user who reported the issue.
4. Assignee: The user or team member responsible for working on the issue.
5. Priority: Indicates the importance or urgency of the issue (e.g., High, Medium, Low).
6. Status: Represents the current state of the issue (e.g., Open, In Progress, Resolved).
7. Resolution: Indicates the outcome of the issue (e.g., Fixed, Won't Fix, Duplicate).
8. Issue Type: Categorizes the issue (e.g., Bug, Task, Story).
9. Due Date: The date by which the issue should be resolved or completed.
10.Labels: Keywords or tags that can help categorize and search for issues.
11.Components: The part or module of the project to which the issue belongs.
12.Affects Version: The version of the software where the issue was first detected.
13.Fix Version: The version of the software in which the issue is resolved or will be resolved.
14.Original Estimate: The initial time estimate for completing the issue.
15.Time Tracking: Fields for tracking time spent, remaining time, and time logged.
16.Sprint: The sprint or iteration to which the issue belongs (for Agile projects).
17.Epic Link: Links an issue to an epic (for Agile projects).

17. 17
Some common built-in fields in Jira
18. Environment: Information about the environment in which the issue occurs.
19.Attachment: Allows users to attach files and documents to issues.
20.Watchers: Users who are monitoring or "watching" the issue for updates.
21.Comments: Allows users to add comments and discussions related to the issue.
22.Sub-tasks: Allows the issue to be broken down into smaller, manageable tasks (typically used for tasks
within a larger issue).
23.Linked Issues: Shows relationships between issues, such as "blocks," "is blocked by," "relates to," etc.
24.Story Points: Used in Agile projects to estimate the relative effort or size of a user story.
25.Sprint Custom Fields: Fields specific to Agile sprints, like "Sprint Start Date" and "Sprint End Date."
26.Worklog: Tracks time spent on an issue, including the work description and author.
27.Issue Security Level: Specifies who can view and edit the issue based on security levels set in Jira's security
schemes.
28.Custom Fields: Custom fields can be defined by administrators to capture project-specific data. The types of
custom fields can include text fields, dropdown lists, checkboxes, date pickers, etc.

18. 18

19. 19

20. 20

21. 21

22. 22
Assignment
• Create a New Project
• Create users with different roles (add your classmates).
• Add user to the Project.
• Create an Epics List
• Create a Product Backlog by adding Stories and Tasks
• Create a Custom Field
• Link Stories with Epics
• Prioritize Product Backlog
• Run complete cycle of Sprint including Sprint Planning Meeting, Daily Standup Meeting using Jira
• Write a JQL query to filter all the incomplete task of current Sprint
• Generate a Burndown Chart
• Create a Dashboard

23. 23
What Next?
https://university.atlassian.com/student/catalog

24. 24
LinkedIn - https://www.linkedin.com/in/abhishekprasoon/
Contact Me – aprasoonin@yahoo.com
9891819681