Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

JIRA & Agile Project Management: A Comprehensive Guide, Exams of Advanced Education

A comprehensive overview of jira, a popular project management tool, and its integration with agile methodologies like scrum and kanban. It explains the key features of jira, its use in issue tracking, bug management, and project management, and highlights the benefits of using jira for various tasks. The document also delves into the principles of scrum and kanban, explaining their respective strengths and how they can be effectively implemented within a jira environment.

Typology: Exams

2024/2025

Available from 12/26/2024

alex-david-34
alex-david-34 🇿🇦

5

(1)

3.7K documents

Partial preview of the text

Download JIRA & Agile Project Management: A Comprehensive Guide and more Exams Advanced Education in PDF only on Docsity!

JIRA & AGILE PROJECT MANAGEMENT

  • JIRA is a project management tool used for issues and bugs tracking system.
    • JIRA is widely used as an issue-tracking tool for all types of testing.
    • JIRA is an incident management tool.
    • JIRA is developed by Atlassian Inc., an Australian Company.
    • JIRA is a platform independent tool; it can be used with any OS.
    • JIRA supports MySQL, Oracle, PostgreSQL and SQL server in the backend.
    • JIRA can be integrated with many other tools - Subversion, GIT, Clearcase, Team Foundation Software, Mercury, Concurrent Version System and many more.
    • JIRA is used in Bugs, Issues and Change Request Tracking.
    • JIRA can be used in Helpdesk, Support and Customer Services to create tickets and track the resolution and status of the created tickets
    • JIRA is useful in Project Management, Task Tracking and Requirement Management.
    • JIRA is very useful in Workflow and Process management.
    • JIRA supports Scrum and Kanban boards.
    • Scrum and Kanban boards provide an immediate snapshot of the project to the team.
    • Boards help to quickly review the progress of the project and see the status of the individual tasks.
    • Board workflow can be customized to fulfill the way a team wants to proceed.
    • The name "JIRA" is actually inherited from the Japanese word "Gojira" which means "Godzilla
    • JIRA issue would track bug or issue that underlies the project. Once you have imported project then you can create issues.
    • Different organizations use Jira to track different kinds of issues, which can represent anything from a software bug, to a project task, or a leave request form.
    • Issues are the building blocks of any Jira project.
  • A "project" is JIRAs highest level container.
  • One single issue can only be in one JIRA project at a time.
  • Kanban Agile is best for teams that are working on bugs or issues where most have an ASAP delivery schedule
  • In Kanban, there is a focus on rapid assignment and working in the right order not as much on estimating projected completion dates for every piece of work.
  • With Kanban, teams collect all the work that needs to be done, put the work in the right order and assign and complete the work as fast as they can.
  • SCRUM Agile is best for teams that are working on new features with a tight schedule for finishing their work as they try to align with the projected launch target or the coordination of delivery from other teams.
  • SCRUM teams manage their way toward this target by breaking their work up into iterative batches called sprints.
  • Most high performing teams agree that two weeks is a good length of time for sprints
  • With SCRUM, when new work is discovered, the existing in-progress work is left as it is and new work is added to the next sprint.
  • With SCRUM, teams collect all the work that needs to be done, they put the work in the right order, they define checkpoints for completion of batches of work and they reprioritize at each checkpoint.
  • In all kinds of agile, teams break up their "to-do's" in small manageable snippets.
  • Breaking work into fragments helps to ensure that ownership of every task is clear and that teams can reprioritize often
  • A JIRA epic is the same thing as a JIRA Align feature.