+ All Categories
Home > Documents > Improved JIRA Process

Improved JIRA Process

Date post: 09-Jan-2016
Category:
Upload: jaguar
View: 63 times
Download: 3 times
Share this document with a friend
Description:
Improved JIRA Process. Unscheduled Backlog. Connect Team. Outside Contrib. Bugs Feature Requests. Requirement Docs. BA Review. Large Tasks or Features Measured in T-Shirt Sizes. Epic. Epic. User Story. User Story. Collection of common tasks sharing a theme - PowerPoint PPT Presentation
Popular Tags:
11
Improved JIRA Process
Transcript
Page 1: Improved JIRA Process

Improved JIRA Process

Page 2: Improved JIRA Process

ConnectTeam

OutsideContrib

Unscheduled Backlog

BugsFeature Requests

BA Review

RequirementDocs

Epic EpicLarge Tasks or FeaturesMeasured in T-Shirt Sizes

UserStory

UserStory

Task Task

DevTask

DevTask

QATask

DocTask

Subtasks

Collection of common tasks sharing a themeblocked to fit into a sprint

Page 3: Improved JIRA Process

Change in Process

Before Now

Task

SubTask

SubTask

SubTask

Task

All mine

SubTask

SubTask

SubTask

Page 4: Improved JIRA Process

Work Types

Development Task

QA Task

Document Task

Infrastructure Task

Research Task

Page 5: Improved JIRA Process

Issue Creation Checklist for Tasks/Bugs1. Give it a brief / descriptive summary2. Assign it a work type, priority, .3. Give it a fixed and affects version.4. Fill out the description with the template considering all work and completion criteria.

EXAMPLE:

Gateway 1001

Summary: Update JIRA to include work types

Description:Development: Add JIRA work type pull down to create tickets and make it

a mandatory option. Include the following work types …QA: Create sample ticket with work type.Infrastructure: Allow assignee access to JIRA admin.Documentation: Update wiki for JIRA process.Research: n/a

CC: Mandatory work type option added to JIRA task/subtask issues, can createand alter this value on tickets.

Page 6: Improved JIRA Process

Issue Creation Checklist for Tasks/Bugs

5. Assign the ticket a point value.

Process for pointing tickets mid sprint:

5?3

5

Skype, Phone,Face to face

5 points

Account forOur Work!

Page 7: Improved JIRA Process

Issue Development Checklist for Tasks/Bugs

1. Assign ticket to yourself.2. Review the description creating subtasks and linked tasks where needed.

If separate work type tickets are created, ensure that they are appropriatelyassigned.

3. Estimate and enter work log (keep in mind all subtasks will log work to the main task).

Page 8: Improved JIRA Process

Task

Small Task: Run CI Confirm Results Run Existing Test

Add CommentTo Task

Large Task: New Test Suite Alteration of CI

New QATask

Link

Medium Task: Alter Existing Tests Deep Dive into Logs Multi-step Verification

QASubTask

QA

Page 9: Improved JIRA Process

Task

Small Task: Wiki Edit Small Installation change

Add CommentTo Task

Large Task: New Multi-page Doc Requires extensive edit

New DocTask

Link

Medium Task: Addition to Doc Requires brief edit Create new wiki

DocSubTask

Doc

Page 10: Improved JIRA Process

Issue Closing Checklist for Tasks/Bugs

1. Ensure that all created subtasks have been closed including QA and any other outside work types.

2. Check that the CC and all work has been completed from the description.3. Make sure all work has been logged on the main task.4. Zero out the time remaining log.5. Double check that the task was pointed.6. If there is an affected version that did not get worked on as a part of this

task, make sure that a ticket is created to encompass this work and link it to the task.

7. Resolve and close the issue.

Page 11: Improved JIRA Process

Suggested JIRA plugin

Create and Link

https://studio.plugins.atlassian.com/wiki/display/JCLP/JIRA+Create+and+Link+Plugin


Recommended