AGILE IN ACTION

Wednesday, 14 December 2005

Seeking improvement and receiving feedback

Posted by Simon Baker
Tags: feedback

Kent Beck identifies improvement as a principle. He says “there is no perfect process, there is no perfect design, there are no perfect stories. You can, however, perfect your process, your design, and your stories”. You can also perfect yourself.

It’s important to learn and improve. I want to continually improve as a team member, as a scrum master, as a coach, and as a person. Feedback is a value of Extreme Programming that provides a mechanism which facilitates improvement. Don’t be afraid to ask someone for feedback. However, recognize that it takes courage to provide feedback, so make it easy for that person to give you feedback. If it’s general feedback you want, try explaining what motivates you and demotivates you. If you have your own ideas on areas in which you could improve volunteer that information.

When receiving feedback, listen actively and receive it genuinely without being defensive. Seek explanations and specific examples and show your appreciation by following at least some of the advice. You should endeavor to make visible improvements based on the feedback.

Creative Commons Licence

Recent Posts

  1. Pursuing features increases total cost of ownership
  2. Organization complexity is a waste farm
  3. Managing costs provides a false sense of security
  4. State of Agile survey for 2011 tells a familiar story
  5. (I can't get no) satisfaction, let alone customer delight
  6. Positive emotions and purpose
  7. People don't buy what you do, they buy why you do it
  8. Too busy chopping wood to sharpen the axe
  9. So you want a fresh apple
  10. Systems are seductive

Archives

  1. 2012 (6)
  2. 2011 (24)
  3. 2010 (31)
  4. 2009 (41)
  5. 2008 (69)
  6. 2007 (152)
  7. 2006 (128)
  8. 2005 (63)
    1. December (22)
      1. Giving trust
      2. Being empowered means being prepared to take a chance
      3. Leading the way
      4. Getting to know people
      5. Slop and slack
      6. What does it mean to be empowered?
      7. Feelings of worth
      8. Martin Fowler has updated The New Methodology
      9. Seeking improvement and receiving feedback
      10. Teamwork and trust
      11. Rules for simplicity
      12. Serenity isn't freedom from the storm, but peace within the storm
      13. How not to do it: Agile development, Microsoft-style
      14. The illusion of fixed price contracts
      15. Effective conversation
      16. Your scrum team needs you
      17. Can trust be restored once it's lost?
      18. Under-promising and over-delivering is a process smell
      19. Daily scrum haiku
      20. Write production-ready code faster with TDD
      21. Kent Beck talks about Extreme Programming and QA
      22. Talking about Selenium with Luke Closs
    2. November (15)
    3. October (11)
    4. August (8)
    5. July (2)
    6. June (1)
    7. May (4)
  9. 2004 (2)

Tags

agile (43) big visible chart (15) conference (39) culture (18) extreme programming (21) leadership (18) lean (47) people (26) planning (17) retrospective (18) scrum (41) story (18) team (30) testing (18) xpday (19)