Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Our experience with implementing the Atlassian product suite - Peter Hinds, Synergy Learning

5 views

Published on

Presentation delivered at Atlassian in Scotland 2019, 19th March 2019, Glasgow by Peter Hinds, Synergy Learning. Peter is the Head of Operations at Synergy Learning, a leading provider
of e-learning solutions. Peter shared his experiences of implementing the Atlassian product suite at Synergy.

Published in: Business
  • Be the first to comment

  • Be the first to like this

Our experience with implementing the Atlassian product suite - Peter Hinds, Synergy Learning

  1. 1. Hi! Peter Hinds Synergy Learning
  2. 2. Who are Synergy Learning? 2 Full Service Provider of Learning Technology ● Partner - 2005 ● Platinum Partner - 2011
  3. 3. Companies we work with 3
  4. 4. Once upon a time..
  5. 5. Starting out with Atlassian 5 ▪ Simple in-house version control (Git) server ▪ Wanted to introduce a GUI ▪ (Very!) Brief comparison between BitBucket & GitHub ▪ Similar feature sets ▪ BitBucket chosen purely on price
  6. 6. Bitbucket - Code Reviews 6
  7. 7. Bitbucket Pull Requests 7
  8. 8. Introduction of Jira 8 ▪ Introduced Jira in 2011 ▪ Originally only for Dev team ▪ Supporting applications (to name a few!) ○ Harvest - Time Tracking ○ Forecast - Project Planning ○ MavenLink - Rest of the Operations Team ○ Desk.com - Support Team ○ Skype - Internal comms
  9. 9. Post Jira Implementation 9 Key Remaining Issues ● Documentation remained distributed ○ Local files, Google Docs, Google Sites & “in peoples heads”. ● No standard workflows ● c. 2016 - Eventually we reached a point where the chaotic nature was a hindrance ● We agreed it was time to invest in standardising
  10. 10. Next steps: 10 ● Reviewed several competitors to Jira ● Long term partner - Decision had to be “right”. Pros: ● Our Dev Team well integrated into Jira ● We had built up a lot of active projects. ● Useful information on closed project issues ● Less of a learning curve more of a refinement
  11. 11. Moodle Plugins 11
  12. 12. Increasing our use of Jira 12 ▪ Company wide review of workflows & processes ▪ Optimised Workflows (at least we thought we did!) ▪ Moved from Jira Cloud to Jira Server ▪ Implemented workflows into Jira
  13. 13. Tempo Timesheets 13 ● Replaced Harvest with Tempo Timesheets ● Integration with Jira Server the key ● Useful reports ● Encourage people to use “Tracker” ● Post early / Post Often ● Weekly Submission (can be monthly)
  14. 14. Tempo Planner 14 ▪ Harvest / Forecast were the most loved ○ No Jira Server integration! ▪ Using Tempo Timesheets so felt sensible to use Tempo Planner too Goals: ▪ Everyone should have an understanding of the project ▪ Everyone should know what they’re working on ▪ Everyone should be fairly allocated work
  15. 15. Jira Service Desk 15 ● Initially quite sceptical of Jira Service Desk ○ Felt like it had been built for Internal IT Support ● Proven to be a great fit ● SLA’s monitors are fantastic! ● Humans = Challenge ○ Encouraging customers towards portal is difficult
  16. 16. Evolution
  17. 17. Project Planning 17 ● Planned Time doesn’t correspond to “Due Date” of an issue ○ Feedback was to have these in sync ● If you changed it in one you had to manually change it in the other ● No project view - Project Planners yearned for Forecast
  18. 18. BigPicture Enterprise 18 ● Full integration with Jira - configured the “End Date” to use “Due Date” ● Compatible & syncs with with Tempo Teams ● Resources Modules - Similar view to Tempo Planner & Harvest ● Gantt module - provides the overall project plan
  19. 19. BigPicture Enterprise 19
  20. 20. Hierarchy in Jira 20 Attempt to introduce a hierarchy ● Jira Project = Customer ● Epic = Synergy Learning Project ● Issue = Deliverable Item ● Worked OK within Jira but made reporting more difficult ● Increased admin - “Issue had to be linked to correct Epic” ● Made planning projects more complex
  21. 21. Profields 21 ● Discovered ProFields plugin ● Saw reporting of Profields in EazyBI at their Community Day ● Switched to Jira Projects = Projects ● Small concern over number of projects & scaling - on our watch list. ● Would like to see project archiving function from “Jira Data Center” in Jira Server
  22. 22. Profields 22 Key information centrally available Layout changes or new fields are pushed to all associated projects. PQL - Ability to query & filter projects same
  23. 23. Structure & Workflows 23 ● The company wide review we conducted was incredibly thorough ● Insightful for the business ● Do not map these 1:1 into Jira workflows ● We had a status & transition for *everything*! ● People quickly lost interest in statuses ○ “I just need to get this done” ● Simplified our workflows
  24. 24. Reporting - EazyBI 24 ● EazyBI Community Day - May 2018 ● Fascinating to see what was possible ● Knew fairly quickly we needed help ● Consultancy with New Verve to define reports ● Development with New Verve to build
  25. 25. Reporting - EazyBI 25
  26. 26. Reporting - EazyBI 26
  27. 27. Reporting - EazyBI 27
  28. 28. Reporting - EazyBI 28
  29. 29. Worth a mention! 29 1. SLA Alerts for Jira ServiceDesk 2. Time to SLA 3. Doublecheck 4. Zephyr
  30. 30. Future
  31. 31. Future Plans 32 ● Retire Crowd SSO ○ “Crowd does not recognize Service Desk Customers as distinct from JIRA users” Several issues marked as “Won’t fix”. Costing us a fortune! ○ Single Point of Failure ○ Integrate with our JumpCloud (Directory as a Service)
  32. 32. Future Plans / Wishlist 33 ● Jira Server - Gain reassurance over longevity / roadmap ○ Jira Cloud development rapid. Next-gen projects <--- want! ○ Data Centre gaining desirable features ■ Project Archiving ● Confluence offline - GDocs often used for “drafts” when travelling ● Improve issue “screens” configuration
  33. 33. Future Plans / Wishlist 34 ● Jira 8 - Batched notifications & Performance Improvements ● Full Slack Integration - Server implementation lacks “Add to issue” ● JiraOps & OpsGenie ● Increase use of Tempo Accounts ● Tempo Budgets - Early investigation work started
  34. 34. Thanks!

×