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
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.
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
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
20.
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.
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
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
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.