Earlier this year, Dave Bouwman and I took a course in Agile Estimating & Planning taught by Mike Cohn.  It was an excellent course, but I felt I needed a deeper understanding of the subject matter.  Fortunately, Mike wrote a book about the same subject (Agile Estimating & Planning) and it is an excellent primer and team reference for estimating and planning using agile practices (as the title obviously infers).

Who should read this book?  Everyone on your team should read this book. It is relevant to your developers, your ScrumMasters, your managers, and even your sales team.  If your team hasn't read this book, or at least parts of it, give it to them today.

What’s inside?  The book is broken into 7 sections. Mike starts off with a good overview of the purpose of planning, as well as an excellent account of why traditional planning methods (AKA waterfall) fail.  The solution: an Agile approach to estimating and planning. 

The next section, Estimating Size, walks us through the complex issue of how to estimate using size instead of the typical duration.  This is a critical distinction in the way Agile teams estimate their projects and Mike does a great job of walking us through the process; it includes specific techniques for estimating, as well as the distinction between estimating in story points and ideal days, and how to choose between the two.

The third part of the book is about planning for value.  This includes several chapters on how to prioritize your backlog items.  Mike describes specific prioritization considerations including thematic prioritization, financial prioritization, and desirability prioritization.  This section of the book also covers how and when to split user stories as they rise to the top of the prioritized backlog.

Section four covers the topic of scheduling.  In this section, Mike presents the essentials of release and iteration planning.  In addition, he details how to derive your team's velocity from metrics gathered on historical data.  If you don't have historical data, don't despair, after 3 or 4 iterations, you'll have a good idea of what your velocity is.  Other topics covered here include how to buffer your estimates by either feature, schedule, or a combination, as well as planning multiple-team projects.

The fifth part of the book is about how to monitor both your release and iteration plans.  It covers some of the basics such as burn-down charts, parking lot charts, iteration task boards, and how to track effort expended.

The last two sections are kind a "Why Agile Planning Works" conclusion.  It includes reasons why agile planning works as well as a case study of the planning and estimating process.

Why it’s on my bookshelf?  Since our team started using Agile practices and Scrum, one of the key questions that consistently arises in any discussion we have with our managers and other development teams is "How do you guys estimate and plan?".  Or more precisely, "Do you guys plan?".  Yes, we definitely plan.  And this book is kind of the how-to for agile estimating and planning techniques.  Our team has used many of the techniques described by Mike in this book with great success.  As a project manager, I found this book absolutely priceless.  It allowed to me to understand ways to gather meaningful (as opposed to useless) project metrics.  As we move forward developing new business using agile practices, I have gained a great deal of confidence in our ability to more accurately (not precisely) estimate our efforts.  And finally, I have referred several people to this book whenever we get the questions mentioned above.  I recently gave a presentation at a company offsite where I knew the planning question would come up. Using information gained from this book, I was easily able to show the different horizons that our agile team plans at, from the detailed iteration level all the way up to the overarching strategic level. 

If you're practicing Scrum, or any other agile methodology, you owe it to yourself and your team to check out this book.  If you're about to start practicing Scrum, do yourself a big favor and read this book first.  It'll save you a lot of trouble down the road if you start using the techniques described in this book right from the start.

Here’s the skinny on the book:

Title: Agile Estimating and Planning

Author: Mike Cohn

Year: 2005

Publisher: Prentice Hall PTR

Length: 368 pages

ISBN-10: 0131479415

ISBN-13: 978-0131479418

List price: $49.99

In just about every article I’ve posted so far, I’ve most likely mentioned the book Agile Project Management with Scrum by Ken Schwaber.  You're probably wondering why I keep referring to it.  No, I don't get $1.00 each time I cite the book (although, that would be nice).  So I figured, it’s probably about I time I wrote a quick post about this book.

Who should read this book?  Anyone interested in learning the basics of Scrum.  No need to be a project manager type.  This book is for everyone.  The managers, the developers, the DBA’s, the analysts, the clients…anyone who works on any type of project can benefit from this book.

What’s inside?  Ken starts off by explaining the basics of Scrum.  In the first 14 pages, he covers the science of Scrum and provides a great overview of the entire process.  If you read nothing else, read these 14 pages.  The remainder of the book goes into detail about the various Scrum roles, planning a Scrum project, project reporting, and scaling projects with Scrum.  Most of the book is filled with case studies that clearly illustrate the concepts Ken is relating about Scrum.  The book concludes with 6 pages of the essential rules of Scrum.

Why it’s on my bookshelf?  This is the book that made it all click for me.  In my eyes, this is the bible of Scrum.  All of the basics are covered in a very easy to understand way.  As a ScrumMaster, any time I feel our Scrum process is slipping a little, I open the book, read a few pages, reflect on our Team’s current process, and use the guidance from this book to help make the necessary course corrections to get back on track.  The book is filled with numerous case studies that provide great insight into situations that real world ScrumMasters, Scrum Teams, Product Owners, and their organizations frequently run into.  I have probably read this book at least six times now as we have started on our Team’s Scrum journey.  As our Scrum process matures and I reflect on the case studies in this book, I can easily recognize things that our Team, our Product Owner, our organization, and I (the ScrumMaster) have done, both good and bad.  I have gained a lot of confidence by coming to realize that we're not the only Team who has experienced the ups and downs that Ken described in the case studies.  Overall, this is a great read for anyone who is interested in producing high quality, valuable products faster.  If you’re considering using Scrum on your projects and you haven’t read Agile Project Management with Scrum, what are you waiting for...run out now and get this book!!!  (Or just order it from Amazon)...

Like most people in GIS and software development, I have an extensive book collection that I rely upon for ideas and information about varous topics.  From time to time, I'll post information about books I'm currently using in the Bookshelf Category.  I'll provide a brief summary of the book and sometimes a short review.  Hope you find some of these books helpful.