Skip to main content

Books for Getting Started With Scrum

A collegue of mine asked me yesterday, "As a CIO, what books should I read to get up to speed on Scrum?" Here are my recommendations:
  1. Agile Project Management with Scrum by Ken Schwaber. The Basics, so start here.
  2. Agile Estimating and Planning by Mike Cohn  - How to plan the project
  3. User Stories Applied by Mike Cohn - how to gather requirements and size the project 
  4. Implementing Lean Software Development by Mary Poppendieck and Tom Poppendieck -- 7 principles to guide you from Concept to Cash
  5. Lean Software Development: An Agile Toolkit by Mary Poppendieck and Tom Poppendieck -- 22 Tools from Seeing Waste to Contracting alternatives to get you from Concept to Cash.
These books are focused on strategic and operational management.

What are your suggestions for engineering practice books?

Comments

Jonas said…
I would recommend "The Art of Agile Development" by James Shore and Shane Warden.
You can see the interview with Shane on InfoQ: http://www.infoq.com/interviews/The-Art-of-Agile-Development-James-Shore

Another one is "Scrum and XP from the Trenches" by Henrik Kniberg. See http://blog.crisp.se/henrikkniberg/

These two proved to be usefull to me.
gerhard said…
Not really about scrum, but for me a must read about making change happen:

"Fearless Change" by Mary Lynn Manns and Linda Rising.
Peter said…
Hi Jonas & Gerhard,

Thanks for the tips. Scrum and XP is great. It was probably the third Scrum book I read. I didn't list it (blush) because when I read it, it wasn't really a book, just a big PDF ;-). But you're right, it goes on the main page.

I heard about Fearless Change at the German Scrum gathering last Friday. It sounds really interesting and I plan to put it on my holiday reading list.

Cheers,
Peter
Peter said…
I really like the Shore & Warden book. It's a good basis for building up the engineering skills in the team. The concept of "Études" is really useful.

There are now a few books in German:

Scrum - Agiles Projektmanagement erfolgreich einsetzen by Roman Pichler

and

Scrum. Produkte zuverlässig und schnell entwickeln by Boris Gloger

Ken Schwaber's Agile Project Management with Scrum is also available in German.

Cheers,

Peter
Laszlo S said…
I would add these two:

(a) Corps Business: The 30 Management Principles of the U.S. Marines: http://www.amazon.com/Corps-Business-Management-Principles-Marines/dp/0066619793/ref=sr_1_1?ie=UTF8&s=books&qid=1237652286&sr=1-1

What's interesting about this one - is how much the culture of Scrum is described within.

(b) Slack by Tom Demarco is a must: http://www.amazon.com/Slack-Getting-Burnout-Busywork-Efficiency/dp/0767907698/ref=sr_1_1?ie=UTF8&s=books&qid=1237652397&sr=1-1

The first two pages of the book will bring to light a great concept
Anonymous said…
Thanks for the list. A good recent book is

The Elements of Scrum
Peter said…
I was not comfortable with this last comment. In general, I'm OK with anonymous comments, but this one gave no indication who or why the book was being recommended -- a bit close to spam for my comfort.

Only because the authors were part of the Bay Area Agile community did I decide to publish this comment.


When recommending a book (and I am really glad for good recommendations!), please do not recommend anonymously. Please do not recommend your own books or include partner IDs in your links.

Thanks!

Popular posts from this blog

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

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…

10 Warning Signs, that your team is not self-organizing

How do you know that self-organization is working? The Bern Chapter of Scrum Breakfast Club looked into this questions, and identified the following warning signs (which I have taken the liberty of translating).

The team reports to the Scrum Master at the Daily ScrumPeople wait for instructions from the Scrum MasterTeam members don't hold each other responsible [for their commitments]The same impediment comes up twice"That's the way it is" => resignation"I" instead of "We"Flip charts are lonelyCulture of conflict-avoidanceDecisions processes are unclear, nor are they discussedPersonal goals are more important than team goals
To this list I would add my a couple of my favorites:
you don't see a triangle on the task board (not working according prioritization of stories)after the daily Scrum, people return directly to their desks (no collaboration)there are a least as many stories in progress as team members (no pairing)
P.S. You can join the …