JIRA core

1) Jira Core is a project and task management solution that every business person across an
organization can use to plan, track, and report on work. That means everyone using the
same system.
Jira Core can be used for any business team to manage any type of project
That means is using same framework or same Environment.
2) project types for JIRA are business focused and can be used in many different
departments, including sales, marketing, product development, task management

There are some features of JIRA

3) Business project templates: There are business project templates to manage

simple & complex tasks or workflows. You can customize the templates as your
requirements.
4) Issue details: basically issues is jira is referred as task ,Jira's issues, the details of
every task, plus comments, attachments, and due dates are stored in one place that can
every team member access it
5) Power search: The search tool helps to find specific answers: a due date, the last
update of a task, or tasks still in progress.
6) Reports and Dashboards: You can create reports and dashboards to help you
understand how your team is doing.
7) Managing projects and tasks in project management software starts with a workflow.
Workflows define your process and enable your team to track tasks.
 JIRA Software

1) Jira Software is part of a products that designed to help teams of all types manage work.
Originally, Jira was designed as a bug and issue tracker.
2) Jira Software provides planning and roadmap tools so teams can manage stakeholders,
budgets, and feature requirements from day one.
3) It supports any agile methodology
4) It is important for software building teams to view all the tasks and bugs in the backlog
(A backlog is a build up of work that needs to be completed) so they can prioritize
goals. Jira’s powerful workflow engine ensures that bugs are automatically assigned and
prioritized once they are captured.
5) Jira Software invested in GDPR(General Data Protection Regulation) and Privacy to
ensure all data is handled with care.
6) legal framework that sets guidelines for the collection and processing of personal
information

Agile methodology:

Agile methodology is a type of project management process, mainly used for software
development,
The Agile methodology is a way to manage a project by breaking it up into several
phases. 

It involves constant collaboration with stakeholders and continuous improvement at every

stage. Once the work begins, teams cycle through a process of planning, executing, and
evaluating.

Scrum methodology:

Scrum is a specific Agile methodology that is used to facilitate a project.

The Scrum model suggests that projects progress via a series of sprints. In keeping with
an agile methodology, sprints are timeboxed to no more than a month long, most
commonly two weeks.
timeboxing allocates a fixed time period, called a timebox, within which planned activity
takes place.

sprint in Scrum is a short period of time wherein a development team works to complete

specific tasks,

Kanban methodology:

Kanban is all about visualizing your work, limiting work in progress, and maximizing
efficiency(or flow). 

Kanban teams focus on reducing the time it takes to take a project(or user story) from start
to finish.

They do this by using a kanban board and continuously improving their flow of work.

Kanban is a workflow management method for defining, managing, and improving services
that deliver knowledge work.

It aims to help you visualize your work, maximize efficiency, and improve continuously. 

 Never Pass Defective Products. ...

 Take Only What's Needed. ...
 Produce the Exact Quantity Required. ...
 Level the Production. ...
 Fine-tune the Production or Process Optimization. ...
 Stabilize and Rationalize the Process.

Kanban methodologies are continuous, whereas scrum is based on

short, structured work sprints.”

  Scrum Kanban

Regular fixed length sprints

Cadence Continuous flow
(ie, 2 weeks)

Release At the end of each sprint Continuous delivery

  Scrum Kanban

methodology

Product owner, scrum master,

Roles No required roles
development team

Lead time, cycle

Key metrics Velocity
time, WIP

Change Teams should not make Change can happen

philosophy changes during the sprint. at any time