Keeping the JIRA team on trackFive techniques we use to boost both speed and quality

2

Paul Slade

JIRA Dev Manager, Atlassian

3

Team Evolution

4

#1 Paper Prototyping

5

#1 Paper Prototyping

6

#1 Paper Prototyping

7

• Build UX skills across your team• Design fast. Design cheap.

8

#2 Tight Teams

Early 2009

Late 2010

9

#2 Tight Teams

Team Ignite & A-team

• Specialists and generalists

• Skills exchange

• Teams follow product themes

10

#2 Tight Teams

Dreamteam & Engine Room

• Teams follow product lifecycle

• Evolve features

• Big code base

11

#2 Tight Teams

• Autonomous

• Team Leads still code

• Fast

• Cohesive

• Self organising

12

• Don’t be centralized too long. It slows you down.

• Change teams around – not that often• Autonomous teams go faster

13

#3 Scaling QA

• About the business experience pre JIRA 4.0

• JIRA 4.0+ shifted to the user experience

• Bring in QA specialists and we had the perfect storm

Image by opensourceway

14

#3 Scaling QA

15

#3 Scaling QA

Developer On Test - DOTOnly 5 issues can be waiting for a Quality Review

16

• Quality matters to an awesome user experience.

• Quality is everyone’s responsibility

17

#4 DevSpeed

• CI debt

• Inner loop speed

• Grease and oil change

• Clean house

18

#4 DevSpeed

• Brings variety

• Blow off some steam

• Try out scrum master for an iteration

19

• Make it easy to capture devspeed hassles

• Let your teams run a de-frag over their processes and tools

20

#5 Ship 20% time

• Use their product and customer knowledge

• Devspeed keeping devs super effective

• Trained to make calls

• Called 20% time

• Sounds awesome

21

#5 Ship 20% time

• Not good enough

• 8-10% time

• Solo projects

• Ambitious?

• Stall at 80% done!

22

Ship 20% time

+ =

23

Wrap up

• Paper protoyping

• Tight teams

• Scale QA

• Dev speed

• 20% time is a team effort

“From paper to product… #summit11”

24

Thanks,Surely there is time for questions…

25