Thursday, December 29, 2005

Being empowered means being prepared to take a chance

Posted by Simon Baker
In an empowered environment, any action means taking some risk because there is the chance of making mistakes. When a team is empowered it has authority to decide how best to achieve a goal and it's acceptable to fail when learning is happening.

Giving trust

Posted by Simon Baker
Tags: people, trust
The best way to gain trust is to give trust.

Leading the way

Posted by Simon Baker
It doesn't take power or authority to demonstrate leadership. The most effective leadership depends on the ability of an individual to recruit others to a particular course of action through persuasion and negotiation, and not by enforcing compliance because of some authority.

Monday, December 19, 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:

Saturday, December 17, 2005

Slop and slack

Posted by Simon Baker
Michael Feathers identified iteration slop as the time spent before an iteration, preparing for it, and the time spent after an iteration, finalizing the work.

Friday, December 16, 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.

Thursday, December 15, 2005

Feelings of worth

Posted by Simon Baker
Tags: people, team
Virginia Satir wrote:

Martin Fowler has updated The New Methodology

Posted by Simon Baker
Tags: agile
Read The New Methodology.

Wednesday, December 14, 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.

Tuesday, December 13, 2005

Serenity isn't freedom from the storm, but peace within the storm

Posted by Simon Baker
Tags: iteration
Amidst the storm of unpredictability that is software development, you can find calm and control by using Scrum. An empirical process such as Scrum uses honest feedback, and frequent inspection and adaptation to control progress in an unpredictable environment.

Creative Commons Licence

Recent Posts

  1. Spark The Change - Innovation Governance
  2. Lean Day London 2014
  3. The Mechanics Of Meaning
  4. Engineering Design
  5. Debugging Grails Database Performance
  6. Grails for Hipsters
  7. Governance - Friend or Foe?
  8. The Energized Work lab is moving aboard ship
  9. Gus Power on the future of software development at The CW500 Club
  10. Agile On The Beach: Session: How Are We Doing?


  1. 2014 (4)
  2. 2013 (2)
  3. 2012 (27)
  4. 2011 (24)
  5. 2010 (31)
  6. 2009 (41)
  7. 2008 (69)
  8. 2007 (152)
  9. 2006 (128)
  10. 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)
  11. 2004 (2)


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