QUALITY. PRODUCTIVITY. INNOVATION.

TEAM and JIRA

Using JIRA as an ALM
June 2014

Edited by Jira Champions:

- Bogdan Giurgiu
- George Anghelache
- Levente Veres
- Sebastian Denes

endava.com
 TEAM Agile Delivery Phases and
JIRA
Planning
Agenda
Envisioning
Concurrent Engineering
Closure
Tools and Techniques

2 2
 TEAM Agile
Sprint planning
User stories walkthrough
Task breakdown
(Optional) Time estimate
Set up JIRA project Set up sprint duration
Set up team in JIRA Development and testing
Set up project roles Transitioning stories / tasks through the workflow
(Optional) Define: Record time
Custom issue types End of Sprint
Split /3move user stories
Custom fields Close sprint
Custom workflows Reporting
Boards Standard reports
Dashboards

Planning Envisioning Concurrent Engineering Closure

Create prioritised product backlog

Final packaging (prepare

Epics release reports, archive

Define Versions project)

(Optional) Set up dashboards

3 3
Quick reference documentations
Topics for Scrum teams:
Creating a Board
Planning Configuring Estimation and Tracking
Configuring Swimlanes
Public Sites Configuring Working Days
Configuring Columns
Documentation Working with Epics
Atlassian Documentation (all products) Creating an Epic
Creating an Issue (Story)
JIRA Documentation Jira documentations
Envisioning Working with Sprints
GreenHopper Documentation Creating a Sprint
Quick guide Creating a Version
Creating a Dashboard
JIRA 101 Starting a Sprint
GreenHopper 101 Adding an Issue to a Sprint
Adding an Issue to a Version
Video Tutorials Adding an Issue to an Epic
Jira Tutorials Channel at YouTube Enabling Ranking
Estimating an Issue
GreenHopper 6 - Welcome to GreenHopper
Planning a Version
JIRA in a Nutshell demo video Ranking an Issue
Transitioning an Issue
Construction
Using Plan Mode
Private (Endava sites) Using Work Mode
Viewing the Burndown Chart
http://intranet/sites/jira - Jira Champions official Viewing the Control Chart
sites Viewing the Cumulative Flow Chart
Viewing the Epic Report
Viewing the Sprint Report
Viewing the Velocity Chart
Viewing the Version Report
Closure Deleting a Sprint

4 4
 JIRA Lifecycle in Endava

Users

Request

If Out of scope
JIRA
CHAMPIONS 5 ITS
Customization, Tailoring, Project, User, Roles
Plugins, Training Management

Shadows/Test the new implementations

Tests In Scope Requests

Imports the Production Environment any time

new implementations are to be made
Promotes
Replicates the Preproduction on Production

TEST STAGING PRODUCTION

5
 JIRA Lifecycle in Endava

Users

Request

our Endava colleagues and

If Out of scope
JIRA client stakeholders
People that are using JIRA, have
CHAMPIONS 6
projects in JIRA and access it in all ITS
Customization, Tailoring, roles (SM, DEV, TST, PO) Project, User, Roles
Plugins, Training Management

Shadows/Test the new implementations

Tests In Scope Requests

Imports the Production Environment any time

new implementations are to be made
Promotes
Replicates the Preproduction on Production

TEST STAGING PRODUCTION

6
 JIRA Lifecycle in Endava
First point of contact for JIRA related activities
System Health
JIRA System Availability Users
Ensure Systems are running at the required performance
Perform regular backups
Keep the systems under maintenance and perform regular
updates Request

Smoke testing on Production Environment after system

modifications(updates, restores, new plugins ) If Out of scope
JIRA
Security ownership on JIRA Servers
Ensure that the servers have valid licenses
CHAMPIONS 7 ITS
Customization, Tailoring, Project, User, Roles
Plugins,Staging
Trainingenvironment Management
Smoke testing on Production and Staging server for JIRA system
health and key scenarios. Shadows/Test the new implementations
Replicates Prod Environment to Staging.
Tests In Scope Requests
Replicates the agreed changes from Staging to Prod
Environment
Imports the Production Environment any time
new implementations are to be made
Manages Promotes
Projects, Users, Roles, Notifications Replicates the Preproduction on Production
Administrative Panel
TEST STAGING
JIRA tailoring (templates, workflows, custom fields, plugins PRODUCTION
a.s.o.)

7
 JIRA Lifecycle in Endava

JIRAUsers
evolution and best practices
champions
Analyse client or teams requests
Requestand propose solutions
Fit-Gap analysis for JIRA tailoring to specific project and
client contexts If Out of scope
JIRA Consulting ITS for JIRA tailoring (templates, workflows,
custom fields, plugins a.s.o.)
CHAMPIONS 8 ITS
Customization, Tailoring, Hold presentations/trainings about JIRA usage Project, User, Roles
Plugins, Training Champion JIRA best practices and usage in their DU Management

Shadows/Test the new implementations

Smoke testing on Staging for JIRA functionalities and
Tests features. In Scope Requests

Imports the Production Environment any time

new implementations are to be made
Promotes
Replicates the Preproduction on Production

TEST STAGING PRODUCTION

Contact: jira_champions@endava.com
8
JIRA Support Workflow
Jira Request Process model: Levente Veres

Request
Request New feature
implemented Reject
Users

Start process

Resolved
Service Desk (Level 1)

Route the
Request Out of Scope (ex:
INCIDENT CHANGE
new plugins)

9 DONE

Common
Incident/
Change
Resolved Its System No
by Service Desk Incident
Level 2

Implements
Resolved
System Incident the Proposal
by Level2

Yes
JIRA Champ.

Analyze by Jira Champions. Implementation

for future possible Approved by Product Imple-
implementation Owner ment

9 9
 JIRA Support Workflow
Change
Jira Request Process Its a CRUD (Create, Update, Delete) model: Levente Veres

Request
Request
modification to the system performed
New feature
by Service Desk. implemented Reject
Users

Start process
Example: new project request, user
add/remove, schema attaches to
project, roles modification
Resolved
Service Desk (Level 1)

Route the
Request Out of Scope (ex:
INCIDENT CHANGE
new plugins)
10 DONE

Common
Incident/
Change
Its System
Incident
Resolved
by Service Desk Incident Out of Scope No

Its a system malfunction that can be Any request that has impact on the
resolved by IT (Level2). regular functions of JIRA Environment
Example: license expiration, system will go to JIRA Champions
Level 2

down, JIRA Application Server down.

Resolved
Example: new plugin, UI modification,
Implements
System Incident the Proposal
by Level2
field values modification, major updates.
Yes
JIRA Champ.

Analyze by Jira Champions. Implementation

for future possible Approved by Product Imple-
implementation Owner ment

10 10