Book Review: Agile Estimating and Planning

Authors:      Mike Cohn
Published:   2005
Publisher:   Prentice Hall
Paperback: 368 pages

This book is perhaps the most cited reference on estimation and planning by agilists. It is not just about “how to estimate and plan an Agile project”. The main objective  is to show how to bring in agility in the estimating and planning process itself.That’s the reason why the author, Mike Cohn has named this book “Agile Estimating and Planning” and not “Estimating and Planning Agile Projects”.
Reading Mike Cohn’s books is always a worthwhile investment of your time. The language he uses is simple and easy to understand for a non-native speaker of English. And this is very important since agile movement is rapidly spreading across non-English speaking countries. The techniques he recommends in his books are very practical and deliver results. And this book is no exception.
It consists of twenty-three  chapters organized in seven parts .Each chapter begins with a very pithy and apt quote about planning and ends with a summary of key points and with a set of discussion questions.
Part I The Problem and The Goal: The purpose of planning; why traditional approaches of estimating and planning lead to project failure; a high-level overview of agile approach towards estimation and planning.
Part II Estimating Size: Two measures of a feature size – story points and ideal time; techniques for estimating the size; advice on how to choose between estimating in story points and ideal time.
Part III Planning for Value: Four specific factors  to be considered when prioritizing user stories and themes; simple ways of modeling the financial return of a story or theme; two different approaches to assessing the desirability of stories and themes; advice on how to split large user stories or features into smaller ones.
Part IV Scheduling: Essential steps to planning a release and then to planning an iteration; selecting an appropriate iteration length; estimating velocity; planning projects with high schedule risks; estimating schedule much in advance with very little information; planning a project involving multiple teams.
Part V Tracking and Communicating: Monitoring release plan and iteration plan; various ways of communicating about estimates , plans and progress.
Part VI Why Agile Planning Works: Why agile estimating and planning are successful in achieving the purpose of the plan; guidelines for applying agile estimating and planning on  projects
Part VII The Case Study:  Main points of this book summarized in form of an extended case study about a fictitious company.
A MUST READ for all project managers from both Agile and Traditional projects !

Links :

Planning Quotes :
These pithy and apt quotes appear in the beginning of every chapter. They convey the essence of agile estimating and planning.

  • Planning is everything. Plans are nothing.”–Field Marshal Helmuth Graf von Moltke
  • “No plan survives contact with the enemy.”–Field Marshal Helmuth Graf von Moltke
  • “A good plan violently executed now is betterthan a perfect plan executed next week.”–General George S. Patton
  • “In a good shoe, I wear a size six, but a seven feels so good, I buy a size eight.” –Dolly Parton in Steel Magnolia
  • “To achieve great things, two things are needed: a plan, and not quite enough time.”–Leonard Bernstein
  • “Prediction is very difficult,especially about the future.”–Niels Bohr, Danish physicist
  • There’s no sense in being precise when you don’t even know what you’re talking about.”–John von Neumann
  • “If you tell people where to go, but not how to get there, you’ll be amazed at the results.”–General George S. Patton
  • “The indispensable first step to getting what you want is this:Decide what you want.”–Ben Stein
  • As a general rule of them,when benefits are not quantified at all,assume there aren’t any.”–Tom DeMarco and Timothy Lister
  • If you have a choice of two things and can’t decide, take both.”–Gregory Corso
  • “These days we do not program software module-by-module,we program software feature-by-feature.”–Mary Poppendieck
  • You improvise. You adapt. You overcome.”–Clint Eastwood in Heartbreak Ridge
  • “It is a capital mistake to theorize before one has data.”–Sherlock Holmes, Scandal In Bohemia
  • “Everything is vague to a degree you do not realize till you have tried to make it precise.”–Bertrand Russell
  • “It is better to be roughly right than precisely wrong.”–John Maynard Keynes
  • “To be uncertain is to be uncomfortable,but to be certain is to be ridiculous.”–Chinese proverb
  • “Do the planning, but throw out the plans.”–Mary Poppendieck
  • The stars might lie but the numbers never do.”–Mary-Chapin Carpenter, “I Feel Lucky
  • “Facts are better than dreams.”–Winston Churchill
  • “The more elaborate our means of communication,the less we communicate.”–Joseph Priestley
  • “If you want a guarantee, buy a toaster.”–Clint Eastwood in The Rookie
Posted in Book Review | Tagged , , , , | Leave a comment

Book Review: Agile Testing – A Practical Guide for Testers and Agile Teams

