The Secret Sauce of Successful Teams
•1,690 j'aime•307,570 vues
Signaler
Partager
Télécharger pour lire hors ligne
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.
Contenu connexe
Tendances
Tendances(20)
Similaire à The Secret Sauce of Successful Teams
Similaire à The Secret Sauce of Successful Teams(20)
Plus de Sven Peters
Plus de Sven Peters(20)
Dernier
Dernier(10)
The Secret Sauce of Successful Teams
- 4. Fast
- 6. Problem Solver Fast Best Ideas
- 7. Elegant Fast Best Ideas Problem Solver
- 8. Technologies Fast Best Ideas Problem Solver Elegant
- 9. Fast Rock Star Best Ideas Problem Solver Elegant Technologies
- 10. Fast The 10x Programmer Best Ideas Problem Solver Elegant Technologies
- 21. SVEN PETERS KICK-ASS DEVELOPER MOTIVATOR ATLASSIAN @svenpet
- 22. WHAT MAKES THE DIFFERENCE?
- 23. TEAM A TEAM B WHAT MAKES A TEAM HIGH PERFORMANCE?
- 24. TEAM A TEAM B ? !! WHAT MAKES A TEAM HIGH PERFORMANCE?
- 25. *%? TEAM A TEAM B ? !! !%! !%* $? ? !*# WHAT MAKES A TEAM HIGH PERFORMANCE?
- 26. SPEAK LISTEN WHAT MAKES A TEAM HIGH PERFORMANCE?
- 33. STRONG STRUCTURE SHARED MINDSET SUPPORTIVE CONTEXT COMPELLING DIRECTION
- 34. COMPELLING DIRECTIONHOW TO GIVE GREATTEAMS GUIDANCE
- 37. INCREASE REVENUE LOWER COSTS LESS DOWNTIME PROJECTX HAS TO BE FINISHED REFACTOR TO MICROSERVICES AUTOMATIC DEPLOYMENTS PROJECTYIS THE MOSTIMPORTANTONE
- 38. NORTH STAR
- 40. VISION 2 YEAR PLAN WHAT’S IMPORTANT? THEMES
- 41. VISION 2 YEAR PLAN WHAT’S IMPORTANT? THEMES FOCUS AREAS HOW DO WE GETTHERE?
- 42. VISION 2 YEAR PLAN WHAT’S IMPORTANT? THEMES FOCUS AREAS MEASURE HOW SUCESS LOOKS LIKE HOW DO WE GETTHERE?
- 46. THATSOUNDS VERYFLUFFY SHOW US THE REALWORLD
- 48. OBJECTIVE KEYRESULT BUILD MOBILE APP 1000 DAILY USER SCORE 700 DAILYUSER 0.7
- 49. STRETCH QUARTERLY LESS IS MORE OKR
- 51. THINGS MAYLOOK GOOD ON PAPER…
- 52. CREATIVITYINC.
- 53. PRODUCT BRAIN TRUST EXPERIENCE FRESHALIGN FEATURING LEADERS AND OUR FOUNDERS
- 54. PRODUCT BRAIN TRUST FEATURING LEADERS AND OUR FOUNDERS JUSTDIRECTION - YOU OWN THE DECISIONS
- 55. VS YOUR IDEAS THE REALWORLD
- 57. 1 2 3 4 5 6 7 8 9 100 DETRACTORS PASSIVES PROMOTERS % Promoters - % Detractors Net PromoterScore (NPS) NPS
- 58. LISTEN TO CUSTOMER FEEDBACK NPS FEEDBACK SUPPORT SOCIALMEDIA INTERVIEWS
- 59. NPS FEEDBACK RELIABILITY USABILITY FUNCTIONALITY R U F
- 61. Usability- 63% Reliability- 31% Functionality- 6% RUF’ING IT! Bugs - 3% Editing - 6% Performance - 28% Navigation - 9% Complexity- 22% Content- 32%
- 62. TELLEVERYONE WHAT BUGS THE CUSTOMER
- 63. WEEKLYEMAIL ARE WE IMPROVING? TO EVERYATLASSIAN
- 64. WEEKLYEMAIL TO EVERYATLASSIAN EACH ATLASSIAN GETS DIFFERENT FEEDBACK
- 65. COMPELLING DIRECTION GIVE YOUR TEAM A NORTH STAR FOLLOW GOALS SANITYCHECKS UNDERSTAND FEEDBACK
- 66. STRONG STRUCTUREHOW TO ASSEMBLE A GREATTEAM
- 72. CROSS FUNCTIONALTEAMS INFORMATION FLOWS FASTER DECISIONS DIVERSITYOF THOUGHT UNDERSTANDING
- 77. MAKE YOUR TEAM A SAFE PLACE SPEAK LISTEN RESPECT
- 78. f%$*ed
- 80. FIKA
- 83. INNOVATIONWEEK
- 84. A TEAM IS MADE OUTOF INDIVIDUALS HIGH FIVE
- 87. OFFICECLAPPING
- 88. GRAD/JNR DEVELOPER DEVELOPER SENIOR DEVELOPER DEVELOPER MANAGER DEVELOPER TEAM LEAD HEAD OF DEVELOPER - GROUP HEAD OF DEVELOPMENT PEOPLE LEADERSHIP
- 89. GRAD/JNR DEVELOPER DEVELOPER SENIOR DEVELOPER DEVELOPER MANAGER DEVELOPER TEAM LEAD HEAD OF DEVELOPER - GROUP HEAD OF DEVELOPMENT PEOPLE LEADERSHIP LEAD DEVELOPER TECHNICALLEAD
- 90. SUPPORTIVE CONTEXTHOW TO HELP GREATTEAMS TO GETSH*TDONE
- 91. DECISIONS
- 101. INTRANET
- 103. OTHER TEAM GOALS DECISIONS OTHER PROJECTS STRATEGIES
- 104. OPEN BYDEFAULT
- 107. ANSWER QUESTIONS
- 108. ALLOW CORRECTIONS
- 112. OPEN COMPANY, NO BULLSHIT
- 115. STOP ENDLESS DISCUSSIONS TAKE IT OFFLINE
- 116. PLAY, AS A TEAM
- 118. WANTTO OPEN SOURCE?
- 119. SSH ACCESS?
- 120. NEED A BIKE? WHILE YOU’RE IN AMSTERDAM
- 122. WAITING FOR OTHERS?
- 123. DO ITYOURSELF
- 128. NEED DESIGN TO CHANGETHE UI? DO ITYOURSELF
- 129. design.atlassian.com
- 132. NEED QA FOR TESTING YOUR SOFTWARE? DO ITYOURSELF
- 134. TESTAUTOMATION MANUALTESTING DEVELOPER QA ENGINEER FAIL FIX
- 135. TESTAUTOMATION MANUALTESTING DEVELOPER QA ENGINEER FAIL TELL FIX
- 136. FAIL
- 138. QA KICK OFF DEVELOPER DEVELOPER + QA CODE TEST +
- 139. QA KICK OFF DEMO DEVELOPER DEVELOPER + QA DEVELOPER + QA CODE TEST +
- 140. NEED A USER TESTFOR YOUR NEW FEATURE? DO ITYOURSELF
- 141. BUILD A PROTOTYPE RENTTHETESTLAB
- 144. DO ITYOURSELFASKING F R HELP MAKE EASY
- 145. HOW DO YOU KNOW ALLTHIS STUFF? LONG TERM EMPLOYEE 25YEARS
- 146. GIVE NEW EMPLOYEES A BOOST
- 149. NEW WORKPLACE NEW TEAM MEMBERS NEW ACRONYMS NEW WORK STYLE NEW PROCESSES + SHOWING YOU’RE GOOD
- 150. SETCLEAR EXPECTATIONS FOR NEW TEAM MEMBERS 90 DAYPLAN
- 155. PAIR PROGRAMMING / CODE REVIEWS
- 156. FRIDAYFAMILY BREAKFAST MOST EMBARRASSING STORY SECRETTATTOO A HIDDEN TALENT
- 157. SHARED MINDSETHOW TO GETTHETEAM THINKING IN THE SAME DIRECTION
- 158. BUILDING TEAM KNOWLEDGE BUG FIX
- 159. BUILDING TEAM KNOWLEDGE BUG FIX
- 160. BUILDING TEAM KNOWLEDGE BUG FIX
- 161. BUILDING TEAM KNOWLEDGE BUG FIX ROTATION
- 162. BUILDING TEAM KNOWLEDGE FEATURE X FEATURE Y
- 163. DEVELOPING FEATURES IS A PROCESS LOTS OF SMALLDECISIONS GETA BUDDY
- 164. BUILDING TEAM KNOWLEDGE FEATURE X FEATURE Y BUDDY BUDDY
- 165. BUILDING TEAM KNOWLEDGE FEATURE BUDDY
- 166. CANARYSESSIONS TESTING IDEAS WITH THE TEAM
- 167. AGILE SLAM LIKE A BROWN BAG, BUTON TEAM PROCESS
- 168. BUILDING TEAM KNOWLEDGE TEAM DISCUSSIONS
- 169. SHARE DESIGN IDEAS
- 170. …AND COLLECTFEEDBACK
- 171. DOING THINGS RIGHT BUILD PROCESSES
- 172. DOING THE RIGHTTHINGS BUILD ADAPTABILITY ? !
- 173. TEAM YOUR WAY
- 175. THE PLAYBOOK ENVISION IT MAKEIT IMPROVEIT 40+ PLAYS TO GUIDE PROJECTTEAMS
- 177. OVERVIEW
- 180. CONCEPTTESTINGENVISION IT PAPER PROTOTYPE USER STICKER
- 181. CONCEPTTESTING
- 185. THE PLAYS
- 186. THE PLAYS THE PLAYBOOK ENVISION IT MAKEIT IMPROVEIT 40+ PLAYS TO GUIDE PROJECTTEAMS
- 187. SHARED MINDSET SUPPORTIVE CONTEXT COMPELLING DIRECTION STRONG STRUCTURE
- 188. HOW AWESOME IS YOUR TEAM?
- 189. HOW AWESOME IS YOUR TEAM? CAN YOU MEASURE IT? HEALTHY
- 190. 8 CHECK POINTS FOR BETTER TEAM HEALTH 1 FULLTIME OWNER BALANCED TEAM SHARED UNDERSTANDING VALUE AND METRICS END-TO-END DEMO README DEPENDENCIES VELOCITY
- 191. Full-time owner Balanced team Shared Value and metrics End-to-end demo Readme Dependencies Velocity CHECKPOINTS 1 2 3 4 5 TRACKINGHEALTH…MEASURINGATCHECKPOINTS
- 193. SO HEALTH SHOWS WHATNOW? IMPROVEYOURTEAM
- 194. IMPROVEYOURTEAM THINK & ACTLIKE A FOUNDER EMPOWER TEAMS TO
- 195. IMPROVEYOURTEAM BETHE CHANGE YOU SEEK
- 197. IMPROVEYOURTEAM THE A-TEAM THE MINION TEAM THE MUPPET TEAM DECIDE IN YOUR ENVIRONMENT
- 199. SINGLE CORE = PHYSICALLIMITS
- 200. MULTI CORE = COMMUNICATION REQUIRED
- 201. TEAM UP! TO BE AWESOME
- 202. TEAM UP! TO BE AWESOME THANKS @svenpet