Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.
VI/ Atlassian

The life of a feature: 

Best practices for shipping quality
features in a timely manner

4%? 

JOE CLARK -...
, . .l. P*. 

'.  ' T‘: """! !|II! .=. =:aa+«:  i.  

. _.. ,g _. ,
L’
How do you build a
feature?
//1,‘ I '3 9 J
/ I
I {lo
I
1;’ 5'0
!  ‘ . .a—. .
N3.
$3. I.  ""'
l

  -, .;‘.  
». _r’:  '~_ _. I_ ‘ , -_~‘ .  ‘ ,  - -. . w.
Development is the simplest
part of the feature lifecycle
Development
Discovery
Development
Delivery
Discovery
Where do good
features come
from?
'l
a I
Customers

'l
a
5

 

Customers

l
Discovery

PUBLIC ISSUE TRACKING
))

Search

JIRA

Dashboards

Projects

Save as

 

Issues Agile Capture reate

0 project =  JIRA and type =  "Suggestion"...
© Suggestions from real,  invested customers
© Suggestions from real,  invested customers

@ Stronger relationship between devs and users
© Suggestions from real,  invested customers
@ Stronger relationship between devs and users

® Validation and weighting of...
Ir.  . _.  . .. . ... 
¥. _4. r./ ..  / / V .  , rz.   . 
_ .  _,    _
V _,  s  c.  . /  .
/  1 .  .  . .
H4 ,  . _ . 
I
....
'l
a I
ffllffifl

Your Engineering Team

I
Atlassian spends

34%

of revenue on R&D
Discovery

l PUBLIC ISSUE TRACKING J

ALLOW CREATIVE TIME
20°/ o Time
2(Cl‘%

 lvltlassiani 
gaf1‘lF—,  i i_

 

20% Time Shiplt
‘F14 "
‘ r
EH9)? ‘

lbnov
 ‘:2


EN’  
r«’~= "

i
/ SIX ‘. :s: ;‘
. -

-z, ,,,  n

 -"ht
EPOn§mEl

4’

5.»!  . "' 4‘ —% g
...
Each initiative creates
valuable results
..4.. 

 

u
eve l e p  e hi
Development is not abut
the “lone coder”
I.  .

I 3
. n  .  .2
M  u
. . .  z & 4
 ;  I. 
- ix
/  o
xi »
.  a .83. . 
3 . iv .  lit
 I,  i / ..
Software development
is a collaborative endeavour
1400

1050

700

350

Growth of Atlassian Employees

2009-2014

2009

2010

2011

Atlassian Employees

2012

2013

2014
‘l
a
Development

RELEASE INDEPENDENTLY
~

54.: 
.. m

. .@/ .u

~

RGMI
. .m

m. mwv. I

~

pawl
. .ew». u

'l
a 1
'l
a 1
'l
1 1
L in 1
?@

“ This module is owned by the other team,  so I
shouldn’t change this code.  ”

'l
‘Q “ My team only works on this feature,  so I don’t
I
g need to learn the other parts of the system. ”

'I
‘Q “ We need more work on the backlog.  Let’s add
3
9 some more features to this component. ”

-«I
Teams still need to be
empowered to improve the
entire product
Development

i RELEASEINDEPENDENTLY J

ALIGN TEAMS WITH THEMES
DUDE

DUDE
DDUDD DUDE
EDD DUDDDD

DUUDDU
DUDDUD

  

'»I

ll
DDDD

DDDD
DDDDD DUDE
DDD DDDDDD

DDDDDD
DDDDDD

    

'»I

ll
DDDD
DDDD

DIDDD ln_n_n_
IDI DDDIID
IDDDDI
DDIDID
Arrange your teams to
achieve your product’s goals
_. .r

.1
Delivery
.1

, _ 5.27 7 If V V Ai_u_ -* .  ' ___
. .s= ”=‘t lei at ,  “P’e1~‘; ”“’""'.  . 
r, :'. ... ... ... “*«~*»   as I

. ‘<“"...
fixes the bus?
. u 
. , .  ..  T
T Q
:  z .  q »‘A . c.. 
..   
.  . . — L . 
. 5 . 
I . _, .1 M.  . .  .
. .,.  .6 I.  R . 
. . 
. . . . ...   - .  .
I c ...
The bug-fix team should
focus on long-term stability, 
not new regressions
Delivery

FEATURE WARRANTIES
Any bugs identified within
3 months of a release,  must
be fixed by the team that
caused them.
100

75

50

25

0

Open Warranty Bugs
Confluence Team - 2014

11-2013 12-2013 01-2014 02-2014 03-2014 04-2014 05-2014 06-2...
iii  Ll itjixi _l'i  .  .
Innovate together
Release independently
Share responsibility
May the force be with you

‘D
YAtlassian

Thank you! 

JOE CLARK - ATLASSIAN - ECLIPSECON 2014 - @JAYSEE00
Attributions

- http: //en. wikipedia. org/ wiki/ Fi| e:GoldenGateBridge-001.jpg

- Description:  The Golden Gate Bridge a...
Attributions

- Font Awesome by Dave Gandy - http: //fontawesome. io"
- License:  http: //scripts. si| .org/ OFL

- Images...
The life of a feature: Best practices for shipping quality features in a timely manner – Joseph Clark
The life of a feature: Best practices for shipping quality features in a timely manner – Joseph Clark
The life of a feature: Best practices for shipping quality features in a timely manner – Joseph Clark
The life of a feature: Best practices for shipping quality features in a timely manner – Joseph Clark
The life of a feature: Best practices for shipping quality features in a timely manner – Joseph Clark
The life of a feature: Best practices for shipping quality features in a timely manner – Joseph Clark
The life of a feature: Best practices for shipping quality features in a timely manner – Joseph Clark
The life of a feature: Best practices for shipping quality features in a timely manner – Joseph Clark
The life of a feature: Best practices for shipping quality features in a timely manner – Joseph Clark
Nächste SlideShare
Wird geladen in …5
×

The life of a feature: Best practices for shipping quality features in a timely manner – Joseph Clark

Joseph Clark's (Atlassian) presentation about best practices for shipping quality features in a timely manner.

  • Loggen Sie sich ein, um Kommentare anzuzeigen.

The life of a feature: Best practices for shipping quality features in a timely manner – Joseph Clark

  1. 1. VI/ Atlassian The life of a feature: Best practices for shipping quality features in a timely manner 4%? JOE CLARK - ATLASSIAN - ECLIPSECON 2014 - @JAYSEE00
  2. 2. , . .l. P*. '. ' T‘: """! !|II! .=. =:aa+«: i. . _.. ,g _. ,
  3. 3. L’
  4. 4. How do you build a feature?
  5. 5. //1,‘ I '3 9 J / I I {lo I 1;’ 5'0 ! ‘ . .a—. . N3. $3. I. ""'
  6. 6. l -, .;‘. ». _r’: '~_ _. I_ ‘ , -_~‘ . ‘ , - -. . w.
  7. 7. Development is the simplest part of the feature lifecycle
  8. 8. Development
  9. 9. Discovery Development Delivery
  10. 10. Discovery
  11. 11. Where do good features come from?
  12. 12. 'l a I
  13. 13. Customers 'l a
  14. 14. 5 Customers l
  15. 15. Discovery PUBLIC ISSUE TRACKING
  16. 16. )) Search JIRA Dashboards Projects Save as Issues Agile Capture reate 0 project = JIRA and type = "Suggestion" order by creat. edDate desc 1-50 of 15462 -I D O O CUE O O O Q E Key JRA—40426 JRA-40425 JRA—40424 JRA-40423 JRA-40422 JRA-40418 JRA-40417 JRA-40415 JRA-40413 JRA-40412 JRA-40408 JRA-40407 JRA~40401 Summary Aellgrlee Hide "License" details in "Guide for JIRA Administrators" gadget for OnDemand Unassigned Peperiksaan Pegawai Tadbir Diplomatik Unassigned Need for comment numbers and linking Unassigned Add user replacements in projects Unassigned Allow all assignable users when using Current User Security Level Unassigned Ability to add a second URL field on the Edit Project Details Unassigned Import from CSV (Bulk Create) documentation Warren Thompson Ability to change Audit Log Rentention Period to 1 day or Disabling Audit Logs Unassigned Change the create date of reopen issue to renew date Unassigned Use Project Management in the name of the schemes for projects created via the Project Unassigned Management Template Doc update for Dragons Stage 2 - JIRA Add-Ons Warren Thompson Update Pie Chart Documentation Warren Thompson JIRA view issue layout Unassigned Reporter Nick Mason ami seop SSR SelvamRaju Marcus Silveira Marcus Silveira Luciano Fagundes Woo Yit Wei Janice Alor Maria Yang Oswaldo Hemandez Morgan Knicely Elisa Diel Aqqiela Zuhra 2 Share I Exp (‘D Q Status Resolution Cre open Unresolved 14/ OPEN Unresolved 14/ OPEN Unresolved 14/ OPEN Unresolved 14/ OPEN Unresolved 14/ OPEN Unresolved 14/ OPEN Unresolved 14/ open Unresolved 14/ over: Unresolved 14/ open Unresolved 13/ open Unresolved 13/ caoszo Done 13/ OPEN Unresolved 13/
  17. 17. © Suggestions from real, invested customers
  18. 18. © Suggestions from real, invested customers @ Stronger relationship between devs and users
  19. 19. © Suggestions from real, invested customers @ Stronger relationship between devs and users ® Validation and weighting of existing ideas
  20. 20. Ir. . _. . .. . ... ¥. _4. r./ .. / / V . , rz. . _ . _, _ V _, s c. . / . / 1 . . . . H4 , . _ . I . ,. ... . S “K . . c . / ~ ‘ » . .. I .7. C. ., m . .. , WA . Ks. S ( / . . .- . 5 4 : . / . l. ’. >14 .
  21. 21. 'l a I
  22. 22. ffllffifl Your Engineering Team I
  23. 23. Atlassian spends 34% of revenue on R&D
  24. 24. Discovery l PUBLIC ISSUE TRACKING J ALLOW CREATIVE TIME
  25. 25. 20°/ o Time
  26. 26. 2(Cl‘% lvltlassiani gaf1‘lF—, i i_ 20% Time Shiplt
  27. 27. ‘F14 " ‘ r EH9)? ‘ lbnov ‘:2 EN’ r«’~= " i / SIX ‘. :s: ;‘ . - -z, ,,, n -"ht EPOn§mEl 4’ 5.»! . "' 4‘ —% g V» ~ '3‘ K2: 4/” ' : #iT?1 . r '4'? ’ ii’? "ire-J‘ . -——~ ‘ i ‘ ~: , /’”
  28. 28. Each initiative creates valuable results
  29. 29. ..4.. u
  30. 30. eve l e p e hi
  31. 31. Development is not abut the “lone coder”
  32. 32. I. . I 3 . n . .2 M u . . . z & 4 ; I. - ix / o xi » . a .83. . 3 . iv . lit I, i / ..
  33. 33. Software development is a collaborative endeavour
  34. 34. 1400 1050 700 350 Growth of Atlassian Employees 2009-2014 2009 2010 2011 Atlassian Employees 2012 2013 2014
  35. 35. ‘l a
  36. 36. Development RELEASE INDEPENDENTLY
  37. 37. ~ 54.: .. m . .@/ .u ~ RGMI . .m m. mwv. I ~ pawl . .ew». u 'l a 1
  38. 38. 'l a 1
  39. 39. 'l 1 1
  40. 40. L in 1
  41. 41. ?@ “ This module is owned by the other team, so I shouldn’t change this code. ” 'l
  42. 42. ‘Q “ My team only works on this feature, so I don’t I g need to learn the other parts of the system. ” 'I
  43. 43. ‘Q “ We need more work on the backlog. Let’s add 3 9 some more features to this component. ” -«I
  44. 44. Teams still need to be empowered to improve the entire product
  45. 45. Development i RELEASEINDEPENDENTLY J ALIGN TEAMS WITH THEMES
  46. 46. DUDE DUDE DDUDD DUDE EDD DUDDDD DUUDDU DUDDUD '»I ll
  47. 47. DDDD DDDD DDDDD DUDE DDD DDDDDD DDDDDD DDDDDD '»I ll
  48. 48. DDDD DDDD DIDDD ln_n_n_ IDI DDDIID IDDDDI DDIDID
  49. 49. Arrange your teams to achieve your product’s goals
  50. 50. _. .r .1
  51. 51. Delivery
  52. 52. .1 , _ 5.27 7 If V V Ai_u_ -* . ' ___ . .s= ”=‘t lei at , “P’e1~‘; ”“’""'. . r, :'. ... ... ... “*«~*» as I . ‘<“"I. »b'-’r‘-: -1‘-. ' S "'¢"": "““§"“‘§*"5‘2’1"““““’T"fi'. *"’ . . -_. 'i. . . . _ / /7 “i
  53. 53. fixes the bus?
  54. 54. . u . , . .. T
  55. 55. T Q : z . q »‘A . c.. .. . . . — L . . 5 . I . _, .1 M. . . . . .,. .6 I. R . . . . . . . ... - . . I c - . . « I. ., .. . 0.? . .1 _ . ‘Q. : Vu '. I / . . ,3 i . v. u M . t _. aw, . I . .-
  56. 56. The bug-fix team should focus on long-term stability, not new regressions
  57. 57. Delivery FEATURE WARRANTIES
  58. 58. Any bugs identified within 3 months of a release, must be fixed by the team that caused them.
  59. 59. 100 75 50 25 0 Open Warranty Bugs Confluence Team - 2014 11-2013 12-2013 01-2014 02-2014 03-2014 04-2014 05-2014 06-2014 07-2014 08-2014 09-2014 I Bugs
  60. 60. iii Ll itjixi _l'i . .
  61. 61. Innovate together
  62. 62. Release independently
  63. 63. Share responsibility
  64. 64. May the force be with you ‘D
  65. 65. YAtlassian Thank you! JOE CLARK - ATLASSIAN - ECLIPSECON 2014 - @JAYSEE00
  66. 66. Attributions - http: //en. wikipedia. org/ wiki/ Fi| e:GoldenGateBridge-001.jpg - Description: The Golden Gate Bridge and San Francisco, CA at sunset. - Date: 1 January 2007 - Source: http: //www. projectrich. com/ gallery - Author: Rich Niewiroski Jr. - License: Creative Commons - http: //en. wikipedia. org/ wiki/ File: Crawford, _Dzingai_200_m_Ber| in_2009.jpg - Description: Shawn Crawford wahrend seines 200m Semifinales - Date: 18August 2009 - Source: Leichtathletik WM 2009 Berlin - Author: André Zehetbauer from Schwerin, Deutschland - License: Creative Commons
  67. 67. Attributions - Font Awesome by Dave Gandy - http: //fontawesome. io" - License: http: //scripts. si| .org/ OFL - Images from Star Wars, Empire Strikes Back and Return of the Jedi - Copyright 1977 - 2014, LucasFilm Ltd - Reproduced under the Fair Use provisions of US Copyright law - All other content Copyright 2014, Atlassian Inc.

×