Scribd
Upload
164 views18 pages

JIRA Notes

Jira is a software project management tool that allows teams to plan, track, and manage their work. It offers products for software development, IT, and other teams. In Jira, individual tasks are called "issues" which are organized into projects. It provides features like agile boards, roadmaps, and reporting to help teams plan work, track progress, and improve processes through iterations and retrospectives.

Uploaded by

suyog sarnaik
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
164 views18 pages

JIRA Notes

Jira is a software project management tool that allows teams to plan, track, and manage their work. It offers products for software development, IT, and other teams. In Jira, individual tasks are called "issues" which are organized into projects. It provides features like agile boards, roadmaps, and reporting to help teams plan work, track progress, and improve processes through iterations and retrospectives.

Uploaded by

suyog sarnaik
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 18

**********************JIRA********************

A brief overview of Jira :


 Jira is a family of products built to help all types of teams manage their
work.

 Jira offers several products and deployment options that are purpose-built
for Software, IT, Business, Ops teams, and more. Read on to see which is
right for you.

 Products and apps built on top of the Jira platform help teams plan, assign,
track, report and manage work.

 The Jira platform brings teams together for everything from agile software
development and customer support to managing shopping lists and family
chores.

Key terms to know :


 Issues :
 A Jira 'issue' refers to a single work item of any type or size that is tracked
from creation to completion.

 For example, an issue could be a feature being developed by a software


team, a to-do item for a marketing team, or a contract that needs to be
written by a legal team.
 Projects :
 A project is, quite simply, a collection of issues that are held in common by
purpose or context.

 Issues grouped into projects can be configured in a variety of ways, ranging


from visibility restrictions to available workflows.
 Jira for bug tracking :
 Bugs are just a name for to-do's stemming from problems within the
software a team is building.

 It is important for teams to view all the tasks and bugs in the backlog so
they can prioritize big picture goals.

 Jira’s powerful workflow engine ensures that bugs are automatically


assigned and prioritized once they are captured. Teams can then track a
bug through to completion.

 Features for software development :


 Scrum boards :
If Scrum is the framework that guides teams and their roles, events, artifacts, and
rules, then the Jira Scrum Board is the visual display of its progress during the
development cycle.

 Plan - Create user stories and issues, plan sprints, and distribute tasks
across your software team.

 Track - Prioritize and discuss your team’s work in full context with
complete visibility.
 Functions :
 Increase communication and transparency –

 The Jira Scrum Board is the single source of truth for the all the work
a team needs to complete.

 Since it can be accessed by any team member at any time, everyone


clearly understands what's on his or her plate, and can quickly
identify any blockers.

 Promote sprint planning and iterative development –

 At the heart of the Scrum framework is the Sprint, a designated


amount of time (typically two weeks) for teams to build a potentially
releasable product increment.

 The Jira Scrum board is designed so teams can organize their work
around the Sprint timeframe.

 Improve team focus and organization –


 Teams miss project deadlines when they're over-committed on their
workload or lose track of key milestones.

 Jira Scrum Boards provide transparency into the team's work by


slicing work into stages and utilizing burndown and velocity reports.
 Roadmaps :
Sketch out the big picture, communicate plans with stakeholders, and
ensure your roadmap connects to your team's work - all in a few clicks in
Jira Software Cloud.
 Agile reporting :
Teams have access to more than a dozen out-of-the-box reports with
real-time, actionable insights into how their team is performing sprint over
sprint.

Ex. Burnup Chart , Burn Down Chart , Sprint Report


 Connect issues to User Stories :
Bring information from your favorite version control, build, deployment or
feature flagging tool into Jira Software and get instant visibility into your
development pipeline.

 How To Log Defect :


o Click on create button
o You will able to see following window and select appropriate project
from project dropdown.

o Select issue type as Bug.


o Then enter the bug summary details in Summary tab.

o Enter the description of defect.


o Then , select appropriate Priority of defect.

o After that upload the test evidences in attachment section and from
assignee dropdown select the developers name.
o Then , Select sprint and click on create button.
 Agile Meetings/Ceremonies :
Sprint planning :

 Attendees: development team, scrum master, product owner and


testing team.

 When: At the beginning of a sprint.


 Duration: Usually an hour per week of iteration.

 Purpose:
o Sprint planning sets up the entire team for success throughout the
sprint.

o Coming into the meeting, the product owner will have a prioritized
product backlog.

o They discuss each item with the development team, and the group
collectively estimates the effort involved.

Daily Stand-up :

 Attendees: development team, scrum master, product owner and


testing team.

 When: Once per day, typically in the morning.

 Purpose:
o Stand-up is designed to quickly inform everyone of what's going on
across the team.

o It's not a detailed status meeting. The tone should be light and fun, but
informative.
o Have each team member answer the following questions:

o What did I complete yesterday?


o What will I work on today?
o Am I blocked by anything?

Sprint (Iteration) review :

 Attendees: development team, scrum master, product owner ,


testing team and stakeholder (optional)

 When: At the end of a sprint or milestone.

 Purpose:

- Iteration review is a time to showcase the work of the team.

- They can be in a casual format like "demo Fridays", or in a more


formal meeting structure.

- This is the time for the team to celebrate their accomplishments,


demonstrate work finished within the iteration, and get
immediate feedback from project stakeholders.

Sprint Retrospective :

 Attendees: development team, scrum master, product owner ,


testing team and stakeholder (optional)

 When: At the end of an iteration.

 Duration: 60 minutes.
 Purpose:
- Agile is about getting rapid feedback to make the product and
development culture better.
- Retrospectives help the team understand what worked well–and
what didn't.
- Retrospectives aren't just a time for complaints without action. Use
retrospectives to find out what's working so the team can continue
to focus on those areas.

- Also, find out what's not working and use the time to find creative
solutions and develop an action plan.

-Continuous improvement is what sustains and drives development


within an agile team, and retrospectives are a key part of that.

 User Stories Format :


 Scenarios on above user story :

 Test cases :

You might also like