continuous development - growing pains

Post on 17-Oct-2014

1.174 Views

Category:

Documents

0 Downloads

Preview:

Click to see full reader

DESCRIPTION

This session focuses on the growing pains and successes of the software teams at Atlassian, when moving to continuous deployment and the opportunities they are creating towards continuous delivery. When a company takes a big strategic decision, the impact it has on its people is a mark of how well its leaders understand the principles behind the agile approach. The impact of this decision on the software development teams was to go from a 97 day iteration to a two week continuous deployment approach. Each team was given the responsibility on how they would achieve this and every team had different triumphs and frustrations Specialist teams were also introduced to build up to specifically transfer knowledge and disseminate useful practices (with context), from UX to build management and wider DevOps practices

TRANSCRIPT

Continuous developmentGrowing pains

1Saturday, 29 September 12

Who am I ?

Community developerSalesforce & Herokukanban, java, scala, clojure communities

@jr0cketblog.jr0cket.co.uk

2Saturday, 29 September 12

Atlassian: In the beginning...

3Saturday, 29 September 12

Success happens !

Software for software developers

4Saturday, 29 September 12

Really big shed

5Saturday, 29 September 12

How does that happen without pain ?

6Saturday, 29 September 12

So the story begins...

startup cultureopen, no bull...practices evolved as necessary business growingeveryone is happy

7Saturday, 29 September 12

Atlassian values

8Saturday, 29 September 12

Maintaining the culture during growth

9Saturday, 29 September 12

Many companies fail

Control over complexity

Restrictive management controls

Fear of innovation

10Saturday, 29 September 12

Mafia

11Saturday, 29 September 12

Atlassian stay “agile”

Trust in their peopleEncouraging collaboration Promoting innovation

12Saturday, 29 September 12

Agree on Cadence

97 Days release cycle

13Saturday, 29 September 12

Innovation encouragement

20% timeFedex Days ShipIt Days

14Saturday, 29 September 12

Big Strategic Decision

15Saturday, 29 September 12

Converging on the cloud

Make products more accessibleProducts have to be more integratedUnified product experienceEnterprise customer support

16Saturday, 29 September 12

Culture influenced from the top

Ship on-demand & product at same timeSame short release cycle across the board

left up to teams on how to achieve it

17Saturday, 29 September 12

Challenges

18Saturday, 29 September 12

Team Culture(s)

Each team evolved its own wayJIRA team formed 2002Confluence team formed 2003

Team practices formed by its members

19Saturday, 29 September 12

Fighting Conway’s Law

Culture shapes codediverse teamsa range of practicesevolving different tools

organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations http://en.wikipedia.org/wiki/Conway%27s_law

20Saturday, 29 September 12

Adapt without loosing Culture

Make your culture visibledefine what you stand for

21Saturday, 29 September 12

Atlassian values

22Saturday, 29 September 12

Culture needs to adapt

23Saturday, 29 September 12

Toward continuous deployment

Focus on smaller featuresbreaking down storiesno more epicsclearer understanding of what is valuable - by delivering it!

24Saturday, 29 September 12

Developer cycle changes

Shorter dev cycleto fit into production dev cyclemore opportunities to consider whats valuablefeeling the pain regularly encourages improvement

25Saturday, 29 September 12

Understanding Technical Debt

Work on something... with the intent to clean it up later

Ward Cunningham

26Saturday, 29 September 12

Technical Debt in practice

Decisions get left behindApproaches get lost over timeUnavoidable growth via software inertia

27Saturday, 29 September 12

Increasing awareness

Customer need over develop what’s coolfeedback from customersdevelopers engaged with those concernsavoid navel gazing & chasing shiny things

28Saturday, 29 September 12

Wider engagement

Social media channels shaping imageCustomers more vocal about experienceCompetition growsBelief & Ambition grow

29Saturday, 29 September 12

More extreme options

Breaking up productstoo costly and painful?

30Saturday, 29 September 12

Missing elements

A realistic roadmapcustomers what to know where something is goinghard to give 100% guarantees on everything / anythinga diverse audience to please

31Saturday, 29 September 12

Solving it together

32Saturday, 29 September 12

Quality Assistance

Helping raise the quality barAsking “difficult” questions

how does x work?

33Saturday, 29 September 12

Build team

Developers love learning maven, right?Puppet is more fun than beer, surely!

34Saturday, 29 September 12

UX team

Helping developers understand value of UX

http://seb.ly/

35Saturday, 29 September 12

Kick-ass team

Teams with in teamsfocusing on specific product challenges

36Saturday, 29 September 12

Collaboratively Iterating

Empowering people to collaborate towards an understood goal that gives clear value

37Saturday, 29 September 12

Leveraging the tools

38Saturday, 29 September 12

Tools != process

Tools can support changeEncourage innovationsAllow understanding value

39Saturday, 29 September 12

Public bug tracker

Ultimate form of “dogfood” Helps some of the audience understand company constraints & direction

40Saturday, 29 September 12

DVCS saves the day !

Not a panacea, but very liberatingDevelopers allowed to experiment in a safe way

Social coding

41Saturday, 29 September 12

Social Code reviews

Not just for new codeIdentifying technical debtLooking for opportunities to improve

42Saturday, 29 September 12

Benefits

43Saturday, 29 September 12

Atlassian as a platform

Engage with developer environmentDrive innovation on a wider scaleAdd value to developers as well as customers

44Saturday, 29 September 12

Customer engagement

New features Dark featuresAB testingGive Feedback

making it really easy to give valuable feedback based on what the customer was doing!!

45Saturday, 29 September 12

Refocus on user experience

Building on areas of strengthworkflow

Radical changes to areas of weaknessuser experience (UX)

46Saturday, 29 September 12

http://semanticstudios.com

47Saturday, 29 September 12

Constraints driving innovation

24 hrs to deliver something valuableno control over whatno say in who or howjust do it, evaluate the results

Formally known as FedEx days

48Saturday, 29 September 12

Engaging the wider community

49Saturday, 29 September 12

Community is the greatest asset

User & Developer communities

give valuable, actionable feedbackbecome an extended part of the organisationyour evangelists to the world

50Saturday, 29 September 12

Opening up

Access to your platformCreating business driven market placeFocusing on developer experienceHelping customers succeed

51Saturday, 29 September 12

Value of platform

52Saturday, 29 September 12

Platform is the new framework

Facebook - social marketingHeroku - universal managed platformSalesforce - Sales, Marketing, Social Media analysis, Enterprise development platforms

53Saturday, 29 September 12

In Summary

54Saturday, 29 September 12

Success, agility & culture

AtlassianSalesforce & Heroku

successful companiesretaining their culture

Why not in your organisation?

55Saturday, 29 September 12

Thank youjstevenson@salesforce.com

@jr0cketblog.jr0cket.co.uk

56Saturday, 29 September 12

top related