Building and Supporting Billion Dollar Ships with JIRA - Greg Warner

#atlassian

NOTES:

• Your main title goes in the large blue

font.

• If you have a title that naturally splits

into a subtitle, use the smaller green

font for the subtitle. If not, delete the

subtitle

PHOTO

1. Place your photo at around the

same size as the example photo

2. (Keynote users:) Move your photo

onto the blue shape below Select both

photo and shape and then choose

“Mask with selected shape” from the

menu. Double click the photo to edit

the scale and crop position.

Greg Warner • Team Leader • BAE Systems • @sabre1817

Building and Supporting Billion DollarShips with JIRA

A little about BAE Systems

• BAE Systems is a global defence, aerospace and security company

• 80,000 employees worldwide

• Customers in more than 100 countries

• 2013 sales of £18.2 billion

A little about me

• Team leader responsible for systems and software engineering tools at BAE Systems in Australia.

• 7 years experience with Atlassian software.

• Experience with 100s of hardware and software projects.

• Atlassian software is used across all of our business. (Aerospace, Land & Integrated Systems, Maritime).

Landing Helicopter Dock

• Largest ships ever built for the Australian Navy.

• Helicopters, troops, landing craft, hospital.

• Assembled in Melbourne, Australia.

Big cool statistic

2,569

Add-Ons in Marketplace

How many tasks? 16,100 (Ship 1) 4,900 (Ship 2)

NOTES:

• Adjust numeral size as needed

250 systems

NOTES:


1180 compartments

Big cool statistic

2,569


mysql> select jira_key, -> compartment_desc from compartment -> where compartment_desc like -> 'beer%';

+----------+------------------+ | jira_key | compartment_desc | +----------+------------------+ | LIW-931 | BEER STOREROOM | +----------+------------------+ 1 row in set (0.00 sec)

The Problem

• Tasks and defects initially tracked in a spreadsheet.

• 6400 rows, 78 columns wide.

• Growing at 250 rows per day.

NOTES:


476,000 attributes

Solution Requirements

• Provide a collaborative multi-user system.

•  Import existing data from multiple spreadsheets.

• Automate common appropriate tasks.

• Configure not customize.

• 4 weeks to deliver the solution with 0 import defects.

Why JIRA?

• My team is familiar with JIRA.

• Comfortable that there was an 80% requirement fit.

• Could JIRA perform in this use case?

• Can we deliver in this time frame?

Why JIRA?

• Can we meet the reporting requirements?

•  Is automation possible?

• Can we retrieve data from other enterprise systems?

• What about through life support for each ship?

But a ship isn’t software?

• Apply software development concepts.

•  Identify workflows.

•  Identify key issue fields.

• Build custom reports.

• Extended JIRA using add-ons.

How did you do it? - Workflows

• Have your customers sketch out their day.

• Translate their sketch to a JIRA workflow.

• Collaborate on the workflow.

• Some steps were “excel” steps. Remove them!

Landing Helicopter Dock

Big cool statistic

2,569


Insert workflow screenshot from JIRA

How did you do it? – Custom Fields

•  Identify the fields that matter.

• Don’t blindly import all fields from excel.

• Perform a mass custom field creation using the JIRA Jelly Runner. • 78 fields in less than a minute!

<jira:CreateCustomField fieldType=“select” fieldName=“Ship Location” searcher=“multiselectsearcher” description=“Identify where the fault can be found” fieldScope=“project” projectKey=“LHDIW” customFieldIdVar=“customField”> <jira:AddCustomFieldSelectValue value=“Starboard”> </jira:AddCustomFieldSelectValue> <jira:AddCustomFieldSelectValue value=“Port”> </jira:AddCustomFieldSelectValue> </jira:CreateCustomField> <jira:AddFieldToScreen screen=“LHDIW” fieldId=“${customField.getId()}”/>

How did you do it? – Migration

• Use the built-in CSV importer.

• Trial runs. Many, many trial runs. • Parse the CSV for errors. Fix as many before import.

• Use the REST interface for everything else.


• Use JIRA to deliver a JIRA project.

• Provide training.

• Knowledgebase and Reference guides in Confluence.

• Lookup tables (old vs new JIRA key). Provide a hyperlink to the JIRA issue.

•  Import the reference if possible. Disable the field later.

How did you do it? – Custom reports

•  Identify the mandatory reports.

• Two reports required on Day 1.

• Cheaper and quicker to have an Atlassian services partner build these.

• Delivered to us as a custom JIRA plugin.

How did you do it? – Extend with Add-ons

• Retrieve data for automation from several databases.

• Use Marketplace plugins where possible.

• Custom plugin to retrieve data via JDBC from SQL databases during workflow transitions.

• Retrieve data on issue save actions.

NOTES:


0 Service desk calls

Go-live


• Day 1 was a success.

• 0 defects.

• 0 impact to the trade work force.

NOTES:


10 minutes Before

Issue Creation

After 2 minutes

NOTES:


1 hour Before

Issue Queries

After 5 minutes

Results

• Significant reduction in manual errors.

•  Increased confidence in data integrity.

• Much happier workforce.

Results

I've been able to get home

each day before the sun sets,

that's a massive improvement – Tom, Shipboard Works Control Manger

Results

Whatever you're doing, do more

of that! – Shaun, Manager Capability Development

NOTES:


60,000 man-hours

NOTES:


$5,000,000 Saved

NOTES:


Next step – Through Life Support

• JIRA Service Desk for Warranty Management.

• Re-used much of the automation.

• Linked the JIRA Service Desk to the “as-is” delivery information in JIRA.

• Our Atlassian services partner wrote a custom plugin to identify export controlled issues.

Next step – Through Life Support

• Started with the customer experience expectations.

• Transition was easy because our customers were already familiar with JIRA. • JIRA is now used everywhere!

NOTES:

• If you have short reminders or

highlights that you want people

to tweet, use this.

Key takeaways:

•  JIRA is easy to integrate with enterprise systems. •  Reduce as many fields on import as possible. •  Large imports will take a long time. •  Work with your customers on their workflow. This will make them happy.

#atlassian

Thank you!

Greg Warner • Team Leader • BAE Systems • @sabre1817

Building and Supporting Billion Dollar Ships with JIRA - Greg Warner

Software

Transcript of Building and Supporting Billion Dollar Ships with JIRA - Greg Warner