Continuous development - Growing Pains

1,109 views
965 views

Published on

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

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,109
On SlideShare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
15
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Continuous development - Growing Pains

  1. 1. Continuous development Growing painsSaturday, 29 September 12 1
  2. 2. Who am I ? Community developer Salesforce & Heroku kanban, java, scala, clojure communities @jr0cket blog.jr0cket.co.ukSaturday, 29 September 12 2
  3. 3. Atlassian: In the beginning...Saturday, 29 September 12 3
  4. 4. Success happens ! Software for software developersSaturday, 29 September 12 4
  5. 5. Really big shedSaturday, 29 September 12 5
  6. 6. How does that happen without pain ?Saturday, 29 September 12 6
  7. 7. So the story begins... startup culture open, no bull... practices evolved as necessary business growing everyone is happySaturday, 29 September 12 7
  8. 8. Atlassian valuesSaturday, 29 September 12 8
  9. 9. Maintaining the culture during growthSaturday, 29 September 12 9
  10. 10. Many companies fail Control over complexity Fear of innovation Restrictive management controlsSaturday, 29 September 12 10
  11. 11. MafiaSaturday, 29 September 12 11
  12. 12. Atlassian stay “agile” Trust in their people Encouraging collaboration Promoting innovationSaturday, 29 September 12 12
  13. 13. Agree on Cadence 97 Days release cycleSaturday, 29 September 12 13
  14. 14. Innovation encouragement 20% time Fedex Days ShipIt DaysSaturday, 29 September 12 14
  15. 15. Big Strategic DecisionSaturday, 29 September 12 15
  16. 16. Converging on the cloud Make products more accessible Products have to be more integrated Unified product experience Enterprise customer supportSaturday, 29 September 12 16
  17. 17. Culture influenced from the top Ship on-demand & product at same time Same short release cycle across the board left up to teams on how to achieve itSaturday, 29 September 12 17
  18. 18. ChallengesSaturday, 29 September 12 18
  19. 19. Team Culture(s) Each team evolved its own way JIRA team formed 2002 Confluence team formed 2003 Team practices formed by its membersSaturday, 29 September 12 19
  20. 20. Fighting Conway’s Law 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 Culture shapes code diverse teams a range of practices evolving different toolsSaturday, 29 September 12 20
  21. 21. Adapt without loosing Culture Make your culture visible define what you stand forSaturday, 29 September 12 21
  22. 22. Atlassian valuesSaturday, 29 September 12 22
  23. 23. Culture needs to adaptSaturday, 29 September 12 23
  24. 24. Toward continuous deployment Focus on smaller features breaking down stories no more epics clearer understanding of what is valuable - by delivering it!Saturday, 29 September 12 24
  25. 25. Developer cycle changes Shorter dev cycle to fit into production dev cycle more opportunities to consider whats valuable feeling the pain regularly encourages improvementSaturday, 29 September 12 25
  26. 26. Understanding Technical Debt Work on something... with the intent to clean it up later Ward CunninghamSaturday, 29 September 12 26
  27. 27. Technical Debt in practice Decisions get left behind Approaches get lost over time Unavoidable growth via software inertiaSaturday, 29 September 12 27
  28. 28. Increasing awareness Customer need over develop what’s cool feedback from customers developers engaged with those concerns avoid navel gazing & chasing shiny thingsSaturday, 29 September 12 28
  29. 29. Wider engagement Social media channels shaping image Customers more vocal about experience Competition grows Belief & Ambition growSaturday, 29 September 12 29
  30. 30. More extreme options Breaking up products too costly and painful?Saturday, 29 September 12 30
  31. 31. Missing elements A realistic roadmap customers what to know where something is going hard to give 100% guarantees on everything / anything a diverse audience to pleaseSaturday, 29 September 12 31
  32. 32. Solving it togetherSaturday, 29 September 12 32
  33. 33. Quality Assistance Helping raise the quality bar Asking “difficult” questions how does x work?Saturday, 29 September 12 33
  34. 34. Build team Developers love learning maven, right? Puppet is more fun than beer, surely!Saturday, 29 September 12 34
  35. 35. UX team Helping developers understand value of UX http://seb.ly/Saturday, 29 September 12 35
  36. 36. Kick-ass team Teams with in teams focusing on specific product challengesSaturday, 29 September 12 36
  37. 37. Collaboratively Iterating Empowering people to collaborate towards an understood goal that gives clear valueSaturday, 29 September 12 37
  38. 38. Leveraging the toolsSaturday, 29 September 12 38
  39. 39. Tools != process Tools can support change Encourage innovations Allow understanding valueSaturday, 29 September 12 39
  40. 40. Public bug tracker Ultimate form of “dogfood” Helps some of the audience understand company constraints & directionSaturday, 29 September 12 40
  41. 41. DVCS saves the day ! Not a panacea, but very liberating Developers allowed to experiment in a safe way Social codingSaturday, 29 September 12 41
  42. 42. Social Code reviews Not just for new code Identifying technical debt Looking for opportunities to improveSaturday, 29 September 12 42
  43. 43. BenefitsSaturday, 29 September 12 43
  44. 44. Atlassian as a platform Engage with developer environment Drive innovation on a wider scale Add value to developers as well as customersSaturday, 29 September 12 44
  45. 45. Customer engagement New features Dark features AB testing Give Feedback making it really easy to give valuable feedback based on what the customer was doing!!Saturday, 29 September 12 45
  46. 46. Refocus on user experience Building on areas of strength workflow Radical changes to areas of weakness user experience (UX)Saturday, 29 September 12 46
  47. 47. http://semanticstudios.comSaturday, 29 September 12 47
  48. 48. Constraints driving innovation 24 hrs to deliver something valuable no control over what no say in who or how just do it, evaluate the results Formally known as FedEx daysSaturday, 29 September 12 48
  49. 49. Engaging the wider communitySaturday, 29 September 12 49
  50. 50. Community is the greatest asset User & Developer communities give valuable, actionable feedback become an extended part of the organisation your evangelists to the worldSaturday, 29 September 12 50
  51. 51. Opening up Access to your platform Creating business driven market place Focusing on developer experience Helping customers succeedSaturday, 29 September 12 51
  52. 52. Value of platformSaturday, 29 September 12 52
  53. 53. Platform is the new framework Facebook - social marketing Heroku - universal managed platform Salesforce - Sales, Marketing, Social Media analysis, Enterprise development platformsSaturday, 29 September 12 53
  54. 54. In SummarySaturday, 29 September 12 54
  55. 55. Success, agility & culture Atlassian Salesforce & Heroku successful companies retaining their culture Why not in your organisation?Saturday, 29 September 12 55
  56. 56. Thank you jstevenson@salesforce.com @jr0cket blog.jr0cket.co.ukSaturday, 29 September 12 56

×