Authors: Lisa Crispin and Janet Gregory
Published: 2009
Publisher: Addison-Wesley Professional
Paperback: 576 pages

“What is in it for me in Agile?” ask testing professionals whom I have come across .  Though Agile methods advocate generalization over specialization in terms of programmers, testers etc., the  available agile literature tends to lean heavily towards programming as compared to testing.  For e.g.  two  Google searches which I conducted just few minutes yielded 25 million results for  “agile programming”  and just 2 million results for “agile testing”.  Therefore this  half-a-thousand page book is in my view is of prime importance in agile literature.

The book has 21 chapters grouped under six parts.
Part I Introduction: Provides an overview of agile testing and highlights how agile testing differs from testing in a traditional or “waterfall” lifecycle. The “whole team” approach i.e. the entire team being responsible for delivering high-quality software is explored. It also covers ten principles which an agile tester needs to follow to contribute effectively to the agile project.
Part II Organizational Challenges: This part deals with how to transition a traditional testing group to an agile testing group and the cultural challenges one may face during this transition.It also explores the ways to build an agile testing team.
Part III The Agile Testing Quadrants: The concept of Agile Testing Quadrants is introduced as a means to ensure that all types of testing are covered. Tests and their associated tools in each of these quadrants viz; Technology Facing /Supporting the Team,  Business Facing/Supporting the Team, Business Facing/Critique the Product and Technology Facing /Critique the Product are dealt with in separate chapters. There is also a chapter which describes a real project using tests from all four agile testing quadrants to overcome difficult testing challenges.
Part IV Automation: Test automation is a critical success factor for any agile implementation. This part deals with the necessity of automation and the challenges faced during the automation journey. It also explains how to develop an practical automation strategy based on agile values, principles,and practices to overcome these challenges.
Part V An Iteration in the Life of a Tester: In this part of the book, the authors describe how an agile tester typically works during the course of an iteration . They show how testers can -  get involved  during release or theme planning; help the team members when they start the iteration; work closely and incrementally with the programmers so that coding and testing are part of one integrated process of delivering software; help their teams stay on track and gauge progress; contribute during release, UAT, packaging, documentation, and training.
Part VI Summary: Discusses 7 Key success factors for agile testing  viz;
1. Use the whole-team approach.
2. Adopt an agile testing mind-set.
3. Automate regression testing.
4. Provide and obtain feedback.
5. Build a foundation of core practices.
6. Collaborate with customers.
7. Look at the big picture.

The authors have shared  over 100 real-life stories drawn from their rich professional experience which makes an interesting read.

A significant portion of this book discusses Agile in general. This will seem superfluous to readers who are already familiar with Agile and looking for deeper insights into testing techniques.

Overall a very significant contribution to agile literature which educates  programmers and testers as well as their managers on how to appreciate one another’s work and collaboratively work towards  integrating testing  activities as a part and parcel of an agile process.

Links:

  • Preface draft – This draft version of the  preface will give you an idea why the authors wrote the book and how use this book
  • Agile Testing Book Mind Map  showing how the book is organized, and what’s in it.
  • Chapters available online:

Chapter 1 – What is Agile Testing Anyway?
Chapter 21 – Key Success Factors for Agile Testing

[Please feel free to leave your comments below or bookmark/share this summary]

Posted in Book Review | Tagged , | Leave a comment

Book Review: Agile Coaching

Authors:      Rachel Davies, Liz Sedley
Published:   2009
Publisher:   The Pragmatic Bookshelf
Paperback: 240 pages

“Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime”,  says a Chinese proverb. Coaching is all about how to teach someone to fish.  An ideal coach is  a dispensable
(Yes you read it right ! It is “a dispensable” not “an indispensable”)  asset for an organization transitioning to agile or for an agile team having an urge to realize its full potential.

The coach who has become indispensable and keeps the team dependent on him has not done his job well.The ultimate yardstick of whether a coach has delivered results is whether the teams coached by her have progressed from “looking up to the coach” to “becoming a self-reliant team no longer dependent on the coach”.

In this book the authors have laid out a clear-cut road map for achieving this goal. Drawing from their own experiences as Agile coaches they provide practical advice, tips and techniques on how to coach the team on their journey towards self-reliance.

