Skip to main content

Scrum Books to Win Friends and Influence people

One way to help make Scrum and Agile less frightening to non-agilists in the company is to simply make information available. An easy, non-threatening way to do this is to set up a library and put it in an obvious place. What books to put in the library? Here's a list I recently gave to a customer:
  • Agile Project Management with Scrum Ken Schwaber. Start here.
  • The Art of Agile Development Jim Shore. OK, if you're a developer, you might prefer to start here.
  • Scrum and XP from the Trenches Henrik Kniberg. This is what it's really about.
  • Agile Estimating and Planning von Mike Cohn. Proof that estimating & planning are not black magic.
  • User Stories Applied: For Agile Software Development Mike Cohn. After Ken's book & Mike's books I felt I was ready to conceive, plan and deliver software projects effectively.
  • Lean Software Development: An Agile Toolkit for Software Development Managers Mary Poppendieck. A bridge for managers between their MBA studies and real agility.
  • Implementing Lean Software Development: From Concept to Cash Mary Poppendieck. Tools for putting your company on a diet.
  • The Enterprise and Scrum Ken Schwaber. An approach for Scaling Scrum.
  • FIT for Developing Software: Framework for Integrated Tests Rick Mugridge und Ward Cunningham. Tests are the bleeding edge between customer and developers. How to know that you are getting what you want and that it stays what you want.
  • Agile Software Development in the Large: Diving Into the Deep Jutta Eckstein. One of the first books on scaling agility. (Oddly, although the author is German, I found the English more readable. Maybe it's because I'm Swiss.)
  • Agile Retrospectives: Making Good Teams Great Esther Derby. The key to continuous improvement is the retrospective. The key to good retrospectives is keeping them fresh and interesting. Many good approaches for many different circumstances.
  • Fearless Change: Patterns for Introducing New Ideas Linda Rising. Changing the organization is the hardest part of agile.
  • The Software Project Managers Bridge to Agility Sliger & Broderwick. If your manager is a PMP, this book will help her or him understand that words "agile" and "project management" can be applied to the same project successfully.
I am generally skeptical of translated books (actually, I kind of embarrassed myself recently by recommending some well known titles, only to discover that their German translations were not great), but there are now a growing number of original German works which offer excellent places to start for native German speakers:
  • Scrum mit User Stories, Ralf Wirdemann - what you need to get started doing Scrum.
  • Scrum - Agiles Projektmanagement erfolgreich einsetzen Roman Pichler - a condensed version of Ken Schwaber's "APM with Scrum" and Mike Cohn's books. A good management introduction.
Any list is a compromise, and there are many good books that I didn't mention (and I wish I had more time to read them - sigh). So happy reading!


Popular posts from this blog

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

Explaining Story Points to Management

During the February Scrum Breakfast in Zurich, the question arised, "How do I explain Story Points to Management?" A good question, and in all honesty, developers can be an even more critical audience than managers.

Traditional estimates attempt to answer the question, "how long will it take to develop X?" I could ask you a similar question, "How long does it take to get the nearest train station?

The answer, measured in time, depends on two things, the distance and the speed. Depending on whether I plan to go by car, by foot, by bicycle or (my personal favorite for short distances) trottinette, the answer can vary dramatically. So it is with software development. The productivity of a developer can vary dramatically, both as a function of innate ability and whether the task at hand plays to his strong points, so the time to produce a piece of software can vary dramatically. But the complexity of the problem doesn't depend on the person solving it, just …

Money for Nothing, Changes for Free

“Money for Nothing, Changes for Free” encourages both customers and suppliers to focus on value.

A key advantage of Scrum projects is that at least once per sprint you have something that could be shipped and no work in progress. You can change direction every sprint, and you can reevaluate whether the project is a good investment or if your money could be better spent elsewhere. Abrupt cancellation is risky for the supplier.

While the concept of an early-exit penalty is not new, Jeff Sutherland gave it a unique allure with his allusion to the Dire Straits hit.
Desired Benefit Incentivize both customers and suppliers to focus on functionality that provides genuine value.
Structure This works with Agile software projects because there is little or no work in progress. After each Sprint, functionality is either complete or not started. Work is basically on a Time and Materials basis with a cost target, often with the intention that the project should not use up the entire project budge…