Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Working in an effective team

Working in an effective team

A presentation given at the Belgian CocoaHeads about working in an effective team. A case study of how we work at VRT

103e1ebcacd620770cf32a36b9aba17e?s=128

AppFoundry

May 07, 2014
Tweet

Transcript

  1. Working in an effective team ENABLING SOFTWARE CRAFTSMANSHIP

  2. SYNOPSIS Working in an effective team ABOUT US MEET THE

    TEAM EFFECTIVE? WHAT’S EFFECTIVE? THE QUEST FOR EPIC EFFECTIVENESS
  3. Working in an effective team Early 2013, a team of

    3 developers and a product owner. Put together to work out a Proof Of Concept around a new idea. Immediately focused on new(er) technologies, best practices and Quality Assurance. Delivering a platform, aligned to the needs of every persona. In the process of creating a “finished” product we are open, transparant and honest about the state of the product. During the development we want to enrich the team, both personal and professional. A team of 7 developers, a tester and a product owner. A close group of people, dedicated to deliver quality software to our best abilities. A bunch of people constantly trying to motivate and challenge each other. INTRODUCTION WHO WE ARE HISTORY MISSION
  4. WHO WE ARE TESTER LIENE SCRUM MASTER, DEVELOPER JORIS PRODUCT

    OWNER TIM DEVELOPER MARC
  5. WHO WE ARE DEVELOPER NIELS DEVELOPER RICARDO DEVELOPER JORIS DEVELOPER

    CHRIS
  6. ? EFFECTIVE What the internet is telling us about effective

    teams…
  7. UNITY OF PURPOSE OBJECTIVES THE TEAM AGREES UPON GOAL

  8. SELF CONSCIOUSNESS KNOWN SELF-SET GOALS GOAL

  9. INFORMAL, RELAXED PEOPLE LIKE EACH OTHER ATMOSPHERE

  10. TEAM DISCUSSIONS LISTENING TO EACH OTHER, IMPROVING WHAT NEEDS TO

    BE DONE COMMUNICATION
  11. FREE TO EXPRESS BOTH IDEAS & FEELINGS COMMUNICATION

  12. AGREE TO DISAGREE EXAMINE WHY, LET THE TEAM FIND SOLUTIONS

    COMMUNICATION
  13. T AKE RESPONSIBILITY EACH MEMBER IS EXPECTED TO CARY HIS/HER

    OWN WEIGHT OWNERSHIP
  14. CRITICISM IS A GIVEN IT NEEDS TO BE CONSTRUCTIVE, WORKING

    TOWARDS A BETTER PRODUCT COMMUNICATION
  15. LEADERSHIP SHIFTS NOT WHO, BUT HOW OWNERSHIP

  16. TRUST & RESPECT MAKES THE TEAM AUTONOMOUS COMMUNICATION

  17. BE HONEST YOU GET WHAT YOU GIVE COMMUNICATION

  18. TEAM EVENTS BRING PEOPLE CLOSER TOGETHER ATMOSPHERE

  19. ALLOW CONFLICT DON’T FAVOUR ANY SIDE, DISCUSS AND FIND BETTER

    SOLUTIONS COMMUNICATION
  20. HIRE AS A TEAM ENSURES THE TEAM GLUES TOGETHER OWNERSHIP/ATMOSPHERE

  21. LET EVERYONE SPEAK SPARK THE QUIET TYPES! COMMUNICATION

  22. REW ARD THE TEAM EVERY MINOR SUCCESS IS A BREAK

    THROUGH ATMOSPHERE
  23. REW ARD INDIVIDUALS REWARD BASED ON TEAMWORK ATMOSPHERE

  24. EFFECTIVE! COMMUNICATION GOAL OWNERSHIP ATMOSPHERE

  25. 1 2 3 4 MIRACLES DO NOT EXIST THE QUEST

    Well, the internet is right and all, but how do you do this? What is the secret, where is the silver bullet?
  26. THE QUEST

  27. TAKE BABY STEPS

  28. 1 2 3 4 REQUIREMENTS SHOWCASE STATUS REPORTS PLAN 5

    EVALUATE BACKLOG HOW WE WORK 2 WEEK SPRINTS DAILY STANDUP SPRINT DEMO RETROSPECTIVE
  29. STAND UP Our daily standup, at our humble scrum board

  30. RED BLUE GREEN FAILING TEST TEST DRIVEN DEVELOPMENT FIXED TEST

    REFACTOR
  31. PAIR PROGRAMMING One driver, one navigator. Helps well while writing

    non-trivial code.
  32. CODE REVIEW Detect problems early. Learn from someone else’s code.

  33. 1 2 3 BUILD & CHECK CI PICKUP CODE &

    COMMIT 4 REPORT RESULTS CONTINUOUS INTEGRATION
  34. BEHAVIOUR DRIVEN TESTING GIVEN WHEN THEN

  35. BEHAVIOUR DRIVEN TESTING Feature: Example! As a user! I want

    to be able to share the interesting news ! So other people can discover the article! ! Scenario: Open Share activity! Given I am on the “interesting news” screen! When I tap the share button! Then I should be able to select a social ! network to share on!
  36. CONTINUOUS DELIVERY CODE TEST, TEST, TEST RELEASE

  37. CONTINUOUS DELIVERY ✔ ✘ ✔ ✔ ✔ ✔ ✔ ✔

    ✔ ✔ ✔ ✘ ✔ ✔ ✔ ✔ ✔ Build 2.13 Build 2.14 Build 2.15 Build 2.16 Build Integration Cucumber Performance Production
  38. SAD CUSTOMER

  39. HAPP(Y)(IER) CUSTOMER

  40. TEAM DEMO

  41. RETROSPECTIVE Evaluating the D.O.D. during a retrospective, triggered by a

    problem detected in our sprint process.
  42. BROWN BAGS

  43. KUDOS

  44. TEAM EVENTS

  45. THANK YOU FOR YOUR ATTENTION! HTTP://WWW.IDA-MEDIAFOUNDRY.BE ALL DONE

  46. We are at Business Park King Square Veldkant 33A, 2550

    Kontich MAP CONTACT US WWW.IDAMEDIAFOUNDRY.BE INFO@IDA-MF.BE +32 (0) 3 871 99 66
  47. @IDAMEDIAFOUNDRY @MIKESEGHERS GITHUB.COM/IDAMEDIAFOUNDRY FOLLOW US