Your SlideShare is downloading. ×
0
2<br />From Grassroots to Enterprise-wide<br />10 Tips for Growing JIRA from 5 Users to 800+<br />Kim Peppers<br />Verisig...
3<br />What Are We Talking About?<br />3<br /><ul><li>How JIRA Grew at Verisign
Challenges We Faced
Tips & Lessons Learned</li></li></ul><li>4<br />About Verisign<br /><ul><li>The trusted provider of Internet infrastructur...
Manages 2 of the world's 13 Internet root servers, - a.root-servers.net and j.root-servers.net
1100 People world-wide
~50 Products</li></ul>4<br />
StarTeam Migration Complete<br />Bugzilla Migration Complete<br />I became JIRA Admin<br />5<br />
6<br />Challenge: Implement Everything<br /><ul><li>Migrate existing issues from Bugzilla – 35 Projects
Status and Metrics live in Confluence
Integrate with Fisheye/Crucible
Train 75 people</li></ul>6<br />
7<br />Lesson: Don’t Create Utopia<br />7<br /><ul><li>Set manageable milestones for implementation
Get a subset working
The team will be excited to see things moving and working in JIRA
Simplify – start small and build on it</li></li></ul><li>8<br />Challenge: Manage the Change<br />8<br />Questions, Questi...
Representatives from Dev & QA
Met weekly</li></ul>9<br />
10<br />Challenge: Who Knows Best?<br /><ul><li>Admins know the tool thoroughly
Best implementation practices
What to avoid</li></ul>10<br />
11<br />Lesson Learned: Know Your Users<br />11<br /><ul><li>Learn how previous tool worked
Meet with Dev Leads
Configure JIRA to match
Permissions, Workflows
Let users get comfortable</li></li></ul><li>12<br />Challenge: Teach the People<br />12<br /><ul><li>75 new people need to...
Different classes for different audiences
JIRA Intro/On-boarding
Specific Topics
Filters & Dashboards
UI Navigation Tips & Tricks
Searching with JQL</li></li></ul><li>14<br />Challenge: A State for Every Step<br />14<br /><ul><li>Overly complicated wor...
Tightly controlled transitions
Not enough transitions</li></li></ul><li>15<br />Tip: Simple & Standard Workflows<br /><ul><li>As few states as possible
Fewer restrictions on Transitions
Reuse
Standard workflow for Bugs & Enhancements</li></ul>15<br />
Simple & Open<br />Complex & Restricted<br />
17<br />Challenge: Long Lists<br />17<br /><ul><li>Workflows, Screens, Schemes
Upcoming SlideShare
Loading in...5
×

From Grassroots to Enterprise-wide: 10 Tips for Growing JIRA from 5 Users to 800+

