Atlas Hugged: How Atlassian Tools Enabled a Software Internalization Team

  • 756 views
Uploaded on

Software internationalization requires the involvement of people around the world in different roles, from sales and marketing to engineering and management. Join Sarah as she tells the story of how …

Software internationalization requires the involvement of people around the world in different roles, from sales and marketing to engineering and management. Join Sarah as she tells the story of how the combination of Confluence and JIRA enabled QAD's Internationalization Team to come together and work closely to meet requirements efficiently and effectively.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
756
On Slideshare
0
From Embeds
0
Number of Embeds
4

Actions

Shares
Downloads
6
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

Transcript

  • 1. Atlas Hugged!How Atlassian tools enabled a softwareinternationalization team.!Sarah Day!Technical Writer, QAD Inc.!
  • 2. Introduction!
  • 3. Introduction!!Sarah Day, Technical Writer!
  • 4. Introduction! !QAD: Providing Enterprise Resource Planning software to global manufacturing companies. !
  • 5. Introduction! !Internationalization (I19): QAD s response to the demands of a global workforce with tight deadlines.!
  • 6. Introduction!•  Project History!
  • 7. Introduction!•  Project History!•  Transitions!
  • 8. Introduction!•  Project History!•  Transitions!•  User Friendliness!
  • 9. Introduction!•  Project History!•  Transitions!•  User Friendliness!•  Oversight!
  • 10. Introduction!•  Project History!•  Transitions!•  User Friendliness!•  Oversight!•  What s next?!
  • 11. Project History !
  • 12. Project History!
  • 13. Project History!Global teams face unique challenges!
  • 14. Project History!•  Generalizing production requirements!•  Facilitating new production requests!
  • 15. Project History!Production requirements and requests were maintained badly!
  • 16. Project History!Production requirements and requests were maintained badly! •  Excel spreadsheets!
  • 17. Project History!Production requirements and requests were maintained badly! •  Excel spreadsheets ! •  Lotus Notes databases!
  • 18. Project History!Production requirements and requests were maintained badly! •  Excel spreadsheets ! •  Lotus Notes databases! •  Email threads!
  • 19. Project History!Inconsistent information management handicapped development!
  • 20. Project History!Inconsistent information management handicapped development! •  Documents were difficult to find!
  • 21. Project History!Inconsistent information management handicapped development! •  Documents were difficult to find! •  Work requirements were often missed or misplaced!
  • 22. Project History!Inconsistent information management handicapped development! •  Documents were difficult to find! •  Work requirements were often missed or misplaced! •  Redundancies in the system meant some work was done twice!
  • 23. Project History!! And then... !
  • 24. Project History!! There was Confluence. !
  • 25. Transitions !
  • 26. Transitions!!QDN gave R&D a home base for development !!
  • 27. Transitions!!The Internationalization space was born!!!!
  • 28. User Friendliness !
  • 29. User Friendliness!!
  • 30. User Friendliness!!•  Simple language!
  • 31. User Friendliness!!•  Simple language!•  Easy access!
  • 32. User Friendliness!County centers! •  Information about each country!
  • 33. User Friendliness!County centers! •  Information about each country! •  Release readiness status imported from JIRA!
  • 34. User Friendliness!County centers! •  Information about each country! •  Release readiness status imported from JIRA! •  Team contacts!
  • 35. User Friendliness!I19 Request Form! •  Template-driven workflow! •  Comalatech’s Ad Hoc Workflow plugin!
  • 36. User Friendliness!!•  Different stages have labels assigned to them automatically!•  Labels trigger emails to team members!!
  • 37. User Friendliness!!The workflow practically runs itself!!
  • 38. User Friendliness!•  Implementation challenges!
  • 39. User Friendliness!•  Implementation challenges!•  User conversion!
  • 40. Oversight !
  • 41. Oversight!!Total managerial supervision!
  • 42. Oversight!!Transparency facilitates group work!!
  • 43. What s Next?!
  • 44. Whats Next?!!Our I19 space is thriving… what now?!
  • 45. Whats Next?!!Our I19 space is thriving… what now?!•  Team spaces?!
  • 46. Whats Next?!!Our I19 space is thriving… what now?!•  Team spaces?!•  Content management QAD-wide?!
  • 47. Wrap-Up!
  • 48. We went from…!•  Too many layers!
  • 49. We went from…!•  Too many layers! •  Two layers!
  • 50. We went from…!•  Too many layers! •  Two layers!•  User confusion!
  • 51. We went from…!•  Too many layers! •  Two layers!•  User confusion! •  Universal transparency!
  • 52. We went from…!•  Too many layers! •  Two layers!•  User confusion! •  Universal transparency!•  Tedious updating!
  • 53. We went from…!•  Too many layers! •  Two layers!•  User confusion! •  Universal transparency!•  Tedious updating! •  Self-advancing workflows!
  • 54. We went from…!•  Too many layers! •  Two layers!•  User confusion! •  Universal transparency!•  Tedious updating! •  Self-advancing workflows!•  Redundancy and errors!
  • 55. We went from…!•  Too many layers! •  Two layers!•  User confusion! •  Universal transparency!•  Tedious updating! •  Self-advancing workflows!•  Redundancy and errors! •  Streamlined processes!
  • 56. Thank you!