AGILE IN ACTION

Thursday, 29 December 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.
Read more...

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:
Read more...

Saturday, 17 December 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.
Read more...

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.
Read more...

Thursday, 15 December 2005

Feelings of worth

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

Martin Fowler has updated The New Methodology

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

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.
Read more...

Tuesday, 13 December 2005

Teamwork and trust

Posted by Simon Baker
Tags: people, trust
Jeffrey Phillips says it's a matter of trust.
Read more...

Creative Commons Licence

Recent Posts

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

Archives

  1. 2012 (5)
  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)