AGILE IN ACTION

Friday, 16 December 2005

What does it mean to be empowered?

Posted by Simon Baker

Understandably, some developers who come from a command and control environment are uncomfortable in a self-organizing team that empowers developers. In a recent post to the Scrum development newsgroup about coaching a developer away from being spoon-fed, an interesting discussion ensued about what it meant to be an empowered developer on a team.

empower - verb, to invest (someone) with the power and authority to do something.

Martine Devos questioned whether Scrum Masters sometimes just try too hard. Certainly pushing empowerment can generate resistance in the people we are trying to empower. It needs to happen naturally. But coaching can help. As Dave Bly said, if you have teenage children, you know that they don’t always listen to you or heed your advice, no matter how much you talk or shout. Sometimes it’s just better to let them ‘stub their toes’ a few times and learn for themselves. The trick is to find ways to help them learn from their failures in small and non-destructive ways.

Power can be ascribed by position. This type of power is given to you by being part of a self-organizing team. Is this power important? Yes it is. But Martine identifies an inner power that everyone has, regardless of position, and this is important too. She says nobody gives you inner power because someone tells you that you’re empowered. You get your inner power when you face your fears and act anyway. Personal power is fueled by your ability to perform and your insistence to communicate freely, even in a command and control environment. Having positional power isn’t worth much if you can’t bring your personal power to bear. In an empowered, self-organizing team you first need to recognize and embrace your inner power, using it to good effect, before you can use your positional power and operate and behave as an empowered member of the team.

Perhaps, as Scrum Masters, we should be more prepared to take a step back and give the team the space and time to unfold and learn to work as a team, while each team member finds their personal power and becomes empowered. The problem is, in the real world, in a commercial environment, you can’t wait forever.

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)