The missing link of Agile: Feedback

580 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
580
On SlideShare
0
From Embeds
0
Number of Embeds
131
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

The missing link of Agile: Feedback

  1. 1. The missing link of Agile Feedback Pawel Badenski
  2. 2. I could be talking about.. Brakujący element Agile, Paweł Badeński
  3. 3. “what you did well, and what you could do better” technique Brakujący element Agile, Paweł Badeński
  4. 4. Feedback sandwich Brakujący element Agile, Paweł Badeński
  5. 5. Annual Performance Review Brakujący element Agile, Paweł Badeński
  6. 6. But... Brakujący element Agile, Paweł Badeński
  7. 7. Two rules of feedback 1. Feedback is always subjective. 2. Emotions are important. Brakujący element Agile, Paweł Badeński
  8. 8. Threat vs reward Brakujący element Agile, Paweł Badeński
  9. 9. Let’s go deeper Brakujący element Agile, Paweł Badeński
  10. 10. Emotions and logic LPU EPU
  11. 11. Triggering the Lizard is easy Brakujący element Agile, Paweł Badeński
  12. 12. “You should be writing more tests” Brakujący element Agile, Paweł Badeński
  13. 13. “I can show you a better solution” Brakujący element Agile, Paweł Badeński
  14. 14. “You could try speaking up more during the meetings” Brakujący element Agile, Paweł Badeński
  15. 15. “You always break the build” Brakujący element Agile, Paweł Badeński
  16. 16. What happens when the Spock speaks with the Lizard? Brakujący element Agile, Paweł Badeński
  17. 17. Exercise What sentence when said by someone makes you sad, angry, annoyed, or trigger other negative emotion? Brakujący element Agile, Paweł Badeński
  18. 18. LUCY JOHN The code that you’re committing has very long methods, and I find it difficult to understand. Your code is difficult to understand to me and I don’t complain.
  19. 19. LUCY JOHN I use TDD and I’m sure my code is well tested, and implemented according to simple design principles. Are you saying my code is bad, and your code is great?
  20. 20. LUCY JOHN No, I’m not saying my code is great. I’m saying I can show how I’m using TDD to make the code look better. I’ve been a programmer for 6 years and I don’t need TDD.
  21. 21. Discussion (in pairs) You learnt about: ● Threat vs reward mechanism ● LPU (the Spock) and EPU (the Lizard) ● the Spock and the Lizard How do these relate to your past experiences? Brakujący element Agile, Paweł Badeński
  22. 22. How to calm down the Lizard? Brakujący element Agile, Paweł Badeński
  23. 23. Calming down (made in Google) Siberian North Railroad technique ● Stop ● Breath ● Notice ● Reflect ● Respond
  24. 24. Exercise your “emotions muscle” ● for the least - mindfully pause ● replay difficult conversations afterwards and apply Siberian North Railroad technique ● once the muscle is well exercised, this process will happen in a matter of a second Brakujący element Agile, Paweł Badeński
  25. 25. Exercise your “emotions muscle” ● for the least - mindfully pause ● replay difficult conversations afterwards and apply Siberian North Railroad technique ● once the muscle is well exercised, this process will happen in a matter of a second Brakujący element Agile, Paweł Badeński
  26. 26. Exercise your “emotions muscle” ● for the least - mindfully pause ● replay difficult conversations afterwards and apply Siberian North Railroad technique ● once the muscle is well exercised, this process will happen in a matter of a second Brakujący element Agile, Paweł Badeński
  27. 27. Exercise (one more time) What sentence when said by someone makes you sad, angry, annoyed, or trigger other negative emotion? Brakujący element Agile, Paweł Badeński
  28. 28. Discussion (in pairs) You learnt about: ● Siberian North Railroad technique How does this relate with your past experiences? Brakujący element Agile, Paweł Badeński
  29. 29. Why the Spock is not as smart as it thinks? Roleplay Brakujący element Agile, Paweł Badeński
  30. 30. Ladder of inference Brakujący element Agile, Paweł Badeński
  31. 31. actions beliefs conclusions assumptions interpreted reality selected reality reality and facts Brakujący element Agile, Paweł Badeński
  32. 32. Exercise (in pairs) analyse the situation using ladder of inference Brakujący element Agile, Paweł Badeński
  33. 33. Discussion (in pairs) You learnt about: ● ladder of inference How does this relate to your past experiences? Brakujący element Agile, Paweł Badeński
  34. 34. ● Spock to Spock ○ overanalyzing, focusing on every little detail, discussing word definitions ● Spock to Lizard ○ disagreement ● Lizard to Lizard ○ conflict or even a fight Communication - what doesn’t work? Brakujący element Agile, Paweł Badeński
  35. 35. How to use the Spock and the Lizard effectively? Brakujący element Agile, Paweł Badeński
  36. 36. It’s all about empathy Brakujący element Agile, Paweł Badeński
  37. 37. What’s violent communication Brakujący element Agile, Paweł Badeński
  38. 38. “You talk too much in the meetings” Moralistic judgement Brakujący element Agile, Paweł Badeński
  39. 39. “He writes better tests than you do” Comparing with others Brakujący element Agile, Paweł Badeński
  40. 40. “You should refactor this method” Using shoulds and haves Brakujący element Agile, Paweł Badeński
  41. 41. “Design is poor, because the project manager told me to do a quick fix” Denial of responsibility Brakujący element Agile, Paweł Badeński
  42. 42. Nonviolent communication
  43. 43. Nonviolent communication ● invented by American psychologist Marshall Rosenberg ● used in business, negotiation, conflict resolution ● trainings in London: Daren De Witt, NVC Resolutions ● more information on http://cnvc.org Brakujący element Agile, Paweł Badeński
  44. 44. Observation Feeling Need Request I feel upset When I see you committing failing test this week for the 3rd time Because I need to know that everyone cares about the quality of the product Would you be willing for us to discuss this? Brakujący element Agile, Paweł Badeński
  45. 45. Tips for NVC ● this process can be done from the other person’s perspective (“you look upset”, “do you need certainty”) ● the goal is to build a connection with the other person instead of trying to persuade them Brakujący element Agile, Paweł Badeński
  46. 46. Tips for NVC ● this process can be done from the other person’s perspective (“you look upset”, “do you need certainty”) ● the goal is to connect with another person instead of trying to persuade them Brakujący element Agile, Paweł Badeński
  47. 47. Exercise (in pairs) Replay the conversation between John and Lucy using NVC Brakujący element Agile, Paweł Badeński
  48. 48. Roles John - with the company for 7 years, defensive, doesn’t want to come across as less skilled in front of Lucy Lucy - new programmer, 2 years of professional experience, an enthusiast of TDD and new technologies Brakujący element Agile, Paweł Badeński
  49. 49. Discussion (in pairs) You learnt about: ● NVC (observation, feeling, need, request) How does this relate to your past experiences? Brakujący element Agile, Paweł Badeński
  50. 50. Summary Brakujący element Agile, Paweł Badeński
  51. 51. 7 day challenge Brakujący element Agile, Paweł Badeński
  52. 52. Contact pawel.badenski@gmail.com Brakujący element Agile, Paweł Badeński

×