The Software Project Manager's Bridge to Agility and over one million other books are available for Amazon Kindle. Learn more
CDN$ 32.75
  • List Price: CDN$ 51.99
  • You Save: CDN$ 19.24 (37%)
Usually ships within 3 to 6 weeks.
Ships from and sold by
Gift-wrap available.
Add to Cart
Have one to sell?
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See all 2 images

The Software Project Manager's Bridge to Agility Paperback – May 19 2008

Amazon Price New from Used from
Kindle Edition
"Please retry"
"Please retry"
CDN$ 32.75
CDN$ 32.75 CDN$ 39.01

There is a newer edition of this item:

The Software Project Manager's Bridge to Agility
Sign up to be notified when this item becomes available.

Join Amazon Student in Canada

Frequently Bought Together

The Software Project Manager's Bridge to Agility + The Art of Agile Development + Agile Project Management with Scrum
Price For All Three: CDN$ 98.92

Some of these items ship sooner than the others. Show details

  • Usually ships within 3 to 6 weeks.
    Ships from and sold by
    FREE Shipping. Details

  • The Art of Agile Development CDN$ 39.85

    In Stock.
    Ships from and sold by
    FREE Shipping. Details

  • Agile Project Management with Scrum CDN$ 26.32

    In Stock.
    Ships from and sold by
    FREE Shipping. Details

Customers Who Bought This Item Also Bought


Product Details

Inside This Book (Learn More)
Browse Sample Pages
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
Search inside this book:

What Other Items Do Customers Buy After Viewing This Item?

Customer Reviews

There are no customer reviews yet on
5 star
4 star
3 star
2 star
1 star

Most Helpful Customer Reviews on (beta) 18 reviews
24 of 26 people found the following review helpful
Agile and PMI are Compatible! July 21 2008
By J. Deville - Published on
Format: Paperback
Finally a book in the agile series that acknowledges agile and PMI are compatible. As a PMP and CSM, one of my long time frustrations has been too many agile authors create a stereotype of an overly bureaucrat waterfall process being managed by a dictator project manager. That may be a great way to sell their books, but their rejection of sound project management principles has been a disservice to the industry--the classic mistake of throwing out the baby with the bathwater.

As the title states, Sliger and Broderick sets out to bridge this divide and does a super job showing how agile management practices fit into the project management body of knowledge (PMBOK). They reinforce this message with extensive quotes from the PMBOK that explicitly address incremental and iterative development. I especially like their chapter summaries which compare and contrast project manager approaches to specific practices under a plan-driven and an agile project. One of their key messages is that project managers should allow the team to focus on the current iteration, allowing the project managers to focus on removing impediments to future work. This is sound advice no matter what development framework you are using.

Sliger and Broderick discussion on how agile is being extended to product and release planning and how it's adapting to interfacing with PMOs and non-agile teams is also very relevant. While agile purest reject such notions, these are issues that my clients are facing today. Sliger and Broderick succinctly summarize the current thinking on agile product and release planning and provide sound advice on adapting agile to meet these real-world needs.

One shortcoming in the book is that the authors imply that agile is the silver-bullet that should always be used. I wished they would have acknowledge that while agile methods are appropriate in many situations; plan-driven methods are the appropriate choice for other situations. (See Balancing Agility and Discipline: A Guide for the Perplexed by Barry Boehm and Richard Turner)

I highly recommend this book and will be adding to our seminars reference lists. It is especially useful to experienced project managers. As the product description (see above) states they often struggle while transitioning to agile. However, I don't think they are doubtful about the approach, but instead are confused by the hype they encounter. It will also be useful to agilest who starting to see through the hype in other books. Sliger and Broderick have cut through the hype and reinforce the point that effective project management principles still apply.
19 of 21 people found the following review helpful
Excellent advice for project managers making the change to agile June 17 2008
By Michael Cohn - Published on
Format: Paperback
This excellent book is targeted directly at Project Management Professionals (PMPs) but will be extremely beneficial to any project manager who is interested in agile development.

After three short chapters that introduce the general principles and activities of an agile software development project, the authors attack the meat of their subject. Each of the nine chapters of part two corresponds directly to one of the PMI's project management knowledge areas. Sliger and Broderick, each an experienced PMP, cover the changed responsibilities of the project manager transitioning to agile. A highlight of each chapter is the small table with columns for "I used to do this" and "Now I do this" that succinctly summarizes the often profound differences between traditional and agile project management.

