Your SlideShare is downloading. ×
From Grassroots to Enterprise-wide: 10 Tips for Growing JIRA from 5 Users to 800+
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

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

841
views

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
841
On Slideshare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
20
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Listen to your users!
  • Transcript

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

    ×