and the workflow
Emma Rush
Stop Worrying!
2
3
• Overview of the problem project• Pain points• Setting up a workflow
• Approach
• How we used the workflow and JIRA to take the pain away
Agenda
4
• A library of training videos• Hundreds of videos• Focusing on specific tasks• Very short• Several stages in production
5
The Project - Micro Videos
6
Ease the workload
• Labour Intensive• Changes difficult to apply• Lack of clarity
Project Problems
8
• Not working well with high volume• Problems on the horizon• Need a searchable video library
Management Problems
9
10
Process Mayhem
Reporting Problems
11
• No Reporting• Lack of visibility• Canʼt delegate tasks
Productivity Problems
12
• Abundance of Time Suck• Manual Reports• Lots of page editing
13
No Clear Pathway
• Process Clarity• Searchable Library• Management Reporting• Increased Productivity
14
Needs
15
Headache
• Ad-hoc Workflows• Scaffolding• Reporting• Chart Macros• Advanced Search• Some Bespoke Work
16
Use Confluence?
Use the right application for the task. ”“
17
JIRA Panacea
18
19
Where to begin?
20
Learn by sketching
21
http://bit.ly/mGAD78
Configuring Fields and Screens
When learning workflows, hands on,
practical experience is vital”“
22
23
http://bit.ly/aXJuRc
24
Enlightenment
25
The pen is mightier than the mouse.
(in the first instance)“
”
Planning• Important Stages in the Process• Stages and Linked steps• Transitions• Screens and Custom Fields• Roles and Notifications
26
27
28
Collaborate with stakeholders early to get the best
design for your workflow”“
29
Everyone loves a flowchart
30
• Learn JIRA Admin Concepts• Try out example workflows• Make your plans on paper• Convert plans into something you can share• Improve with feedback, iteratively• Build
Planning
31
32
33
Create Script
Video Requested
Get ReviewCreate VideoGet Review
Publish
Create RequirementsGet Review
Video Accepted
• Process can be constantly improved• See problems clearly, early
Kaizen up your process
34
35
Clear Pathway
• One Project for Training videos• One Issue Type
Using JIRA
36
1
37
The Boiler Plate
38
Reporting
• Use statuses for reportingHow many tickets are open
Which status they are in
Where the bottlenecks are
Reporting. The key to getting a project on track”“
39
Reporting
40
project = TRAINVIDS AND issuetype=”Training Video” AND status = Open
41
Dashboards
42
43
44
45
Dashboards put information that your team needs
at their fingertips”“
46
47Ticket Wrangling
48
How to keep on top of your tickets
• What information will you need to find quickly?• Make custom fields to suit
keeping content fresh
find tickets for specific software version
49
50
51
52
53
54
Issue Management
• Pimping out the workflow with Conditions• Custom Fields Vs Components and Versions• Additional options in the workflow
Reflections
55
I the workflow
56
Get your project on track. Put it in a JIRA
workflow ”“
57
• Reporting• Visibility• Added Review and Testing into the Process
Manage Process
58
I the workflow
59
60
Attributionhttp://www.flickr.com/photos/bispham2/3997915098/• Process Mayhem
• Unclear Pathhttp://www.flickr.com/photos/osucommons/3230009752/
http://www.flickr.com/photos/40230585@N08/3695173456/
• Enlightenment
Attribution
61
http://www.flickr.com/photos/nationallibrarynz_commons/4535966085/sizes/o/in/photostream/
• Wrangling
• Boiler Platehttp://www.flickr.com/photos/mk94577/4081258769/
62
!"#$%&'&(
!"#$%&"'(")*
63
!"#$%&'&(
!"#$%&"'(")*
A Brief History...
64
JIRA Text-Based Editor
65
• Better than XML• Part of Core JIRA
• No Visual Representation• Requires Lots of Planning• Not Very Intuitive• Frustrating
JIRA Text-Based Editor
66
GOOD BAD
JIRA Text-Based Editor
67
NOT GROOVY
SysBliss Workflow Designer
68
• Prettier than text• Visualizes Workflows
• Looks Different than JIRA
• Takes Over Entire Interface• Lots of Right-Clicking• Does Basically what JIRA Does
SysBliss Workflow Designer
69
GOOD BAD
SysBliss Workflow Designer
70
Groovy, but
NO LOVE
JIRA 4.4 Workflow Designer
71
• Built Into JIRA• Clean UI matches JIRA• No Right-Clicks• Functions Not Possible in Core Editor• UX Enhancements = SPEED• View Workflow From Any Issue• 120+ Issues/Features Resolved
JIRA 4.4 Workflow Designer
72
73
!"#$%&'&%!!"#$%&"'()"*+
• Workflow Creator is not the Consumer• Back and Forth - “Can you see it now?”
• Paper / White Boarding
• Gliffy *nod*
• Never catch everything
• Consumers Have No View into Problem Areas• Difficult to Revise Once Implemented
Up-Front Workflow Design
74
• Easy Creation: The Diagram IS the Workflow• Consumer View Enables Collaboration• Easy Revision: The Diagram IS the Workflow• PNG Export Enables Workflow Diffs• Donʼt Feel Like You Have To “Get It Right”• Ongoing Collaboration = More Beer!
Iterative Workflow Design
75
Initial Collaborative Design
76
• Controlled by JIRA Permissions• Link on View Issue Screen• Highlights the Current State
Workflow Test Run(read-only workflow views)
77
Update and Publish
78
79
A Workflow For Making Workflows
An Educational Video
80
• Collaborate on Initial Design in Workflow Designer• Super Fast Edits
• Immediate Feedback
• Test Workflow in JIRA
• Donʼt Worry About Breaking Stuff
• Easy to Change
• Freedom to Grow Workflow Over Time•
Summary
81
Try It Now!
82
http://atlss.in/jiraeap