869

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
869
On Slideshare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
20
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Listen to your users!
  • Transcript of "From Grassroots to Enterprise-wide: 10 Tips for Growing JIRA from 5 Users to 800+"

    1. 1.
    2. 2. 2<br />From Grassroots to Enterprise-wide<br />10 Tips for Growing JIRA from 5 Users to 800+<br />Kim Peppers<br />Verisign<br />2<br />
    3. 3. 3<br />What Are We Talking About?<br />3<br /><ul><li>How JIRA Grew at Verisign
    4. 4. Challenges We Faced
    5. 5. Tips & Lessons Learned</li></li></ul><li>4<br />About Verisign<br /><ul><li>The trusted provider of Internet infrastructure services for the networked world.
    6. 6. Manages 2 of the world's 13 Internet root servers, - a.root-servers.net and j.root-servers.net
    7. 7. 1100 People world-wide
    8. 8. ~50 Products</li></ul>4<br />
    9. 9. StarTeam Migration Complete<br />Bugzilla Migration Complete<br />I became JIRA Admin<br />5<br />
    10. 10. 6<br />Challenge: Implement Everything<br /><ul><li>Migrate existing issues from Bugzilla – 35 Projects
    11. 11. Status and Metrics live in Confluence
    12. 12. Integrate with Fisheye/Crucible
    13. 13. Train 75 people</li></ul>6<br />
    14. 14. 7<br />Lesson: Don’t Create Utopia<br />7<br /><ul><li>Set manageable milestones for implementation
    15. 15. Get a subset working
    16. 16. The team will be excited to see things moving and working in JIRA
    17. 17. Simplify – start small and build on it</li></li></ul><li>8<br />Challenge: Manage the Change<br />8<br />Questions, Questions, Questions<br /><ul><li>How to determine what to change and when?</li></li></ul><li>9<br />Tip: Create a Steering Committee<br /><ul><li>Size = 5 People
    18. 18. Representatives from Dev & QA
    19. 19. Met weekly</li></ul>9<br />
    20. 20. 10<br />Challenge: Who Knows Best?<br /><ul><li>Admins know the tool thoroughly
    21. 21. Best implementation practices
    22. 22. What to avoid</li></ul>10<br />
    23. 23. 11<br />Lesson Learned: Know Your Users<br />11<br /><ul><li>Learn how previous tool worked
    24. 24. Meet with Dev Leads
    25. 25. Configure JIRA to match
    26. 26. Permissions, Workflows
    27. 27. Let users get comfortable</li></li></ul><li>12<br />Challenge: Teach the People<br />12<br /><ul><li>75 new people need to learn the tool quickly</li></li></ul><li>13<br />Tip: Lots of Training Classes<br />13<br /><ul><li>Keep them short (1 hour or less)
    28. 28. Different classes for different audiences
    29. 29. JIRA Intro/On-boarding
    30. 30. Specific Topics
    31. 31. Filters & Dashboards
    32. 32. UI Navigation Tips & Tricks
    33. 33. Searching with JQL</li></li></ul><li>14<br />Challenge: A State for Every Step<br />14<br /><ul><li>Overly complicated workflows
    34. 34. Tightly controlled transitions
    35. 35. Not enough transitions</li></li></ul><li>15<br />Tip: Simple & Standard Workflows<br /><ul><li>As few states as possible
    36. 36. Fewer restrictions on Transitions
    37. 37. Reuse
    38. 38. Standard workflow for Bugs & Enhancements</li></ul>15<br />
    39. 39. Simple & Open<br />Complex & Restricted<br />
    40. 40. 17<br />Challenge: Long Lists<br />17<br /><ul><li>Workflows, Screens, Schemes
    41. 41. Hard to scroll and find one</li></li></ul><li>18<br />Tip: Standard Naming Conventions<br /><ul><li>Prefix with Category Name
    42. 42. Include Object Type
    43. 43. “PPD Create Bug & Enhancement Screen”
    44. 44. “Naming Edit Story Test Screen”
    45. 45. Use Version Numbers</li></ul>18<br />
    46. 46. 19<br />Tip: Standard Naming Conventions<br />19<br />
    47. 47. 20<br />Challenge: We Want More!<br /><ul><li>People want more, more, more
    48. 48. How to add functionality without changing code?</li></ul>20<br />
    49. 49. 21<br />Tip: Empower with Plugins<br />21<br /><ul><li>Easy to increase functionality
    50. 50. 100s available
    51. 51. Is it supported?</li></li></ul><li>22<br />Plugins We Love<br /><ul><li>CustomWare Traffic Lights</li></ul>22<br />
    52. 52. 23<br />Plugins We Love<br /><ul><li>JIRA SU (Switch User)
    53. 53. JQL Enhancement Functions
    54. 54. VersionList</li></ul>23<br />
    55. 55. 24<br />Challenge: JIRA 24x7<br />24<br /><ul><li>With users across the world, availability is critical
    56. 56. Downtime has to be minimal</li></li></ul><li>25<br />Sys Admin Tips<br />25<br /><ul><li>Test EVERYTHING
    57. 57. 1 Test Server – 2 JIRA Instances
    58. 58. Link is published to users
    59. 59. Solid Backup/Recovery Process
    60. 60. Syncs to Test Server, including Attachments</li></li></ul><li>26<br />Sys Admin Tips<br /><ul><li>Planned Maintenance Window</li></ul>26<br />
    61. 61. 27<br />Challenge: Reading Minds<br />27<br /><ul><li>How is it working?
    62. 62. Are they using the cool features of the tool?</li></li></ul><li>28<br />Tip: Survey Users<br />28<br /><ul><li>Keep it short – 10 questions or less
    63. 63. Specific questions focus on user experience
    64. 64. Permissions, Notifications, Workflows, Reporting, Integrations
    65. 65. Follow-up with answers & solutions</li></li></ul><li>29<br />Survey Questions<br />29<br />
    66. 66. 30<br />User Survey: 3 Things We Learned<br /><ul><li>#1 - No consensus on how much email is enough
    67. 67. Custom Notification Schemes – Small, Medium, Large
    68. 68. Size determined how much email was generated
    69. 69. Project Team could choose </li></ul>30<br />
    70. 70. 31<br />User Survey: 3 Things We Learned<br /><ul><li>#2 - Create Screen = Simple, Edit Screen = Everything</li></ul>31<br />
    71. 71. 32<br />Simple isBetter!<br />32<br />
    72. 72. 33<br />User Survey: 3 Things We Learned<br /><ul><li>#3 - Different filter results in bug scrubs
    73. 73. Defined Standard Filter Templates & Shared Dashboards</li></ul>33<br />
    74. 74. 34<br />Sample Filter Template #1<br />PPD All Open Bugs per Project<br />Filter Fields:<br />Project: < > <br />Issue Type: Bug <br />Affects Versions: Any <br />Status: Open, Pending, Deferred, Working and Testing <br />34<br />
    75. 75. 35<br />Sample Filter Template #2<br />PPD Open Bugs by Release<br />Filter Fields:<br />Project: < > <br />Issue Type: Bug <br />Affects Versions: <x.1, x.2 …> <br />Status: Open, Pending, Deferred, Working and Testing  <br />35<br />
    76. 76. 36<br />Challenge: You Want to Track What in JIRA?<br /><ul><li>Easy for everyone to use
    77. 77. As JIRA’s popularity grew, so did creativity</li></ul>36<br />
    78. 78. 37<br />Tip: Push the Envelope – JIRA Isn’t Just for Bugs<br /><ul><li>Corporate Marketing Projects
    79. 79. Sys Admin Support Requests
    80. 80. Change Control Board Issues</li></ul>37<br />
    81. 81. 38<br />Our Star - Tracking Project Status<br /><ul><li>Replaced 100 weekly emails!</li></ul>38<br />
    82. 82. 39<br />Recap of 10 Tips<br />1. Don’t Create Utopia<br />2. JIRA Steering Committee<br />3. Training Classes<br />4. Know Your Users<br />5. Simple & Standard Workflows<br /><ul><li>6. Standard Naming Conventions
    83. 83. 7. Empower with Plugins
    84. 84. 8. Test Everything
    85. 85. 9. Survey Users
    86. 86. 10. Push the Envelope</li></ul>39<br />
    87. 87. “<br />Go home and create a JIRA Steering Committee and survey your users, even if you’ve been using JIRA for years.<br />”<br />#atlassiansummit<br />#summit11<br />40<br />
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×