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

Keeping -the bar- higher - XP and Peer Review

Keeping -the bar- higher - XP and Peer Review

Build systems are all about: communication, courage, feedback, respect and simplicity with those XP values and some tools you can keep your quality bar higher.

Hélio Medeiros

February 26, 2014
Tweet

More Decks by Hélio Medeiros

Other Decks in Programming

Transcript

  1. K E E P I N G H I G

    H E R E X T R E M E P R O G R A M M I N G A N D P E E R R E V I E W - T H E B A R - @helmedeiros
  2. } R E Q U I R E M E

    N T S D E S I G N D E V E L O P M E N T T E S T I N G D E P L O Y M E N T M A I N T E N A N C E L O S T I N A L O N G F L O W … E X P E C T I N G H I S T I M E T O D O H I S J O B
  3. C O M M U N I C AT I

    O N create the right thing is totally tied to what it is with whom you talk about an idea; we must expand our debates, not only within but also between the teams
  4. E L E V A T E T H E

    E F F I C I E N C Y O F Y O U R D E C I S I O N S share the discovery on what you’ve made and learn
  5. C O U R A G E create right thing

    and keep it on the right path requires courage; need to create an immune system for products
  6. “an auto-immune system, identifiying any product errors, removing the change,

    notifying the corresponding team and preventing it from installing any new change on the system until the bug is fixed” E R I C R I E S
  7. A M P L I F Y T H E

    T R A N S P A R E N C Y O F Y O U R A C T I O N S share patterns learned and used in your projects
  8. F E E D B A C K create right

    thing and keep it on the right path requires feedback; need to progressively evolve in the right direction
  9. L E A N S T A R T U

    P Build > Mesure > Learn L E A N U X Think > Make > Check
  10. F A C I L I T A T E

    T H E R E T U R N O F I N F O R M A T I O N allow collaborative feedback on everything you build or think
  11. R E S P E C T listening, learn to

    understand and respect the views of others is essential
  12. R E T I R E H I E R

    A R C H I E S everyone should have an equal voice on everything you build or think
  13. S I M P L I C I T Y

    need to focus on what is needed, and only then work as may be necessary
  14. C R E A T E A N E T

    W O R K O F T R U S T developers work with the product team on what is needed to find out the next step.
  15. how can we do that: TDD collective code ten minutes

    build peer reviewing pull requests
  16. T E C H N I Q U E S

    how can I create such a structure within my company?
  17. T E S T D R I V E N

    D E V E L O P M E N T anticipate the identification and correction of faults during development
  18. C O D E O W N E R S

    H I P I S C O L L E C T I V E all are equally responsible for all parts of the existing application code
  19. P R O J E C T S B U

    I L D S U P T O T E N M I N U T E S fast, automated builds help reduce the stress of staff in times of trouble
  20. F A C I L I T A T E

    S D I S C U S S I O N O N T H E C O D E C R E A T E D members of your team must see value in debating encourages learning through revisions
  21. F A C I L I T A T E

    C O N T R I B U T I O N S B E T W E E N T E A M S members of a team can contribute to projects of other embolden the exchange between teams
  22. T O O L S how can I create such

    a structure within my company?
  23. prod YES usando trunk? YES NO TAG NO cria tag

    trunk restaura trunk tag cria branch trunk avisou? dev homo l ok? reintegra te branch cria tag trunk loca l BUILD versioning? IN A CLICK LAUNCHING VERSIONS ORGANIZE THE LOCAL ENVIRONMENT!
  24. A T H R E E S T E P

    S P L A N T O A C H I E V E T H AT: A L L A R O U N D C O D E 1 P E E R R E V I E W I N G 2 P U L L R E Q U E S T S 3 1. Get all server permissions to install gitbucket; 2. Create a culture of use and tied to the project documentation; 3. Make visible projects which have or not unit testing, automated deployment, etc.; 1. Get all server permissions to install barkeep; 2. creating a culture of code review to stimulate, unit testing, design patterns, etc.; 1. creating a culture of knowledge tied to projects without restricting team sharing.
  25. K E E P I N G H I G

    H E R E X T R E M E P R O G R A M M I N G A N D P E E R R E V I E W - T H E B A R - @helmedeiros