Process to Change Overview: Level 1

Instructor Guide – Practice Demo

Table of Contents
JIRA Process to Change Overview: Level 1

Examination of the differences between JIRA and ALM

Exploring the differences in ALM and JIRA Requirement Process

Reviewing the differences in the ALM and JIRA Test Management Process

Intro to Xray for Test Management Jira Process

Facilitator Materials Include:
List of Job Aids
List of Rise 360 presentation visual aids
List of Training Aids; FAQ/ Definition of Terms
List of Classroom Resources such as an Agent Desktop Computer/Laptop
List of User Guides

Facilitator Notes
Note: Trainers should become familiar with JIRA and Articulate 360; I.e. Rise 360 and the __________
LMS by practicing use of the system.

Xray Test Management Training Manual Overview

This training review, demonstrates and offers guided practice activities as well as training scenarios
involving web-based training associated with the Xray Test Management Manual:

Key Points for Instruction

All training is virtual instructor led training. (VILT)
All demonstrations must be accompanied by a visual representation of the content. (This may
include live demonstrations, Rise 360 presentations, static images, training aids, and user
guides.).
Students must engage in hands-on activities whenever possible.

Requirements
Basic Agile Skills
Basic JIRA Skills
Training Aids/FAQ/ Definition of terms
Classroom resources, such as an agent desktop/laptop computer.
User guides
Participant guide
Software/Hardware Requirements
Articulate 360/Rise 360
_________LMS
Jira Process to Change Overview: Level 1

Learning Objectives
In this module you will learn the following:

1. Identify key differences between ALM and Jira

2. Explain the functionality of the Xray Test management Tool

This module contains the following lessons:

Lesson One: Introduction to Process Change For ALM to JIRA

60 Minutes
Lesson Topics:
A. Examination of the differences between JIRA and ALM
B. Exploring the differences in ALM and JIRA Requirement Process
C. Reviewing the differences in the ALM and JIRA Test Management Process
D. Intro to Xray for Test Management Jira Process
Lesson One: Introduction to Process to
Change for ALM to JIRA
This lesson reviews the following topics:

A. Examination of the differences between JIRA and ALM

B. Exploring the differences in ALM and JIRA Requirement Process
C. Reviewing the differences in the ALM and JIRA Test Management Process
D. Intro to Xray for Test Management Jira Process

By the end of this lesson, the participant will understand the functionality of the ALM Process to Change
to the JIRA program and explain the difference in ALM agile functions and JIRA processes.

The following objectives correlate directly to the level one evaluation. See Level One Evaluation
Questions/Answers page at the end of this module.

1. Identify key differences between ALM and Jira.

Estimated Duration:
30 Minutes

A. Examination of The Differences Between JIRA And ALM

What is ALM Software?
(See description below)

ALM - Application Life Cycle Management (ALM) is the product lifecycle management or project
management of a computer program.

What is JIRA Software?

(See description below)

by Unknown
JIRA – isJira is an agile project management tool
Author that is developed by the Atlassian company. It was
licensed
originally
under
designed as a bug and issue tracker.

*Bonus Note
The software’s name comes from the Japanese word “Gojira” Atlassian is an Australian company.

Differences in JIRA and ALM

 FEATURES ALM JIRA

Highly Customizable X
Project Roadmap X X
Detailed Reporting X X
Mobile Application X
Requirements Review X X
Add-Ons X X
SaaS Model X
Supports Many Browsers X
Cost Effective X

Every development team is totally different in every organization. Therefore, the ability to
customize your project management tool can be a really useful asset. The capacity to change tools
regardless of company procedure is both a benefit and a strength.
Out of the box functionality that includes road mapping and project planning can easily be
achieved with JIRA. JIRA allows the user to extend most functionalities such as managing requirements
and content through the application of add-ons. On the other hand, the add-on benefits of ALM are
contained within the tool. This means collaboration and documentation could result in higher premiums
due to the need for consultation.
The benefit of collaborating and allowing the user to utilize many browsers and operating
systems can assist teams to reach maximum efficiency for the users. On the contrary ALM is only
supported by one browser, IE (Internet Explorer). We are a global community and IT agile environments
must adopt tools that meet the needs of a multi-platform and multi -operating system. To continue to use
a rigid system such as ALM will require increased personnel for system maintenance and support. Unlike
ALM JIRA functions on a SaaS model.

SaaS Model
(See description below)

SaaS Model – Software as a Service is different than traditional enterprise software because it does not
require a professional to install it on your hardware. Instead, it is easily accessible and available through
the internet. Likewise, users can gain access through a website or a mobile app.
In summary, this ALM to JIRA Process to Change course will help you to make the transition to work
successfully in an agile environment by using JIRA as an issue tracking, and bug tracking project
management tool. JIRA was created and built to compliment the agile work model. It can provide you
with multiple agile reports such as Burndown and Velocity charts. This type of data can ensure that
decisions are data driven and can pinpoint necessary improvements for upcoming sprints.
 Now that you understand the differences between JIRA and
ALM
Let’s take a look at the Requirements Process

B. Exploring the Differences in ALM and JIRA Requirements

Processes

(Figure 1) Cur

rent ALM Use

In ALM a user could have up to 16 steps to complete in order to manage requirements in an ALM
environment. The diagram above shows how some data is internal to ALM and other requirements data
is external to ALM. In ALM data is created and stored in folders which requires a lot of time to create
and manage.

Let’s examine the 16 Steps a user would need to take to upload Requirements in ALM.
 Uploading Requirements in ALM
As illustrated above uploading Requirements in ALM can require a lot of work. The
requirements in ALM will also need the user to assign a Requirement ID number to the
Requirement.
 Now that we have explored “Requirements” in ALM
Let’s take a look at the Differences in the ALM & Jira Test
Management Process i

C. Reviewing the Differences in the ALM and JIRA

Test Management Process

In Jira Xray Test Management all objects are verified at the project level and resolved to assure
that they are actually defects before being linked to a defect at enterprise level. This is a very
efficient way of decreasing enterprise team activity on bugs that are not actually defects.

This process helps to eliminate redundant work.

D. Introduction to Xray for Test Management Jira Process
JIRA XRAY TEST MANAGEMENT

A. Logging into Jira Dashboard

To access the Jira platform you will need to log-in via the following URL


B. Make sure you have the Xray plugin on your dashboard

Step 1: Click on the project tab at the top of your Jira dashboard.
Step 2: Select your project

Select your project and

open it in a new tab

SAMPLE INSTRUCTOR GUIDE