The Secret Sauce of Successful Teams

164,699 views

Published on

Every software team writes code, but some teams produce fewer bugs than others. Every software team creates new features, but some teams develop them faster than others. What do high performance teams do differently, and why are team members more focused, satisfied and relaxed? They truly work together. No 10x rockstar programmer can achieve what a well rounded, enthusiastic team can.
Sven examines how the best software teams set and follow goals, integrate new members fast, ensure diversity, monitor and continually improve team health, embrace transparency, use a playbook to guide them through every phase of development and much more. He shares techniques including: bugfix rotations, OKRs, feature buddies, open demos, focus days and many more that help teams and team members to work more effectively together, and produce awesome results.

Published in: Leadership & Management
13 Comments
1,634 Likes
Statistics
Notes
  • nice (y)
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • @Charles Akkerman, CD I agree that there is no real secret, it's a combination of a lot of things. I disagree that you can't lay the foundation for teams to be successful because it's tied to the product / project. Giving teams the autonomy to adapt, a clear direction, support from the rest of the organization and forming a team with greta people of different skills and backgrounds is key. Let them act in a psychologically safe place and you got a successful team. Now if the product is doomed to fail the team will point that out and tell the management. If the company don't react we're missing the point on getting support from the rest of the organization.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • really i like it
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Said like a true jr Director or sr manager who wants to mold the thinking of those beneath. Teams require components, each task is different and the sauce, well there is no secret, it is unknown as we never know how people will work together and there are too many variables. What is the product expected, maybe it is doomed to fail in which case we blame the team even though they did the best work. Thanks for the post but its most basics to what a manager wants not the real sauce. Thank you
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Thank you
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
164,699
On SlideShare
0
From Embeds
0
Number of Embeds
9,874
Actions
Shares
0
Downloads
2,263
Comments
13
Likes
1,634
Embeds 0
No embeds

No notes for slide

