4. -To give the brief Introduction to Jira Features
- To Address on how can we use Jira effectively on
daily basis in accordance with our organizations
current stage
-To get the better Visibility of our dependencies
Purpose Purpose of PPT
5. Jira is a widely-used project management and
issue tracking software developed by Atlassian. It
is designed to help teams of all sizes plan, track,
manage, and release software projects. Originally
developed for software development, Jira has
evolved to become a versatile tool used in various
industries and for different types of projects.
What Is Jira ?
10. Epic : A big user story that needs to be broken down. Epics group together bugs, stories,
and tasks to show the progress of a larger initiative. By default, software projects
Bug : A bug is a problem which impairs or prevents the functions of a product.
Story : A user story is the smallest unit of work that needs to be done.
Task : A task represents work that needs to be done.
Subtask : A subtask is a piece of work that is required to complete a task. Subtasks issues
can be used to break down any of your standard issues in Jira (bugs, stories or tasks).
Issue Types in Jira
21. Some of the Best Practices are :
1. Clear and Descriptive Issue Descriptions : Write clear and descriptive issue descriptions. Include necessary
details, steps to reproduce (for bugs), acceptance criteria (for user stories), and any relevant attachments.
2. Comprehensive Comments : Use comments to provide context, updates, and additional information. Encourage
team members to communicate within Jira to maintain a centralized record of discussions.
3. Proper Issue Linking : Establish meaningful relationships between issues using appropriate linking. This helps
in tracking dependencies, blocking issues, and understanding the relationships between different pieces of work.
4. Effective Use of Labels and Tags: Leverage labels and tags to categorize and filter issues. This aids in
searching for and grouping related tasks across projects.
5. Regular Backlog Grooming : Schedule regular backlog grooming sessions to review and prioritize the backlog.
This ensures that the most important work is ready for the team to pick up during planning sessions.
6. Version and Release Planning : Plan versions and releases in advance, assigning issues to specific versions.
This helps in tracking progress toward release goals and ensures that work aligns with the overall project
timeline.
7. Split Issue : If half work done & half is remained then we can split issue & release it Independently
8. Sprint Burnout : Whenever we add story points in running Sprint , It is best practice to remove other lower
priority story points to maintain the burnout of sprint
22. CREDITS: This presentation template was created by Slidesgo, and includes icons
by Flaticon, and infographics & images by Freepik
Thanks!
Do you have any questions?
