Using JIRA in the Enterprise

Cleas-Göran Carlander | Scania

n2

Jira @  ScaniaClaes-­Göran  Carlander

Senior  Engineer,  C3Process  Support

SCM  and  Build  Management  for  Powertrain  Control

Agenda

n Scania  general  presentation

n Why Jira  

n Jira  @  Scania

n Maintenance

n Project  in  Jira

n Security

n Scrum /  Kanban /  Agile  /  Extreme  /  VP  /  DP

n Headaches

n Summary

3

4

124  years  of  industrial  history

1891 Company  founded1897 First  car1900 Scania  was  established  in  Malmö1902 First  truck1905 First  industrial  engine1911 Scania  and  Vabis  merge,  first  bus1921 Bankruptcy1930s Buses  main  product1934 Last  red figures1940s New  strategy1948 General  agent  for  Volkswagen1950s Exports  started1957 Factory  in  Brazil1964 Factory  in  Netherlands1969 Saab  and  Scania-­Vabis  merge

1976 Factory  in  Argentina1992 Factory  in  France1993 Factory  in  Poland1995 Factory  in  Mexico1995 Independent  company1996 Scania  a  public  company2000 Factory  in  St  Petersburg,  Russia2008 Subsidiary  of  Volkswagen2010   New  R-­series  is  “Truck  of  the  year”2011      100  years  since  the  first  bus  delivery2013   Launch  of  Scania  Streamline  and  

complete  range  of  Euro  6  engines2014 Scania  became  a  wholly  owned  

subsidiary  of  the  Volkswagen  Group

Connected  Services

5

Why  JiraScania  started  using  Jira  at  ~2010.

– Main  purpose  was  to  use  ONE  system  for  software  bug  tracking  and  software  change  requests  for  all  Software  development  on  R&D.  Pre  Jira  we  used  at  least  five  different  systems  to  document  an  track  issues,  one  of  the  most  popular  was  Excel.

– Some  of  our  Requirements  at  that  time– Easy  to  use– Easy  to  maintain  and  configure– Traceability  between  issues  and  related  code  (perforce  repository)

– Structure  and  Links

– Is  Jira  the  right  tool  for  everything  we  use  it  for?  While  thinking  of  this  our  Jira  site  grows  and  we  become  more  and  more  dependent  on  it.  We  invest  a  lot  of  time  to  improve  our  Jira.

6

MaintenanceJira  is  an  important  tool  for  Scania  that  holds  a  lot  of  business  critical  information  so  it  must  be  easy  to  maintain  and  have  24/7  uptime.  

n First  line  support  thru  Scania’s  helpdesk– Handles  all  kind  of  questions  regarding  computers,  access  control,  network,  phones,  etc.

n Jira  specialists  available  on  regular  office  hours  (8  am  – 5  pm)  – Currently  a  team  of  ~8  persons  handling  Jira  and  Perforce  (Source  code  repository)

7

Jira  @  Scania

We  have  three  production  Jira  sites  used  for  different  purposes  and  6  sites  for  test  and  development

– R&D  and  a  lot  of  other  stuff.– Jira  2  (some  obscure  projects).  – DMZ  Jira.

– Used  for  partners,  issues  in  this  sites  can  be  linked  to  issues  in  our  internal  site.  

– PreProd  Internal  /  PreProd  DMZ– Test  &  Development  (3  sites)  /  DMZ  Test  &  Development  (1  site)

8

Jira  @  Scania

9

Projects  in  JiraR&D  project  is  rarely  a  development  project  managed  by  a  small  team.  In  most  cases  a  Jira  project  is  equal  to  a  System  or  part  of  a  system.  

– Engine  Management  System– 5  generation  of  systems,  3  in  production.– >  20  variants,   thousands  of    parameter  settings.– 4  maintained  Jira  projects.

– Suspension  Management  System– Infotainment

A  typical  project/system  lifecycle  for  us  is  10  to  20  years,  during  this  period  the  we  will  have  function  development  and  bug  fixing  and  of  course  we  need  to  track  changes  all  the  time.

