PM Workflow News

The PMI affiliated website published Dan's article: Project Workflow Framework- An Error Free Project Management environment

Project (PMI) published the article "5 Types of Project Cost" with multiple quotations from our book.



The June/July issue of the PMI's Project Management Journal publication featured book's review by William Scally.The review spoke well of the book and complimented it. 

PMI members may see the review at

The PM Podcast


Cornelius Fichtner has published his new episode 316 of his popular podcasts, dedicated to our book. Dan Epstein and Rich Maltzman answer Cornelius' questions. You may access episode #316 here:


An advisory article Project Initiation Process, based on our book, has been published in February, March and April 2015 editions of PM World Journal  
Part 1 (February 2015)
Part 2 (March 2015)
Part 3 (April 2015) 


A new review by the well known Dutch blogger Henk-Jan van der Klis has been published in his Good Reads Magazine at:

The same review will be published later in his blog and the Dutch IPMA magazine.


On November 19, 2014, Dan presented PM Workflow at the PMI webinar: PM Workflow Framework: Defined and detailed.
The presentation describes PM Workflow Framework, on which the book is based. Along with the book features, the presentation describes how some of the most important features are implemented and explains why PM Workflow is today's project manager's Global Positioning System.

You may access the recorded presentation at:

However, you must install first a free tool Adobe Connect Pro on a desktop computer (Windows). It won't work on iPad or Android tablets.


Another book review was published at


Our book review has been published by site


A  featured article Project Estimating Process, based on our book, has been published by PM World Journal



The book review has been published in the PM World Journal.

Among other things, it says:

This is one of the few books that sensibly combines methodologies to produce a better approach. It is a welcome addition to the tools available for the practicing PMP.



The book has been mentioned by the PMO Expert Mel Bost in his blog. Mel writes: 

I would highly endorse my blog readers to consider Project Workflow Management as a reference text when defining a foundation project management process for your project group. I firmly believe this is the “finesse” we have been seeking individually in our project groups for many years.


The book is finally out! It is available on this website, Amazon, the Publisher and soon from the PMI Bookstore.


The Project Workflow Management Webinar was presented by Dan at the influential International Project Management Day Webina. The webinar recording is available at: or
the YouTube:

The presentation describes not only the book features, but also show how it is actually done.


The popular Management Issues website has published an article Getting to grips with virtual project management, featuring interview with Dan and Rich, authors of the Project Workflow Management book.


The leading British Project Management Today magazine follows us on Twitter.

07/12/2013 blog published analysis of differences between the small and large project scope changes and their implication on a project. The analysis quotes the Project Workflow Management book definition. Please note that the article provides the mirror address of our website. Also, a picture on the book cover has changed.

                                         Few excerpts from the post  

Small scope changes can be difficult to define as it really does depend on the type of project you are working on and the overall size of the work. For example, if you are working on a six-week project, then a change that takes two days is significant. But a change that takes two days on a project that lasts two years really isn’t that big of a deal.

There’s another way to look at this as well, which is set out by Dan Epstein and Rich Maltzman in their forthcoming book, Project Workflow Management. I’ve been lucky enough to see a copy of the book before its official release date and there is a section about scope change planning and what constitutes as small change which can help us answer the question of whether a new process is needed to handle smaller requests.

Epstein and Maltzman say that a small change:

  • Takes less than 8 hours of effort to complete
  • Adds no additional risks to the project
  • Impacts nothing else in the project
  • Impacts nothing else outside the project
  • Creates no new issues
  • Does not add any new stakeholders or business users.

That seems to me a pretty comprehensive list of everything that could potentially fall into the small change category.