Skip to main content

How to launch a corporate Agile library

a vending machine - random books
One simple initiative each Agile Transformation can make is to create a book lending library focused on Agile processes, organizational change, learning organizations, best engineering practices in software development and other topics.  Since this topic of "what books would you recommend" comes up quite a lot, perhaps it is time for me to join the ranks of hundreds of people making their top 10 Agile books list.


Top 100 Agile Books (Edition 2012) by Jurgen Appelo

But no that's not what this post will be.  It is something much more useful.  Instructions on creating your very own lending library.

  1. Get funding - about $1000 for the first quarter.
  2. Find a book shelf and a reading room with comfortable chairs.
  3. Purchase 3 copies of each book on the short list - these books are the seed stock.
  4. Make a company logo sticker for the back of each book and inside cover.
  5. Make signs and hall way posters to advertise your new library.
  6. Make a book list to hang on the wall, listing all titles, authors, and number of copies.
  7. Upon arrival of a majority of your new (used) books - sticker the spines and inside cover and place them on the shelf.
  8. Open the library - send email, put up posters, invite people to read your books.
  9. In one month look at the shelf - compare it to the book list - purchase more of the books that are missing from the shelf (celebrate - they are being used).
  10. In month number two - send out a reminder email, and posters in the hall to return the book after they are read - give someone else a chance to enjoy such wonderful knowledge that has just been collecting dust on your night stand.
  11. In month three, work up a new list and purchase more books.
  12. Repeat until the whole organization knows everything.
I am constantly amazed at the looks I get from managers that can't image a lending library without a complicate check-out procedure to insure we get the books back.  I remind them that these are our trusted employees.  The ones with the keys to the client's kingdoms.  The same employees that could launch Thermonuclear War with just a key stroke.  So maybe we can trust them to return the books.  And hey, if they forget, then it cost us a few dollars to educate them in some new technique.  Compare that cost to sending them to a training session that they are planning to take their phone and TXT with their BFF the whole time.

Some further recommendation:
  • purchase used book - many great books have been in print for a while
  • don't worry about returns - consider it a bonus plan for employees that can read
  • add a wish-list to your book shelf
  • add a donation can to the shelf - to defray the cost of forgetful patrons
  • add a list of YouTube video links, and other resources on paper
  • add a general reading shelf - give-one & take-one shelf
  • don't forget the differenator between the library and the book store - comfortable sitting & coffee
  • see also: http://littlefreelibrary.org 
Here's a short list of Agile books to add to the library.

Or just buy any book on the Pragmatic Book Shelf.

Methodologies and Principles
Development Practices
Management and Other Practices

Post a Comment

Most Popular on Agile Complexification Inverter

David's notes on "Drive"

- "The Surprising Truth about what Motivates Us" by Dan Pink.

Amazon book order
What I notice first and really like is the subtle implication in the shadow of the "i" in Drive is a person taking one step in a running motion.  This brings to mind the old saying - "there is no I in TEAM".  There is however a ME in TEAM, and there is an I in DRIVE.  And when one talks about motivating a team or an individual - it all starts with - what's in it for me.

Introduction

Pink starts with an early experiment with monkeys on problem solving.  Seems the monkeys were much better problem solver's than the scientist thought they should be.  This 1949 experiment is explained as the early understanding of motivation.  At the time there were two main drivers of motivation:  biological & external influences.  Harry F. Harlow defines the third drive in a novel theory:  "The performance of the task provided intrinsic reward" (p 3).  This is Dan Pink's M…

Exercise:: Definition of Ready & Done

Assuming you are on a Scrum/Agile software development team, then one of the first 'working agreements' you have created with your team is a 'Definition of Done' - right?



Oh - you don't have a definition of what aspects a user story that is done will exhibit. Well then, you need to create a list of attributes of a done story. One way to do this would be to Google 'definition of done' ... here let me do that for you: http://tinyurl.com/3br9o6n. Then you could just use someone else's definition - there DONE!

But that would be cheating -- right? It is not the artifact - the list of done criteria, that is important for your team - it is the act of doing it for themselves, it is that shared understanding of having a debate over some of the gray areas that create a true working agreement. If some of the team believes that a story being done means that there can be no bugs found in the code - but some believe that there can be some minor issues - well, …

What belongs on the Task Board?

I wonder about these questions a lot - what types of task belong on the task board?  Does every task have to belong to a Story?  Are some tasks just too small?  Are some tasks too obvious?  Obviously some task are too larger, but when should it be decomposed?  How will we know a task is too large?

I answer these questions with a question.  What about a task board motivates us to get work done?  The answer is: T.A.S.K.S. to DONE!



Inherent in the acronym TASKS is the point of all tasks, to get to done.  That is the measure of if the task is the right size.  Does it motivate us to get the work done?  (see notes on Dan Pink's book: Drive - The surprising Truth about what motivates us) If we are forgetting to do some class of task then putting it on the board will help us remember.  If we think some small task is being done by someone else, then putting it on the board will validate that someone else is actually doing it.  If a task is obvious, then putting it on the board will take vi…

Elements of an Effective Scrum Task Board

What are the individual elements that make a Scrum task board effective for the team and the leadership of the team?  There are a few basic elements that are quite obvious when you have seen a few good Scrum boards... but there are some other elements that appear to elude even the most servant of leaders of Scrum teams.









In general I'm referring to a physical Scrum board.  Although software applications will replicated may of the elements of a good Scrum board there will be affordances that are not easily replicated.  And software applications offer features not easily implemented in the physical domain also.





Scrum Info Radiator Checklist (PDF) Basic Elements
Board Framework - columns and rows laid out in bold colors (blue tape works well)
Attributes:  space for the total number of stickies that will need to belong in each cell of the matrix;  lines that are not easy eroded, but are also easy to replace;  see Orientation.

Columns (or Rows) - labeled
    Stories
    To Do
    Work In P…

What is your Engagement Model?

What must an Agile Transformation initiative have to be reasonably assured of success?

We "change agents" or Agilist, or Organizational Development peeps, or Trouble Makers, or Agile Coaches have been at this for nearly two decades now... one would think we have some idea of the prerequisites for one of these Transformations to actually occur.  Wonder if eight Agile Coaches in a group could come up with ONE list of necessary and sufficient conditions - an interesting experiment.  Will that list contain an "engagement model"?  I venture to assert that it will not.  When asked very few Agile Coaches, thought leaders, and change agents mention much about employee engagement in their plans, models, and "frameworks".  Stop and ask yourselves ... why?

Now good Organizational Development peeps know this is crucial, so I purposely omitted them from that list to query.

One, central very important aspect of your Agile Transformation will be your Engagement model.