This document provides 10 tips for growing usage of JIRA from 5 users to 800 users based on the experience of Verisign. Some of the key tips include: 1. Set manageable milestones and start small when implementing JIRA instead of trying to achieve everything at once. 2. Create a steering committee of users to help determine what changes to make and when. 3. Conduct user surveys to understand how people are using the tool and identify areas for improvement. 4. Empower users by using plugins to add functionality without changing code. 5. Standardize workflows, naming conventions, and other aspects to simplify usage and maintenance.

2. 2 From Grassroots to Enterprise-wide 10 Tips for Growing JIRA from 5 Users to 800+ Kim Peppers Verisign 2

4. Challenges We Faced

6. Manages 2 of the world's 13 Internet root servers, - a.root-servers.net and j.root-servers.net

7. 1100 People world-wide

8. ~50 Products4

9. StarTeam Migration Complete Bugzilla Migration Complete I became JIRA Admin 5

11. Status and Metrics live in Confluence

12. Integrate with Fisheye/Crucible

13. Train 75 people6

15. Get a subset working

16. The team will be excited to see things moving and working in JIRA

18. Representatives from Dev & QA

19. Met weekly9

21. Best implementation practices

22. What to avoid10

24. Meet with Dev Leads

25. Configure JIRA to match

26. Permissions, Workflows

28. Different classes for different audiences

29. JIRA Intro/On-boarding

30. Specific Topics

31. Filters & Dashboards

32. UI Navigation Tips & Tricks

34. Tightly controlled transitions

36. Fewer restrictions on Transitions

37. Reuse

38. Standard workflow for Bugs & Enhancements15

39. Simple & Open Complex & Restricted

42. Include Object Type

43. “PPD Create Bug & Enhancement Screen”

44. “Naming Edit Story Test Screen”

45. Use Version Numbers18

46. 19 Tip: Standard Naming Conventions 19

48. How to add functionality without changing code?20

50. 100s available

53. JQL Enhancement Functions

54. VersionList23

57. 1 Test Server – 2 JIRA Instances

58. Link is published to users

59. Solid Backup/Recovery Process

63. Specific questions focus on user experience

64. Permissions, Notifications, Workflows, Reporting, Integrations

67. Custom Notification Schemes – Small, Medium, Large

68. Size determined how much email was generated

69. Project Team could choose 30

71. 32 Simple isBetter! 32

73. Defined Standard Filter Templates & Shared Dashboards33

74. 34 Sample Filter Template #1 PPD All Open Bugs per Project Filter Fields: Project: < > Issue Type: Bug Affects Versions: Any Status: Open, Pending, Deferred, Working and Testing 34

75. 35 Sample Filter Template #2 PPD Open Bugs by Release Filter Fields: Project: < > Issue Type: Bug Affects Versions: <x.1, x.2 …> Status: Open, Pending, Deferred, Working and Testing 35

77. As JIRA’s popularity grew, so did creativity36

79. Sys Admin Support Requests

80. Change Control Board Issues37

83. 7. Empower with Plugins

84. 8. Test Everything

85. 9. Survey Users

86. 10. Push the Envelope39

87. “ Go home and create a JIRA Steering Committee and survey your users, even if you’ve been using JIRA for years. ” #atlassiansummit #summit11 40