AGILE IN ACTION

Tuesday, 21 February 2006

APLN and collaborative leadership

Posted by Simon Baker

I’ve finally joined the APLN . I’ve been planning to join for a while but I was eventually spurned into action by the creation of a London Chapter . The primary aim of APLN is to make people great project leaders by focusing on value, customers, teams, individuals, context and uncertainty. Read about APLN and the Declaration of Interdependence for more information.

Lately, I’ve been reading about collaboration techniques and collaborative leadership so I’m particularly interested to see what gets discussed in this forum. A few hot topics of interest to me at the moment include:

  • Learning and developing techniques that help inculcate Agile values into team members so they become guided instinctively by the principles of Agile as they perform Extreme Programming practices.
  • Learning and developing techniques that help customers to take ownership and responsibility that is commensurate with their role, and to engage proactively as a full-time member of the project.
  • Finding new ways to help team members understand the empowering effect of being in a self-organising team, and within this context, to achieve their capabilities for creativity and effective teamwork while demonstrating collective responsibility.
  • Exploring the dynamic nature of leadership as a part of collaboration in a self-organising team.
Links:

Collaborative Leadership
Collaborative Leadership Training Tools

Books:



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)
    1. December (16)
    2. November (26)
    3. October (7)
    4. September (11)
    5. August (7)
    6. July (7)
    7. June (4)
    8. May (4)
    9. April (4)
    10. March (4)
    11. February (14)
      1. Don't be afraid to make mistakes
      2. APLN and collaborative leadership
      3. Scrum ba
      4. Ten-minute build, continuous integration and developer rhythm
      5. User stories part 3: Using spikes to help estimate user stories
      6. User stories part 2: Adaptive planning
      7. User stories part 1: What is a user story and who writes them?
      8. Ba
      9. Watch out for the mini-series
      10. Ideal time vs. story points
      11. Making the quality-factor visible
      12. User stories and tasks
      13. Knowing when you're done
      14. Switching pair-programming partners
    12. January (24)
  8. 2005 (63)
  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)