The book consists of four parts.
Part I Coaching Basics: The “whats and hows” of agile coaching; skills that help in working with people viz; listening , giving feedback, resolving issues/conflicts; leading change through effectively introducing and facilitating it; establishing conditions for teamwork to make the team jell.
Part II Planning as a Team: Taking the team beyond the standard format of daily standup meeting and helping them customize the meeting to suit their needs; how to introduce user stories to the team and avoid common pitfalls;helping the team strike the right balance between high-level and detailed planning; coaching the team to keep maintaining the visibility of items like iteration plans, retrospective actions, the state of the software etc.
Part III Caring About Quality: Helping the team to understand clearly exactly what “being done” means and how they can collaborate to make it happen; getting the team started on Test-driven development (TDD) and overcoming the barriers to implementing it; helping the team make the shift to Continuous Integration; making “clean code” a focus for the team and getting them started with Agile practices such as incremental design, collective code ownership, and pair programming.
Part IV Listening to Feedback: Helping the team run effective demos that feel useful and productive;the mechanics of retrospective design and techniques for running successful retrospectives; enhancing the coaching abilities.

At the end of every chapter  there is a list of possible hurdles which an agile coach may face and the tips to handle them. This in my opinion is one of the USPs of this book.

I liked the way the authors go beyond the cookie cutter approach of implementing agile practices (for e.g. daily standup meeting). They are also humble enough not to make tall claims about the effectiveness of their approach. They clearly say in the introduction that “Every person, project, team, and organization is different, so we can’t prescribe exactly what you should do in your situation. Instead, we give general guidelines to follow and ideas on different options you can apply. We can’t give you formulas to follow that will always work, because no two situations are alike. Throughout the book, We share stories about what we did in different circumstances, along with some more specific tips that you can use if your situation happens to match the one we describe. You’ll need to decide whether to apply our advice to your teams.”

This book is a must-have tool of an Agile Coach ! Highly recommended reading for every one in the agile team as well!

Links:
Contents and Extracts from the book : Visit this link to the publisher’s site and  read the full table of contents;  the foreword by Ron Jeffries, one of the founders of XP;
Chapter 1 Introduction (complete); Chapter 2 Working with People (extract); and
Chapter 5 Daily Standup (extract).

[Please leave your comments or share this summary if you like it]

Posted in Book Review | Tagged , , | 1 Comment

Book Review: Delivering E-Learning

Author: Kenneth Fee
Published: 2009
Publisher: Kogan Page
Buy from Flipkart

In this information age one cannot afford to keep away from the potential benefits which e-learning can deliver. However the subject of e-learning is still misunderstood and still accounts for only 10 % of all the training though its popularity seems to be on rise.
The author Kenneth Fee through this book presents a complete strategy of design, application and assessment of e-learning initiatives.
The focus of this book is on the process of learning rather than on the digital technologies that enable e-learning.
Quite a concise, well-written, introductory book on the e-learning strategy which also provides insights on how to manage e-learning effectively.
A MUST READ for every learning and development professional taking first steps towards e-learning.

For Chapter wise summary of the contents of this book visit Bookworm Reads: Delivering E-Learning.

Posted in Book Review | Tagged , , | Leave a comment

Book Review: High Performance Operations

Author: Hillel Glazer
Published: 2011
Publisher: FT Press
Buy from Flipkart
Acknowledgement :
I thank the author and the publisher for sending me a free pre-publication copy of this book and seeking an honest opinion of mine through this blog post. It has been a privilege to have read this book before it was released.

Book Review:
Many organizations treat compliance requirements like SOX, CMMI , FDA, ISO 9001, which are imposed on them either by clients or regulatory authorities as a necessary evil or a dead weight which needs to be endured as a hygiene factor to sustain their business.
But at the same time there are also some organizations (though in minority numbers) who have successfully leveraged the same compliance requirements to enhance their business performance and gained competitive advantage. The author Hillel Glazer has helped several such organizations to achieve this feat by creating process solutions that build compliance into the value stream using a system engineering approach.
This book provides the essence of this approach called Process Solutioneering (R) [ patent applied for by the author].

The author has primarily aimed this book at managers and executives. And it has found its mark right on ! The book can be a real eye-opener for them when they realize how compliance issues can be effectively leveraged to transform their operations to a high performing one provided they are willing to invest in terms of establishing appropriate leadership, culture, trust, autonomy, learning and communication system.
For read detailed review of this book visit Bookworm Reads:High Performance Operations.

Posted in Book Review | Tagged , | Leave a comment

Book Review: Understand Statistics

Author:     Alan Graham
Published: 2010
Publisher: Hodder Education