This book is necessary reading for any project manager making the change to agile as well as for any ScrumMaster or agile coach working on a large projects. The book takes a giant stride toward dispelling the myth that the only role for project managers is to buy pizza and soda and get out of the way.
18 of 21 people found the following review helpful
An important book June 26 2008
By Bas Vodde - Published on
Format: Paperback
When I saw this book, I knew I had to read it, though I was very skeptical about it. Mapping the PMBOK practices to agile practices, is that the right thing to do? Why would you want to do that? What are the authors trying to prove?

The first chapter already helped me forward and removed some of my skepticism. This book is really what is says it is. It's a bridge for the traditional PMI project manager to understand what the difference is between traditional projects and agile projects and it's written in the language of a traditional project manager, the language of PMBOK. From that perspective, I've come to see this as an smart and important book thatm hopefully, will help lots of trainer project managers to understand what agile development is trying to do and why.

The book start with an introduction by Stacia, who describes her experience moving from a traditional environment to an agile environment and the difficulty she faced of changing the way of working she was used to. An excellent introduction that sets the tone of the rest of the book.

The rest of the book consists of 3 parts (plus some appendixes). The first part is the "standard introduction" part in which Agile development gets introduced, in which the first mapping of Agile development to the PMBOK is made and ends with a chapter on a generic agile lifecycle model, which is a guideline for the rest of the book.

The second part is the main part of the book and is structured around the different chapters of the PMBOK. This part actually maps to the PMBOK even on sub-chapter level, done quite well. Within each of the PMBOK chapters, the authors explain the problems the PMBOK tries to solve and how Agile practices solve the same problems, but in a different way. It summarizes this in every chapter with a comparison between traditional practices and Agile practices.

All the chapters seem to cover all the major agile project management practices. It starts with integration management and discussing how all things integrate together and how changes are managed. From there it moves to scope control and explains the differences between traditional WBS task breakdowns and working in a more feature-based way. Time management is next, covering the different planning cycles in the generic agile lifecycle framework (they introduced in Chapter 3). Next is cost management, and quality management. Chapter 9 covers human resource management and was a really nice chapter in which the authors describe well the difference between traditional project resourcing and trying to work with fixed teams that can actually learn new skills when needed. By this time, I felt the major topics had been covered, but there still needed to be communications management and Risk Management to make the mapping of the PMBOK complete. Here I felt the authors started repeating things that were covered earlier, but thats the risk when copying a fixed structure. The last chapter in the PMBOK mapping is procurement management and this chapter was a disappointment to me. The authors are of opinion that there is not much difference in this area, while personally I would not agree with that. Anyways.

The third part covers "the rest" with the main chapter probably be 13 which discusses about the changes in responsibilities between a traditional project manager and an "agile project manager". It describes in fairly much detail the changes in behavior and even tries to cover how to get past this difficult change and why people would want to go through the change (whats in it for them). Also chapter 15 answers one important question: What to do with the PMO. The authors suggest transforming it into an agile supporting organization which they still call "Agile PMO".

Chapter 16 (Selling benefits of Agile) and Chapter 17 (Common Mistakes) are useful chapters for people who are driving the change. It helps them answer some of the common questions and deal with some of the resistance. These chapters conclude the book.

In many areas, I'm still skeptical and do not always agree with the authors. I don't know if it's a good idea to change peoples and organizations role and still keep the old name, like "agile project manager" and "agile PMO". Scrum has solved this by simply calling it different: when the behavior is different then also call it different. Hence the ScrumMaster. Also, the authors strongly stick to the "project thinking" and seem at assume that thats a good way of a managing work. Same with contracts, the authors don't seem to think there will be much change in that area. The book has not convinced me the PMBOK is a good idea either, instead just confirmed my earlier criticism.

All tht said. Realistically, I understand that much of these aspect will not change or not quickly. So, this book introduces new concepts in a familiar language. I do think this will be needed and the authors done a great (perhaps the best possible) job in explaining agile concepts in traditional terms without losing it's meaning. This was the purpose of the book and it certainly succeeded in that.

For project managers looking at agile development, this book is an absolute must.
For agilists, the book is still a good and useful read! (also to understand traditional thinking)

Great work!
2 of 2 people found the following review helpful
Right on the Money...! Sept. 18 2009
By Amazon Customer - Published on
Format: Paperback
The authors have a comprehensive understanding of agile values, principles and practices and use this knowledge to provide an enlightening mapping to the PMBOK. This is a great "bridge" for PMI project managers wanting to transition to a more agile approach to software development projects.
A good book April 20 2014
By Eye Care For You - Published on
Format: Paperback Verified Purchase
I am learning a lot from this book. Got my PMP, but don't yet know about agile and the various "flavors" thereof. This book - even though not the newest -- is clear and concise and helping me learn a lot.