Reading List..

August 12, 2009 by admin in blog, Uncategorized | 1 Comment

I have been involved in transitioning two of the largest organizations (in the North America) to value driven project methodologies such as Agile, Scrum, and Lean. During these transitions, I have coached several teams, managers, and executives on Agile Practices and principles, and have often been asked for recommended reading list. I have accumulated a list of references that I often recommend my new teams read when starting their journey on Agile. Here is the list for your reference.

Books

  • Agile Project Management with Scrum (Schwaber)
  • User Stories Applied (Cohn)
  • Scrum and XP from the Trenches.pdf (Kniberg)
  • Scaling Software Agility (Leffingwell)
  • Agile Estimating and Planning (Cohn)
  • Implementing Lean Software Development: From Concept to Cash (Poppendieck)
  • Test Driven Development: By Example (Beck)
  • Agile Software Development with SCRUM (Schwaber)

    Online References

  • Scrum Alliance
  • Being Agile is our favourite thing
  • Agile Manifesto
  • Agile Wikipedia
  • Mountain Goat Software
  • Jeff Sutherland NYC Spin
  • Scrum and XP from the Trenches
  • Agile Project Leadership
  • Agile Management
  • Ward Cunningham on the origin of the term Technical Debt
  • Agile Thoughts
  • Testers Shine on Agile Projects
  • Requirements Up Front
  • Agile Requirements
  • BSA Role
  • It’s Not Just Standing Up
  • Big Macs vs. The Naked Chef
  • Agile Has Crossed the Chasm
  • Constructive Disruption and Compromised Agility
  • Kanban in a nutshell

    Learn from the experts: Blogs, RSS Feeds

  • Schwaber on Scrum
  • Agile Advice
  • Agile Alliance
  • Agile Management Blog
  • Implementing Scrum
  • Pages tagged with ‘agile’ on del.icio.us
  • Stevey’s Blog Rants: Good Agile, Bad Agile
  • agile at google
  • The Planning Onion: Five Levels of Agile Planning

    Shameless post: link to my blog

  • Unlearn what you have learnt
  • Delivering the W, One Game at a Time
  • Field of View
  • a quick introduction: What is Scrum?

    • I prefer Team Leader, or Team Coach. Project leeadr implies a team can only be on one project, which is not always true, especially in support situations.Coach is a great term because a coach is a person that is invested in success/failure (winning/losing), but isn’t on the field doing the work. Their job is to provide the mentoring and tools (and environment) for the team to be able to succeed.