Pages

The book was sent for review, though I chose it amongst
others. The book piqued my interest because project management and agile are
considered contradictory ideas.

Published by Wiley, the book covers all aspects of agile and
how its different from the traditional waterfall.

What it covers is:

Provide a better understanding of what Agile is

Talk about the roles and how they are different
in Agile

Take the main discussion points from PMBOK and
explain how the same topic is looked in Agile

Dedicates a chapter to Agile tool- about Version
One specifically.

·The book is categorized into 4 main section:

§Fundamentals of Agile

§Agile Project Management

§Making Agile Work for a Business

§Enterprise Level Agile Frameworks

·Chapter 11 onwards, the discussion focuses more
on understanding Agile at deeper level and subsequently talk about Scaling
Agile, the concept of Agile Transformation and towards the end Frameworks

§SAFe

§DAD

§Managed Agile Development Framework

·The case studies brings in the how changes
happen in reality, the challenges and how to overcome them.

·The added benefit is the glossary of terms, so
someone very new to the concept of Agile doesn’t need to go through another
book or web, but can simply get all the terminologies from right here.

Total No of pages

399 (including index)

Who should read this
Book?

Project Managers moving into Agile- This book is caters to both
experienced and new project managers. Apart from explaining the concepts, the
book talks in details about all aspects of traditional project management and
its changing roles- from estimation to time management.

Sponsors for Agile Transformation- The case studies are a great way to
look into the challenges along with the scaling frameworks. While Agile tool
has been discussed here, they are a lot many options available in the market.

Managers interested in knowing the relevance of roles in Agile and how
they are supposed to be handled- With self organizing Agile teams, the concern
for management always lies in where does the existing roles fit in?

Why should you read this
book?

Anyone
interested to know where a project manager would fit in an Agile Organization
can read this book. I have to say, the book is for someone who’s new to Agile,
or has been working in traditional project management role for long.