Build Better Software Together
•
7 likes•13,257 views
Software development is a social challenge. We should design our workflows so that everybody knows what's going on: From coining an idea to running the software on servers in production. Let me share with you how we at Atlassian are working with a highly transparent workflow and how we have build that directly into our tools - to build software better together!
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Build Better Software Together
Similar to Build Better Software Together (20)
More from Sven Peters
More from Sven Peters (15)
Recently uploaded
Recently uploaded (20)
Build Better Software Together
- 3. Building software is a ... challenge WIN FAIL
- 4. Building software is a ... challenge WIN FAIL
- 5. Building software is a social challenge Every team must share... Code x3 Source code, review, continuous integration, DVCS management x6 Tasks Issue and project tracking // Get the product id stored in the optionValue of the widget $productId = $order['customIdNumber' ]; // Load the product $product = Mage::g Ideas Team collaboration Group chat
- 7. separate teams: hardware and software Error No SIM card or phone is! turned off! (0xff05) Confirm
- 8. Software Development Flow Connecting Tasks Ideas Tasks Code Builds
- 9. Software Development Flow Connecting Teams Ideas Product Owner Product Manager Tasks Code Developer Builds Operations
- 10. Software Development Flow Connecting People Ideas Product Owner Product Manager Tasks Code Developer Builds Operations
- 11. Software Development Flow Connecting Locations Code Ideas Tasks Ideas Code Tasks Builds Developer Code
- 12. Transparent Flow
- 14. The idea
- 15. 62 involve everybody Original Post One Day Later One Week Later
- 16. Planning Flow REQUI REMENTS STOR IES SPRIN TS
- 27. Best practices with Blueprints Quickly create & link content Traceability
- 31. Best practices with Blueprints Quickly create & link content Traceability
- 32. Planning Flow REQUI REMENTS STOR IES SPRIN TS
- 33. Development Flow + BRANC H, CODE & TEST PULL R EQUESTS
- 34. Development Flow
- 35. Branching
- 36. Branching
- 37. Branching From JIRA Issue to Branch to Code in 30 seconds
- 38. Caption
- 50. Free Git client for Windows or Mac
- 51. Branching Code Isolation Best Practices Quick & Simple
- 52. Branching
- 55. Code Reviews are more important than TDD
- 56. Better Quality Feel Better Code Reviews Learn
- 57. Pull Requests review stories & builds
- 58. Free Git client for Windows or Mac
- 70. Pull Requests Code Review Quality Check Control
- 72. Development Flow
- 73. DONE !
- 75. How could that happen?
- 77. What happened
- 78. Branch Detection Don’t let that happen detect branch (& run automatically)
- 79. Branch Detection Don’t let that happen detect branch (& run automatically)
- 80. Who broke the built?
- 81. What Who broke the built?
- 82. Look at the logs Found failing test Look at the code Can not find the problem Look at the changes Nothing changed Look at the change set Problem found! Why did it change? Go to the author
- 83. Look at the build server Look at the change set Found failing Issue Problem found!
- 84. See the cause
- 85. Find the problem
- 86. You can not find the problem? rerun!
- 88. What does it tell you? failing test = useless
- 89. Put flaky tests under quarantine
- 93. Transparent Flow
- 94. connecting teams connecting people Transparent connecting locations Flow connecting taks
- 95. WHY?
- 96. Tearing down silos is a... challenge