Download as PDF, PPTX
Uploaded byStiltsoft
Confluence Cloud Mobile
The document discusses the structure and processes of the Confluence Cloud Mobile team at Atlassian. It covers their team structure with 4 verticals and over 200 people total. It also discusses how they ensure quality with peer testing, biweekly blitz sessions, and test automation. Key decisions are made using a DACI framework. Releases utilize feature flags for phased rollouts and rollbacks, and engineers participate in on-call rotations to resolve incidents.
Confluence Cloud Mobile
- 2. SIARHEI BARYSENKA |PRINCIPAL IOS ENGINEER | ATLASSIAN AMSTERDAM Confluence Cloud Mobile: An Overview StiltSoft Atlassian Day 2019
- 3.
- 4.
- 5.
- 6.
- 7.
- 8. >200 people in totalwork for Confluence Cloud
- 9. ~30 people work formobile version
- 10.
- 11. CONTENT EXP. Deliver content creationexperience to help users move work forward
- 12. CONTENT EXP. Deliver content creationexperience to help users move work forward Ownership: • create/edit/publish, • content rendering, • page restrictions
- 13. DISCO. & ORG. Helpusers organize, find, and discover information from their teams
- 14. DISCO. & ORG. Helpusers organize, find, and discover information from their teams Ownership: • search & page tree, • Your Work & Activity dashboards, • space directory & overview
- 15. COLLABORATION Empower teams to engagemeaningfully and move work forward
- 16. COLLABORATION Empower teams to engagemeaningfully and move work forward Ownership: • notifications, • collaborative actions (comments, likes, and shares)
- 17. COLLABORATION Empower teams to engagemeaningfully and move work forward Ownership: • notifications, • collaborative actions (comments, likes, and shares)
- 18. BACKBONE Propel dev experience, velocity, andoperational excellence
- 19. BACKBONE Propel dev experience, velocity, andoperational excellence Ownership: • cross-cutting services (e.g. networking), • auth, • deep links
- 20.
- 21. 0 manual QA engineersinvolved
- 22. Manual QA dutiesare shared across all members of the team PEER TESTING
- 23.
- 24. PEER TESTING “In PeerTest” The column is used to indicate tasks required to be tested by a peer
- 25. PEER TESTING “In PeerTest” The column is used to indicate tasks required to be tested by a peer Assignee An engineer from your vertical
- 26. Team gets togetheronce in two weeks before the release to verify critical functionality BLITZ SESSIONS
- 27.
- 28. BLITZ SESSIONS Checklist Describes thefunctionality to verify during the Blitz
- 29. BLITZ SESSIONS Checklist Describes thefunctionality to verify during the Blitz Failures If functionality doesn’t work, the bug is reported
- 30. BLITZ SESSIONS Checklist Describes thefunctionality to verify during the Blitz Failures If functionality doesn’t work, the bug is reported Prioritization Bugs are triaged to respective verticals, and prioritized to identify whether the release should be put on hold
- 31. Company-wide investment into thetools and practices of automated quality control TEST AUTOMATION
- 32.
- 33. TEST AUTOMATION Unit &UI tests Run on each pull request
- 34. TEST AUTOMATION Unit &UI tests Run on each pull request End-to-end tests Run on schedule
- 35. TEST AUTOMATION Unit &UI tests Run on each pull request End-to-end tests Run on schedule Goal Lower the effort of manual testing due to constantly increasing coverage achieved by automated tests
- 36.
- 37. What if oneneeds to make an engineering decision on a topic that have multiple opinions? MAKING DECISIONS
- 38. At Atlassian, one wouldmake a DACI MAKING DECISIONS
- 39. DACI is aframework that helps making group decisions efficiently and effectively DACI
- 40. What does DACIstand for?
- 41. What does DACIstand for? Driver A person responsible for gathering all the necessary information and getting a decision made by the agreed date
- 42. What does DACIstand for? Driver A person responsible for gathering all the necessary information and getting a decision made by the agreed date Approver A person who makes the decision
- 43. What does DACIstand for? Contributors They have knowledge or expertise that may influence the decision – i.e., they have a voice, but no vote Driver A person responsible for gathering all the necessary information and getting a decision made by the agreed date Approver A person who makes the decision
- 44. What does DACIstand for? Contributors They have knowledge or expertise that may influence the decision – i.e., they have a voice, but no vote Informed They are informed of the final decision Driver A person responsible for gathering all the necessary information and getting a decision made by the agreed date Approver A person who makes the decision
- 45. An example ofDACI
- 47. DACI persons Group ofpeople relevant to this decision
- 48. Status Current status ofDACI, and a place to eventually state which option you go with
- 49. Due date The deadlinefor making the decision
- 50. Recommendations Opinions from yourcontributors
- 51. Background The reasons thisdecision is required
- 54. Current state Where you'reat right now
- 55. Supporting data The researchyou've done to inform your decision
- 58. Options considered A tablewith a column for each option where you can summarise pros n' cons, risks, trade-offs, estimated cost or effort, etc
- 61. References A list oflinks out to reference material, along with a brief description of why it's relevant
- 62. Discussion A place todiscuss things and share concerns
- 63.
- 64.
- 65. Ship new featuressafely, without causing customer pain through unexpected outcomes FEATURE FLAGS
- 66.
- 67. FEATURE FLAGS Phased roll-outs Allowsto ship features to the smaller audiences and identify issues earlier
- 68. FEATURE FLAGS Phased roll-outs Allowsto ship features to the smaller audiences and identify issues earlier Easy roll-backs If something goes out of plan, it’s easy to turn off the feature
- 69. Engineers are involvedinto the on-call rotation to help resolving production issues INCIDENT RESOLUTION
- 70.
- 71.
- 72. On-call responsibilities Identify severityDisable phased roll-out
- 73. On-call responsibilities Investigate &fix the issue Identify severity Disable phased roll-out
- 74. On-call responsibilities Investigate &fix the issue Submit a new build Identify severity Disable phased roll-out
- 75. SIARHEI BARYSENKA |PRINCIPAL IOS ENGINEER | ATLASSIAN AMSTERDAM Thank you! StiltSoft Atlassian Day 2019