Atlassian builds tools for all teams... including ourselves! There's no right or wrong way to use our tools, but we've developed some best practices that a lot of our teams have adopted. In this session you will learn how an Atlassian developer uses JIRA, Confluence, HipChat, BitBucket, and Bamboo to plan, build, test, and continuously deploy HipChat. You will also learn some tips and tricks for using the Atlassian toolset to take a project from a concept to a released application. David Cruz, Senior Software Developer - HipChat Desktop, Atlassian

1. A Day in the Life of a
HipChat Developer
DAVID CRUZ | SENIOR SOFTWARE DEVELOPER | ATLASSIAN | @CRUZERLD

2. Introduction

3. My Typical Day

4. Automation
What can be automated
should be automated.
Our Project Values
Confidence
Code and deploy with
confidence.
Transparency
Allow your stakeholders to
know your progress.

5. Agenda
Transparency
Automation
Confidence

7. Internal
For your team
External
For your stakeholders
Transparency

8. TRANSPARENCY
Milestone
development
encourages
transparency.

9. Iterative
Breaks up a large project into a set of
deliverables
Get early feedback
Facilitates creating and distributing an MVP
internally and to prospective customers
Know your timeline
Allows you and your stakeholders to know if you
are meeting your estimates
Benefits of
Milestone
Development

10. Iterative
Breaks up a large project into a set of
deliverables
Get early feedback
Facilitates creating and distributing an MVP
internally and to prospective customers
Know your timeline
Allows you and your stakeholders to know if you
are meeting your estimates
Benefits of
Milestone
Development

11. Iterative
Breaks up a large project into a set of
deliverables
Get early feedback
Facilitates creating and distributing an MVP
internally and to prospective customers
Know your timeline
Allows you and your stakeholders to know if you
are meeting your estimates
Benefits of
Milestone
Development

13. TRANSPARENCY
Turn requirements
into features
Organize these features into
complete milestones
Each milestone
should end with a
deliverable
Milestones should be roughly
six weeks long

14. TRANSPARENCY
Turn requirements
into features
Organize these features into
complete milestones
Each milestone
should end with a
deliverable
Milestones should be roughly
six weeks long

15. TRANSPARENCY
We use JIRA and
agile development
to turn our
milestones into
tasks.

16. Turn features into
epics
Break epics up into individual tasks
JIRA and agile
development
Use Epics
Be Specific
Sort Tasks
Create Sprints

17. Tasks should be well
defined
Each will need a definition of done
and an estimate
JIRA and agile
development
Use Epics
Be Specific
Sort Tasks
Create Sprints

18. Order your tasks
You should always accomplish the
biggest tasks first
JIRA and agile
development
Use Epics
Be Specific
Sort Tasks
Create Sprints

19. Start with the highest
priority issues
Only drop in as many tasks as your
teams can handle
JIRA and agile
development
Use Epics
Be Specific
Sort Tasks
Create Sprints

21. Link Bitbucket
This allows you to create a
branch and shows you the state
of any pull requests.
JIRA INTEGRATIONS
Link Bamboo
This shows you how many
builds this ticket’s work is in
and the status of those builds.

22. Link Bitbucket
This allows you to create a
branch and shows you the state
of any pull requests.
JIRA INTEGRATIONS
Link Bamboo
This shows you how many
builds this ticket’s work is in
and the status of those builds.

25. TRANSPARENCY
Workflows can
enforce culture
Auto-transitions
encourage good
behavior
Helps streamline
our workflow

26. TRANSPARENCY
Workflows can
enforce culture
Auto-transitions
encourage good
behavior
Helps streamline
our workflow

27. TRANSPARENCY
Workflows can
enforce culture
Auto-transitions
encourage good
behavior
Helps streamline
our workflow

28. Agenda
Transparency
Automation
Confidence

30. Synchronous tasks
Automation
Tasks you might forgetRepetitive tasks

31. AUTOMATION
We use Bamboo to
automate
continuous
integration and
delivery.

32. What is CI / CD?
And why are they important?

34. https://xkcd.com/303/

35. Build and test every change
Automation should be among the first tasks you
do.
Test from the start
Your first tasks are often the core of your
product.
Build as if you were going to
deploy
No shortcuts!
Automation

36. Build and test every change
Automation should be among the first tasks you
do.
Test from the start
Your first tasks are often the core of your
product.
Build as if you were going to
deploy
No shortcuts!
Automation

37. Build and test every change
Automation should be among the first tasks you
do.
Test from the start
Your first tasks are often the core of your
product.
Build as if you were going to
deploy
No shortcuts!
Automation

38. AUTOMATION
What makes a
good build?

39. https://testing.googleblog.com/2015/04/just-say-no-to-more-end-to-end-tests.html
The Test Pyramid

41. Agenda
Transparency
Automation
Confidence

42. Knowledge
Know the state of your
project at all times.
Assurance
Testing and building is the
minimum of what you need.
Confidence

44. Confidence from CI / CD
Coverage Vulnerability Scanning
Code Linter Test Reporting

45. CONFIDENCE
We use Bitbucket
to develop code
with confidence.

46. Require passing
builds
Do not allow merges unless the
branch you are merging has had a
successful build.
Protect your
code
Build before
merging
No cowboy
coding
Review all code
Protect your
main branch

47. Review all changes
No matter how good you are, make
sure your team reviews your code.
Demos are extra credit (but we
require them).
Protect your
code
Build before
merging
No cowboy
coding
Review all code
Protect your
main branch

48. Remove approvals
when pull requests
are updated
Make sure no code is merged unless it
is reviewed.
Protect your
code
Build before
merging
No cowboy
coding
Review all code
Protect your
main branch

49. Disallow history
changes to master
Changes should only occur with a pull
request and reviews.
Protect your
code
Build before
merging
No cowboy
coding
Review all code
Protect your
main branch

53. CONFIDENCE
We use HipChat as
our team’s
communication
hub.

55. We use our main
team room
Integrations work better when
you are more likely to see the
messages they send.
HIPCHAT
More links lead to
more value
You can see an example of how
in five lines we can see an
entire issue resolved.

56. We use our main
team room
Integrations work better when
you are more likely to see the
messages they send.
HIPCHAT
More links lead to
more value
You can see an example of how
in five lines we can see an
entire issue resolved.

57. Link HipChat and
JIRA

58. Sentry
JavaScript error
reporting
StatusPage
Instant reporting of
service issues
PagerDuty
To notify of
incidents.
DataDog
For realtime
monitoring.
Confidence after GA

59. Conclusion
Transparency
Automation
Confidence

60. Code Without Obstacles

62. Thank you!
DAVID CRUZ | SENIOR SOFTWARE DEVELOPER | ATLASSIAN | @CRUZERLD