I am always on the lookout for good ideas to enhance my training and consulting approaches. Therefore I read from time to time, from a purely pedagogical perspective, introductory level books on the subjects which I am quite well versed with. The intention is to study the manner in which authors introduce the nuances of a subject to the novices. Statistics is one such subject.
While facilitating the implementation of high CMMI maturity level practices in companies I previously worked for, I felt that the project managers and senior level management need to have at least a basic knowledge of statistics to properly understand and use the metrics which such organizations churn out. I wish I had read this book then and recommended it to them. I must admit that even I learnt a few new things in this book.
This book is one of the best introduction to the principles of statistics I have ever read. Simple and easy to understand language; packed with practical examples and exercises and interesting stories revolving around statistics.
So if you want to learn statistics, start with this book !

For a more detailed summary of this book visit Bookworm Reads: Understand Statistics

Posted in Book Review | Tagged | Leave a comment

Book Review: User Stories Applied: For Agile Software Development

Author: Mike Cohn
Published: 2004
Publisher: Addison-Wesley Professional

The entire business of software development (for that matter any product development) starts with a user need (whether inherent or created by innovative marketing !) which gets expressed in form of documented requirements. This holds true for both the traditional and the agile methods. But the difference lies in the way these requirements get documented. The traditional methods like waterfall method recommend a Big Requirements Up-Front (BRUF) approach where the entire set of requirements are documented by the analysts and passed on like a relay race baton to the development team. The agile methods zealously espouse the cause of short and “just enough” documentation of requirements which encourages conversation between the developers and the product stakeholders. User Stories , the subject of this book, are one such way of documenting requirements, highly recommended by most of the agilists.
Mike Cohn, the author of this book, is an oft cited authority whenever the topic of user stories arises in Agile related discussions. Here he provides a very practical approach towards effectively using User Stories in the software development projects.
If you want to know anything about the User Stories, this is the GO-TO book !

Read the book summary at Bookworm Reads:User Stories Applied

Posted in Book Review | Tagged , | 1 Comment

Book Review: Agile Retrospectives – Making Good Teams Great

Author: Esther Derby, Diane Larsen
Published: 2006
Publisher: The Pragmatic Bookshelf

Agile Principle # 12 – At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. The “reflection” part typically happens in a retrospective meeting after every iteration . Unless retrospective meetings are well planned, well facilitated and result in clear cut action items for the team to “tune and adjust”, they will not be of much value. But a successful retrospective will enable a team to improve their capability and productivity and increase their capacity to deliver a high quality product. Moreover it will result in better teamwork and job satisfaction.
And how to get these benefits out of retrospectives is what exactly the authors of this book have attempted to teach us through this book.
A useful and handy book which each team should have !

More detailed summary at Bookworm Reads:Agile Retrospectives – Making Good Teams Great.

Posted in Book Review | Tagged | Leave a comment

Book Review: Individuals and Interactions – An Agile Guide

Authors: Ken Howard and Barry Rogers
Published: 2011
Publisher: Addison-Wesley Professional
Buy from Flipkart
“Individual and Interactions over Processes and Tools”, thus begins the Agile Manifesto. It is obvious that the authors of the Agile Manifesto considered “Individual and Interactions” of foremost importance for any Agile implementation. Ironically even after ten years, the Agile literature is flooded with books on “Processes and Tools” but hardly any on individual behaviors and team interactions in context of Agile projects. Therefore this book is a very welcome addition to the Agile literature.
People issues are the most challenging ones in any agile project. This book is an excellent guide for Team members, ScrumMasters, Product Owners, Management, Consultants, Trainers to understand these issues and successfully address them. A Must-Read !

Read the book summary at Bookworm Reads: Individuals and Interactions: An Agile Guide

Posted in Book Review | Tagged , | Leave a comment

Book Review: Agile Product Management with Scrum – Creating Products that Customers Love

Author: Roman Pichler
Published: 2010
Publisher: Addison-Wesley Professional

A Product Owner (PO) is one of the key roles in Scrum framework. POs are responsible for maximizing the value of the product being developed and the work of the development team. Clearly the role of a PO is a very challenging one. This book is a much needed guide for the POs to excel in their roles and to ensure the launch of products that the customers will be delighted to have.
There may not be much new in this book for a highly experienced and effective Product Owner who may be already aware of and even following many of the useful techniques discussed in this book.
But for a novice Product Owner, other members of the Scrum Team, and the management of an organization taking baby steps towards implementation of Scrum, this book should be a mandatory read.

Read the Book Summary at Bookworm Reads: Agile Product Management with Scrum

Posted in Book Review | Tagged , , | Leave a comment