Enter your mobile number below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
Getting the download link through email is temporarily not available. Please check back later.
To get the free app, enter your mobile phone number.
The Agile PMO: Leading the Effective, Value driven, Project Management Office (Volume 3) Paperback – February 27, 2013
Best Books of the Year So Far in fiction, nonfiction, mysteries, children's books, and much more.
Frequently Bought Together
Customers Who Bought This Item Also Bought
About the Author
If you buy a new print edition of this book (or purchased one in the past), you can buy the Kindle Edition for FREE. Print edition purchase must be sold by Amazon. Learn more.
For thousands of qualifying books, your past, present, and future print-edition purchases now lets you buy the Kindle edition for $2.99 or less. (Textbooks available for $9.99 or less.)
Top Customer Reviews
Let’s spare some time, with avoiding to reinvent the wheel.
Read this instead!
Thank you Michael for this really nice summary with lifelike examples.
I initially found such a forceful statement a little hard to swallow, but the book shows (using example scenarios drawn from the author's consulting experience) several ways how the PMO can fail if it chooses to focus its efforts in other directions.
If a PMO fails to establish the necessary authority and credibility with the Project Manager (PM) community at a sufficiently early stage, it becomes relegated to performing only supportive, administrative work. This is so time-consuming that there is no time to develop more useful services, value delivery is limited and the PMO will be cut as soon as funding decreases.
If a PMO focuses on methodology, the PMs may superficially complete templates and processes just to keep the PMO quiet, but the completed templates and processes may bear little relation to reality. Unless the methodology is focused tightly on improving project delivery, this type of PMO merely increases administrative burden on PMs without enhancing value. Again, the PMO will be cut as soon as funding decreases.
PMOs that function mainly as a home for PMs do little to create value (other than managing the PMs as resources). Despite this it can persist for a long time as business value is not even considered, and the PMO duties are usually carried out by fairly junior (cheap) people.Read more ›
The positives that I found include:
- "Kotter's 8-Step Change Model for Successful Transformational Change"
- Mission of the PMO
The section that describes guidelines for Agile PMO, while useful, was light on detail and did not cover the one scenario that I was looking for: small/mid-sized companies.
The author does not appear to have a strong grasp of agile principles. In one statement "Time boxing is great as long as you are flexible to changing the durations of the time box if necessary.", the author oversimplifies and does not explain what he meant by this, and why this is considered "best practice" in his mind. Changing the duration of the timebox can create chaos that disrupts the project. Also, there were only 10 pages or so of content related to "Agile PMO"; for a book that is titled "Agile PMO", I expected much more detailed coverage of the main subject matter.
Despite the good data I found reading this book, I found several grammatical and spelling errors, which are minor, but create a distraction. In the age of spell-checkers, I find it inexcusable for a book aimed at professionals (or any published book, for that matter) to have such blatant mistakes. Examples of such errors are below. There were also a number of mis-capitalized words such as "Methodology" in places that do not require it.
"personal" instead of "personnel"
"defiend" instead of "defend"
"you’re" instead of "your"
Due to the issues I mentioned, I give this book 3 stars overall. The content overall is ok but the errors detract from its value.
As other reviewers have also pointed out, not much depth and/or totally lacking in substance. I do begin to wonder where the 5- and 4-star reviews come from...
Moreso, the use of "Agile" in the title? There is nothing "Agile" about what he has written, if you take it from the perspective of the Agile Methodology/SCRUM, etc. After the last page, I felt like being a victim of a "bait-and-switch."
In summary, I was hoping to find some PMO-specific best practices, processes, methodologies, templates, etc. that I could leverage in my work. The title of the book is very misleading, and unfortunately came out feeling empty-handed...
Most Recent Customer Reviews
The author completely misses the core of Agile methodologies. The book presented a more structured and rigid project management style that still maintains an underlying waterfall... Read morePublished 6 months ago by Club Racer
I bought 70+ sheets of paper. The title misleads you into thinking you are buying a guide to blending traditional PMO management techniques with Agile processes. Nope. Read morePublished 13 months ago by R. E. Blitz
There are several spelling errors, repetition/recycling of points, and ideas that run counter to agile values and principles (ie. allocating individuals to projects vs. Read morePublished 16 months ago by Jon Jorgensen
This was my first introduction to Michael's work and it couldn't have come at a better time. I'm in the process of establishing a humble PMO within my region at work and struggling... Read morePublished 19 months ago by Chris C
A great wealth of knowledge for navigating projects in an agile and waterfall organization. Lots of good tips and explanation.Published 20 months ago by Sheila
Too basic and lacks practical advice. If you'd never run aPMO it may have something interesting to say.Published 20 months ago by Adam
Short and succinctly explains the need of Agile methodology in today's fast paced, ever changing scenarios. Relates to all industriesPublished 21 months ago by Bhanu Vadlakonda
This was a quick and simple read. I didn't find anything new and I was disappointed by the lack of grounded references or actual data to support some of the recommendations. Read morePublished 23 months ago by Phil Magrogan