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

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, …

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…

Webinar: Collaboration at Scale: Defining Done, Ready, and NO.

I was invited to participate in a Scrum Alliance Webinar.  Maybe you would like to listen to us in a discussion of techniques to collaborate at scale (remotely and with many people).  The topic is one that I've got some experience in discussions - yet I never seem to get to done...
Collaboration at Scale: Defining Done and Ready and NO for Distributed Teams
With Joel Bancroft-Connors, Agile Organizational Coach; David A. Koontz, Agile Transition Guide; and Luke Hohmann, CEO and Founder of Conteneo, Inc.


14 February 2018 11 a.m. ET (USA).




The Scrum Guide is pretty clear on the criticality of the definition of Done: "When a Product Backlog item or an Increment is described as "Done," everyone must understand what "Done" means. However, the Scrum Guide ALSO says that the definition of Done can "vary significantly per Scrum Team." This leads us to examine when and how the definition of Done should vary, how distributed teams should cr…

A T-Shaped 21st Century Knowledge Worker

Knowledge workers in the 21st Century must have many areas of deep knowledge, while also be capable of collaboration across multiple other domains with dissimilar T-shaped individuals.  This description of a person is a metaphor.  Compare it to the shape of the "I" in the classic saying there is no "I" in Team.


I first read about Scott Ambler's term "Generalizing Specialist" - but it's so hard to remember the proper order of the words... get it backwards and it has an inverted meaning... T-Shaped is easier to remember. 
A generalizing specialist is someone who:
Has one or more technical specialties (e.g. Java programming, Project Management, Database Administration, ...). Has at least a general knowledge of software development. Has at least a general knowledge of the business domain in which they work. Actively seeks to gain new skills in both their existing specialties as well as in other areas, including both technical and domain areas.  General…

A FAILURE to Communicate

I was working with a failing team some time ago.  I use "failing" to describe the outcome of the team - not the people on the team.  Are you OK with that description?



An issue arrose in the stand up - a team member that was to verify the quality of a procedure did so and reported that there were a few records that didn't match expectation in the data set.  Upon inquire the number of records not matching was over 2000.  Most people acknowledged immediately the exaggeration - I could tell by the laughter.  After about 10 minutes of discussing the details of the problem - it appeared the team had a handle on the specific situation.

I stopped the discussion and inquired if they could name the impediment.  One team member did a great job of describing the impediment as a _communication gap_.  Wonderful - I could work with that - the problem had a name and it didn't include anyones Proper Name.

"If the problem has a first name; we are going to have a problem."

I&#…