AGILE IN ACTION

Monday, 19 December 2005

Getting to know people

Posted by Simon Baker

When I start on a project as a Scrum Master, I want to get to know the people I’ll be working with as quickly as possible. Beyond the basic introductions, I perform the following activities with the team and Product Owner:

  • I ask each team member how they would like to receive feedback. I also ask them if they would be willing to give me feedback. We then agree an informal contract which allows us to discuss issues easily and honestly.

  • I ask each team member to complete a motivation exercise and to share the results with everyone. This helps me and the other team members understand what excites and what deflates a person.

  • I ask each team member to complete a simple questionnaire based on the Myers-Briggs Indicator and to share their type (an alternative type description is available here) classification with everyone. This helps me and the other team members understand the styles of interaction that other people prefer to employ.

I also like to have weekly one-to-one meetings with the team members and the Product Owner. These take no longer than 15 minutes each, and are peer-to-peer and, in some cases, coach-to-coachee sessions that aim to be mutually beneficial. They provide a forum in which to discuss any issues or topics, and to provide feedback, privately.

Creative Commons Licence

Recent Posts

  1. System failure is inevitable so design for a fast recovery
  2. Delight comes as a surprise in unexpected places
  3. Help create business agility. Bake quality in
  4. Governance - Friend or Foe?
  5. 70% Forum
  6. Measuring purpose. Measuring customer delight
  7. Stop pushing features and start delighting users
  8. Lost without a goal
  9. Emotion creates the common language
  10. Five sneaky ways to kill an initiative

Archives

  1. 2012 (16)
  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 (40) culture (18) extreme programming (21) leadership (18) lean (47) people (26) planning (17) retrospective (18) scrum (41) story (19) team (30) testing (19) xpday (19)