10

11

SOP  IssueFunction A

Analys

ImplImpl

Analys

Test/Impl

Impl

Analys

Impl 1

Analys

Impl 2

Team  1

Team  2

Team  3

Project  ASOP  1512

Impl

Impl

Group  X Sprint  v4 Sprint  v12 Sprint  v16 Sprint  v20 Sprint  v24 Sprint  v35 Sprint  v39 Sprint  v43Sprint  v28Sprint  v8

Prj ADL3

Prj ADL2

Prj ADL1

Impl 1

Analys

Impl 2

Impl

Analys

Test/Impl

Impl Impl

Impl

Impl

Impl

D1 D1 D2

Project  CSOP  1512

Prj CDL1

PrjCDL2

SOP  IssueFunction C

SOP  IssueFunction B

D2 D3D1

Project  dependencies

Workflows

Keep  it  simple

Basic  workflow  introduced  2014.

12

Scrum  /  Kanban  /  Agile  /  WP  /  DPSo  many  names  and  methods,  and  we  use  them  all,  in  our  own  Scania  way.

800  SW-­developers,  and  that´s  on  R&D  only,  I  have  no  figures  on  the  number  of  developers  in  our  IT-­area,  can’t  be  convinced  to  use  the  same  methodology,  we  must  accept  differences  in  the  way  teams  work.

Tools  must  be  easy  configurable  to  support  the  way  we  work.  

The  tool  should  support  the  process  not  dictate  it.

13

Security  issues  in  a  large  organisation

n Links  to  documents– Avoid  attachments,  it  may  brake  access  rules  for  the  attached  document.  

n Getting  data  from  other  systems– Is  it  ok  to  list  data  retrieved  form  another  system  in  a  Jira  dropdown  box?

14

Headaches

n Scripting.– Any  system  developer  can  write  a  Perl,  Python  or  Ruby  script  or  use  other  tools  that  can  access  data  in  Jira  over  REST.

n Gadgets.– Gadgets  is  wonderful  and  dangerous,  it  is  easy  to  block  Jira  with  for  example  ’Google  calender’.  

n Using  Script’s  and  Gadgets  can  block  a  version  upgrade  of  Jira  due  to  compatibility  issues

15

Next  step

n Solving  Performance  issues.– Ongoing  work  to  identify  and  resolve  problems.

n Resource  planning  and  estimations.– Find  a  tool  that  can  visualize  our  planned  work.

n Data  retrieval  from  other  internal  Scania  systems.

n Define  a  kind  of  hierarchy  between  projects– This  is  process  oriented  not  really  a  tool  question  but  we  need  to  understand  how  our  issues  shall  be  linked  together  by  Parent/Child  links  and  other  link  types

16

Some Jira  wishesn Weeks  don’t  start  on  Sundays,  there  is  a  world  outside  US.

n Sorting  on  Version  is  impossible  to  describe  for  humans.  Alphabetically  or  numeric  sort  i  can  explain.  Jira  is  using  some  kind  of  manual  sort  or  sort  based  on  ID’s  that  is  for  robots.

n Allow  shared  filters  and  dashboards  to  be  edited  by  a  group  or  more  then  one  user.  https://jira.atlassian.com/browse/JRA-­17783

n Filters  in  Filter  is  smart  and  efficiant,  but  when  a  gadget  like  Calendar  uses  some  other  search  engine  the  result  is  surprising  and  confusing.

17

Summary

n It  takes  time  to  get  it  perfect.

n Set  standards  and  use  them.– Terminology.– Workflows.

n Information,  education  and  local  support.

n Be  Agile  & Lean.

n It  will  never  be  perfect.

18

19

Thank  you  for  listening

Questions.

"Treat  the  earth  well:  it  was  not  given  to  you  by  your  parents,  it  was  loaned  to  you  by  your  children.  We  do  not  inherit  the  Earth  from  our  Ancestors,  we  borrow  it  from  our  Children."