The Secret Sauce of Successful Teams

  1. THE SECRETSAUCE OF SOFTWARETEAMS 100% AWESOME TEAMS @svenpet SUCCESSFUL
  2. SUCCESSFUL PEOPLE
  3. Fast
  4. Best Ideas Fast
  5. Problem Solver Fast Best Ideas
  6. Elegant Fast Best Ideas Problem Solver
  7. Technologies Fast Best Ideas Problem Solver Elegant
  8. Fast Rock Star Best Ideas Problem Solver Elegant Technologies
  9. Fast The 10x Programmer Best Ideas Problem Solver Elegant Technologies
  10. DOES THATATTRACT ?
  11. DOES THATATTRACT ?
  12. A PLACETHATEMPOWERS HIGH PERFORMANCETEAMS
  13. SVEN PETERS KICK-ASS DEVELOPER MOTIVATOR ATLASSIAN @svenpet
  14. WHAT MAKES THE DIFFERENCE?
  15. TEAM A TEAM B WHAT MAKES A TEAM HIGH PERFORMANCE?
  16. TEAM A TEAM B ? !! WHAT MAKES A TEAM HIGH PERFORMANCE?
  17. *%? TEAM A TEAM B ? !! !%! !%* $? ? !*# WHAT MAKES A TEAM HIGH PERFORMANCE?
  18. SPEAK LISTEN WHAT MAKES A TEAM HIGH PERFORMANCE?
  19. PSYCHOLOGICAL SAFTY
  20. PSYCHOLOGICAL SAFTY STRUCTURE
  21. PSYCHOLOGICAL SAFTY STRUCTURE MINDSET
  22. PSYCHOLOGICAL SAFTY STRUCTURE MINDSET SUPPORT
  23. PSYCHOLOGICAL SAFTY STRUCTURE MINDSET SUPPORT DIRECTION
  24. STRONG STRUCTURE SHARED MINDSET SUPPORTIVE CONTEXT COMPELLING DIRECTION
  25. COMPELLING DIRECTIONHOW TO GIVE GREATTEAMS GUIDANCE
  26. INCREASE REVENUE LOWER COSTS LESS DOWNTIME PROJECTX HAS TO BE FINISHED REFACTOR TO MICROSERVICES AUTOMATIC DEPLOYMENTS PROJECTYIS THE MOSTIMPORTANTONE
  27. NORTH STAR
  28. VISION 2 YEAR PLAN
  29. VISION 2 YEAR PLAN WHAT’S IMPORTANT? THEMES
  30. VISION 2 YEAR PLAN WHAT’S IMPORTANT? THEMES FOCUS AREAS HOW DO WE GETTHERE?
  31. VISION 2 YEAR PLAN WHAT’S IMPORTANT? THEMES FOCUS AREAS MEASURE HOW SUCESS LOOKS LIKE HOW DO WE GETTHERE?
  32. VISION THEMES FOCUS MEASURE VT…WHAT?
  33. FEATURES QUALITY VS
  34. THATSOUNDS VERYFLUFFY SHOW US THE REALWORLD
  35. OKR OBJECTIVE KEYRESULTS
  36. OBJECTIVE KEYRESULT BUILD MOBILE APP 1000 DAILY USER SCORE 700 DAILYUSER 0.7
  37. STRETCH QUARTERLY LESS IS MORE OKR
  38. MAKE GOALS TRANSPARENT FOR EVERYONE
  39. THINGS MAYLOOK GOOD ON PAPER…
  40. CREATIVITYINC.
  41. PRODUCT BRAIN TRUST EXPERIENCE FRESHALIGN FEATURING LEADERS AND OUR FOUNDERS
  42. PRODUCT BRAIN TRUST FEATURING LEADERS AND OUR FOUNDERS JUSTDIRECTION - YOU OWN THE DECISIONS
  43. VS YOUR IDEAS THE REALWORLD
  44. DON’T#%@& THE CUSTOMER
  45. 1 2 3 4 5 6 7 8 9 100 DETRACTORS PASSIVES PROMOTERS % Promoters - % Detractors Net PromoterScore (NPS) NPS
  46. LISTEN TO CUSTOMER FEEDBACK NPS FEEDBACK SUPPORT SOCIALMEDIA INTERVIEWS
  47. NPS FEEDBACK RELIABILITY USABILITY FUNCTIONALITY R U F
  48. 40,000PIECES OF FEEDBACK
  49. Usability- 63% Reliability- 31% Functionality- 6% RUF’ING IT! Bugs - 3% Editing - 6% Performance - 28% Navigation - 9% Complexity- 22% Content- 32%
  50. TELLEVERYONE WHAT BUGS THE CUSTOMER
  51. WEEKLYEMAIL ARE WE IMPROVING? TO EVERYATLASSIAN
  52. WEEKLYEMAIL TO EVERYATLASSIAN EACH ATLASSIAN GETS DIFFERENT FEEDBACK
  53. COMPELLING DIRECTION GIVE YOUR TEAM A NORTH STAR FOLLOW GOALS SANITYCHECKS UNDERSTAND FEEDBACK
  54. STRONG STRUCTUREHOW TO ASSEMBLE A GREATTEAM
  55. DESIGN PROGRAMMING TESTING PRODUCT OPERATIONS
  56. TONE DIRECTOR CAMERA ACTORS LIGHT
  57. CROSS FUNCTIONALTEAMS
  58. CROSS FUNCTIONALTEAMS
  59. CROSS FUNCTIONALTEAMS
  60. CROSS FUNCTIONALTEAMS INFORMATION FLOWS FASTER DECISIONS DIVERSITYOF THOUGHT UNDERSTANDING
  61. CROSS FUNCTIONALTEAMS
  62. CROSS FUNCTIONALTEAMS
  63. CROSS CULTURALTEAMS
  64. DIFFERENTBACKGROUNDS DIVERSITYOF THOUGHT CREATIVE /STRONGER SOLUTIONS
  65. MAKE YOUR TEAM A SAFE PLACE SPEAK LISTEN RESPECT
  66. f%$*ed
  67. RITUALS AND REFRESHMENTS
  68. FIKA
  69. CONFERNCEVIDEOFRIDAYS
  70. GSD*DAYS *GETTINGSH%TDONE
  71. INNOVATIONWEEK
  72. A TEAM IS MADE OUTOF INDIVIDUALS HIGH FIVE
  73. SAY“GREATJOB” GIVE KUDOS
  74. SAY“GREATJOB” GIVE KUDOS
  75. OFFICECLAPPING
  76. GRAD/JNR DEVELOPER DEVELOPER SENIOR DEVELOPER DEVELOPER MANAGER DEVELOPER TEAM LEAD HEAD OF DEVELOPER - GROUP HEAD OF DEVELOPMENT PEOPLE LEADERSHIP
  77. GRAD/JNR DEVELOPER DEVELOPER SENIOR DEVELOPER DEVELOPER MANAGER DEVELOPER TEAM LEAD HEAD OF DEVELOPER - GROUP HEAD OF DEVELOPMENT PEOPLE LEADERSHIP LEAD DEVELOPER TECHNICALLEAD
  78. SUPPORTIVE CONTEXTHOW TO HELP GREATTEAMS TO GETSH*TDONE
  79. DECISIONS
  80. DECISIONS INFORMATION
  81. DECISIONS INFORMATION 1:1s
  82. DECISIONS INFORMATION 1:1sEMAILS
  83. DECISIONS INFORMATION 1:1sEMAILS DOCUMENTS
  84. DECISIONS INFORMATION 1:1sEMAILS DOCUMENTS MEETINGS
  85. DECISIONS INFORMATION 1:1sEMAILS DOCUMENTS MEETINGS RANDOM DISCUSSION
  86. DECISIONS INFORMATION 1:1sEMAILS DOCUMENTS MEETINGS RANDOM DISCUSSION WORD OF MOUTH
  87. DECISIONS INFORMATION 1:1sEMAILS DOCUMENTS MEETINGS RANDOM DISCUSSION WORD OF MOUTH EXCELSHEETS
  88. DECISIONS INFORMATION 1:1sEMAILS DOCUMENTS MEETINGS RANDOM DISCUSSION WORD OF MOUTH EXCELSHEETS INTRANET
  89. INTRANET
  90. YOUR TEAM SPACE COMPANYINFORMATION PERSONALPAGES
  91. OTHER TEAM GOALS DECISIONS OTHER PROJECTS STRATEGIES
  92. OPEN BYDEFAULT
  93. WRITE DOWN YOUR DECISIONS
  94. PROVIDE DATA AND CONTEXT
  95. ANSWER QUESTIONS
  96. ALLOW CORRECTIONS
  97. OR ITDIDN’THAPPEN SHAREIT
  98. OR ITDIDN’THAPPEN EAC IT
  99. OPEN COMPANY, NO BULLSHIT
  100. Passionate discussion
  101. STOP ENDLESS DISCUSSIONS TAKE IT OFFLINE
  102. PLAY, AS A TEAM
  103. INFORMATION EASYACCESS HELP
  104. WANTTO OPEN SOURCE?
  105. SSH ACCESS?
  106. NEED A BIKE? WHILE YOU’RE IN AMSTERDAM
  107. MAKE SERVICE DISCOVERABLE
  108. WAITING FOR OTHERS?
  109. DO ITYOURSELF
  110. LEGALCONTRACT REVIEW? DO ITYOURSELF
  111. NEED DESIGN TO CHANGETHE UI? DO ITYOURSELF
  112. design.atlassian.com
  113. NEED QA FOR TESTING YOUR SOFTWARE? DO ITYOURSELF
  114. TESTAUTOMATION DEVELOPER
  115. TESTAUTOMATION MANUALTESTING DEVELOPER QA ENGINEER FAIL FIX
  116. TESTAUTOMATION MANUALTESTING DEVELOPER QA ENGINEER FAIL TELL FIX
  117. FAIL
  118. DEVELOPER CODE TEST +
  119. QA KICK OFF DEVELOPER DEVELOPER + QA CODE TEST +
  120. QA KICK OFF DEMO DEVELOPER DEVELOPER + QA DEVELOPER + QA CODE TEST +
  121. NEED A USER TESTFOR YOUR NEW FEATURE? DO ITYOURSELF
  122. BUILD A PROTOTYPE RENTTHETESTLAB
  123. MICROPHONE COMPUTER CAMERA USER VIDEO & LIVESTREAM
  124. DO ITYOURSELFASKING F R HELP MAKE EASY
  125. HOW DO YOU KNOW ALLTHIS STUFF? LONG TERM EMPLOYEE 25YEARS
  126. GIVE NEW EMPLOYEES A BOOST
  127. FIRST WEEKS BOOTCAMPLOADING…. LESSONS BY EMPLOYEES
  128. NEW WORKPLACE NEW TEAM MEMBERS NEW ACRONYMS NEW WORK STYLE NEW PROCESSES + SHOWING YOU’RE GOOD
  129. SETCLEAR EXPECTATIONS FOR NEW TEAM MEMBERS 90 DAYPLAN
  130. PAIR PROGRAMMING / CODE REVIEWS
  131. FRIDAYFAMILY BREAKFAST MOST EMBARRASSING STORY SECRETTATTOO A HIDDEN TALENT
  132. SHARED MINDSETHOW TO GETTHETEAM THINKING IN THE SAME DIRECTION
  133. BUILDING TEAM KNOWLEDGE BUG FIX
  134. BUILDING TEAM KNOWLEDGE BUG FIX
  135. BUILDING TEAM KNOWLEDGE BUG FIX
  136. BUILDING TEAM KNOWLEDGE BUG FIX ROTATION
  137. BUILDING TEAM KNOWLEDGE FEATURE X FEATURE Y
  138. DEVELOPING FEATURES IS A PROCESS LOTS OF SMALLDECISIONS GETA BUDDY
  139. BUILDING TEAM KNOWLEDGE FEATURE X FEATURE Y BUDDY BUDDY
  140. BUILDING TEAM KNOWLEDGE FEATURE BUDDY
  141. CANARYSESSIONS TESTING IDEAS WITH THE TEAM
  142. AGILE SLAM LIKE A BROWN BAG, BUTON TEAM PROCESS
  143. BUILDING TEAM KNOWLEDGE TEAM DISCUSSIONS
  144. SHARE DESIGN IDEAS
  145. …AND COLLECTFEEDBACK
  146. DOING THINGS RIGHT BUILD PROCESSES
  147. DOING THE RIGHTTHINGS BUILD ADAPTABILITY ? !
  148. TEAM YOUR WAY
  149. BUILD IMPROVE ENVISION SOME GUIDANCE TEAM YOUR WAY
  150. THE PLAYBOOK ENVISION IT MAKEIT IMPROVEIT 40+ PLAYS TO GUIDE PROJECTTEAMS
  151. OVERVIEW
  152. CONCEPTTESTINGENVISION IT PAPER PROTOTYPE USER STICKER
  153. CONCEPTTESTING
  154. PROJECTPOSTERMAKE IT SHARED UNDERSTANDING
  155. THE PLAYS
  156. THE PLAYS THE PLAYBOOK ENVISION IT MAKEIT IMPROVEIT 40+ PLAYS TO GUIDE PROJECTTEAMS
  157. SHARED MINDSET SUPPORTIVE CONTEXT COMPELLING DIRECTION STRONG STRUCTURE
  158. HOW AWESOME IS YOUR TEAM?
  159. HOW AWESOME IS YOUR TEAM? CAN YOU MEASURE IT? HEALTHY
  160. 8 CHECK POINTS FOR BETTER TEAM HEALTH 1 FULLTIME OWNER BALANCED TEAM SHARED UNDERSTANDING VALUE AND METRICS END-TO-END DEMO README DEPENDENCIES VELOCITY
  161. Full-time owner Balanced team Shared Value and metrics End-to-end demo Readme Dependencies Velocity CHECKPOINTS 1 2 3 4 5 TRACKINGHEALTH…MEASURINGATCHECKPOINTS
  162. www.atlassian.com/healthmonitor HEALTH MONITOR IMPROVEYOURTEAM
  163. SO HEALTH SHOWS WHATNOW? IMPROVEYOURTEAM
  164. IMPROVEYOURTEAM THINK & ACTLIKE A FOUNDER EMPOWER TEAMS TO
  165. IMPROVEYOURTEAM BETHE CHANGE YOU SEEK
  166. IMPROVEYOURTEAM THE A-TEAM THE MINION TEAM THE MUPPET TEAM
  167. IMPROVEYOURTEAM THE A-TEAM THE MINION TEAM THE MUPPET TEAM DECIDE IN YOUR ENVIRONMENT
  168. SINGLE CORE = PHYSICALLIMITS
  169. MULTI CORE = COMMUNICATION REQUIRED
  170. TEAM UP! TO BE AWESOME
  171. TEAM UP! TO BE AWESOME THANKS @svenpet

×