1.
About me
• Anatoli Kazatchkov
akazatchkov@atlassian.com
Confluence dev manager
• Software developer for 11 years
• Shipped 13 major, 50+ minor releases
of Confluence since 2007
• … but still learning how to write and
ship better software!

2.
Atlassian

3.
Sexier than Google?

4.
JIRA
Issue tracking, workflow and project management.

5.
JIRA: when do you use it?
• When you have too many bugs to keep in
your head
• When you are working with more than
two or three people
• When you want to let other people report
issues with your software

6.
Confluence
World’s most widely-used enterprise wiki.

7.
Confluence:
when do you use it?
when do you use it?
• When you have too many detailed ideas to
keep in your head
• When you are working with more than
two or three people
• When you want to share your ideas with
other people

8.
Bamboo
Software telemetry & build server.

9.
Bamboo:
when do you use it?
when do you use it?
• When your software is too big to test
manually every time you change something
… you write automated tests.
• When you need someone to know when
they’ve broken something ASAP
… you set up Bamboo.

10.
FishEye & Crucible
Collaborative, peer code review.
Source insight & analysis.
Code coverage and test improvement.

11.
FishEye & Crucible:
when do you use them?
when do you use them?
• When you want to see the history of your
project
• When you want changes to the software
reviewed by multiple people

12.
Atlassian Stash
Distributed version control, pull requests.

13.
Atlassian OnDemand
Hosted all-in-one development suite.

14.
Recent additions
• Bitbucket – hosted source repository
• Team Calendars – add-on for Confluence
• Bonfire – testing add-on for JIRA

15.
Growth

16.
Development Roles
•Graduate
Learns to write the code
•Developer
Writes the code
•Architect
Designs the code structure

17.
Problem Roles
•QA Engineer
Prevents customer problems
•Performance Engineer
Solves performance problems
•Support Engineer
Solves customer problems

18.
Customer Roles
•Product Manager
Divines customer needs
•Technical Writer
Documents the solution
•Marketing Specialist
Demos how needs are met

19.
“Real artists ship”

20.
How do you get (working)
software out the door?

21.
Track your issues
• All software has bugs, feature ideas
• Keep a list: in your head, on a piece of
paper, in a spreadsheet, in a system

22.
Use version control
• Many teams still operate without proper
version control system
• No excuses
• Free or commercial, hosted or self-service

23.
Write automated tests
• Software can test itself
• Developers write tests
• that live with the code
• Open source: JUnit,
• JWebUnit, Selenium

24.
Run the tests often
• Nightly builds:
cron & shell scripts
• Email developers
when they fail
• More configurations:
use a build server
• Free or commercial

25.
Allow for mistakes
• Tests catch them
• Builds catch them
• Reviews catch them, too
• Use pair programming or
code reviews for
important changes

26.
Release often!
• Once it works, package it up for download
• Have a one-step process
• Use a build tool: Maven,Ant, Rake
• Go for release lunch (often)!

27.
What should I take home?
• Make sure you’re working
with the right tools –
most of them are free!
• Work should be fun

28.
akazatchov@atlassian.com
Questions