Building JIRA with JIRA

DAVE MEYER • JIRA PRODUCT MANAGER • @DMEYER

D I S C L A I M E R

Legal Mumbo JumboAll statements describing future releases and capabilities, estimated release dates, and content are plans only, and Atlassian is under no obligation to develop, include or make available, commercially or otherwise, any specific feature or functionality in any Atlassian product. Information is provided for general understanding and informational purposes only, and is subject to change at the sole discretion of Atlassian in response to changing customer requirements, market conditions, delivery schedules and other factors. Information should not be distributed in any manner without written permission from Atlassian.

P M D E S I G N

Q AP R O J E C T M A N A G E R

M A R K E T I N GT H E B O S S

O P S

The team?

Embrace the chaos

team

D E VP M D E S I G N

Q AP R O J E C T M A N A G E R

M A R K E T I N GT H E B O S SO P S

The

The basics

The basics

Teams own their process

Branching Per Issue

Photo: http://www22.imagesandwallpapers.com/

Issues Code

Issues Code

JIRA-456

JIRA-123JIRA-123

JIRA-456

Branch per issue

feature/JIRA-30

stable master branch

isolated feature work

master

D E V

P M

The teamMore features faster please?

Communication comes first

D E S I G N

What about me?!?

Since our designers are embedded in the dev teams, it’s tough to track our design tasks. We use one board for the whole team so we can keep an eye on each other. It keeps the quality bar high.

L I A M G R E I G , J I R A D E S I G N L E A D

”

“

D E VP M

The teamLet’s triage some bugs!

Q A

Developers own quality

Kickoffs prevent bugs before they've been written. It gets QA into the development process and remind devs of known complications, edge cases, and most importantly, risks from other interacting teams or products. Most bugs are caused by not thinking about a particular scenario ahead of time, so in a kickoff we can discuss a story's requirements and risks more deeply. In addition, we give developer's some interesting scenarios to test on their own.

P E T E R O B A R A , J I R A Q A T E A M L E A D

”

“

Continuous Integration

Photo: William Warby

Building master & develop

JIRA-234

master

Building master & develop

JIRA-234

master

always build master

automatically triggered

Keep the f*cking builds green

O P SD E V

P M

The teamLet’s ship this thing!

Q A

Individuals and interactions over processes and tools.T H E A G I L E M A N I F E S T O

”“

Teams own the processBest practices come from culture

PMs communicate at all costsKeep the f*cking builds green

Releases are for everyone

Embrace the chaos

Danke

DAVE MEYER • JIRA PRODUCT MANAGER • @DMEYER

go.atlassian.com/howjirabuildsjira