Changes Regarding Preliminary Scope Statement and Collect Requirements at PMBOK 4th Edition

In this podcast, Ricardo talks about the changes related to the Integration and Scope Management at the PMBOK Guide 4th edition. He discusses the removal of the process related to the preliminary scope statement and the insertion of the process to collect requirements as the first process of scope management. Moreover, Ricardo analyses the reasons, the implications and the benefits of the change.

Download (7 MB)

Episode transcript

The transcript is generated automatically by Podscribe, Sonix, Otter and other electronic transcription services.

Hello. Oh, everybody. And welcome to the five minutes BM podcast today. I'd like to discuss one change that happens from the third edition to the fourth edition of the PMBOK Guide regarding the Scope Statement. If we look back to the third edition of the PMBOK Guide we saw that the process Preliminary Scope Statement was removed from the Integration process, and this raises a lot of questions. I receive several emails talking to you. What happened with this Preliminary Scope Statement and let's return back to the third edition and let discuss why this process was included.

There's the process was included to have some kind of work Regarding Integration and Scope in the initiating process. So just after developing the project charter, we needed at that time to develop some top-level Scope Statement to help us to understand what is the project about. And now we don't have this process anymore. And for me, this is a very good thing that happened from the third edition to the fourth edition, because now we took out the Preliminary Scope Statement for me, this word is it's not clear for me because I don't see value in some kind of document that is not the final document.

It's like a draft. And what happened now, the PMBOK four Edition built a new process in the Scope called Collect Requirements is the first process in the Scope Management and why this process is so critical because the do you tend to of developed the Preliminary Scope Statement on the third edition is to say, to develop the Requirements for my project. And now we have a specific process to do that in this process that is now in the right place.

This is my personal opinion, the right place on this Scope and it's the first one. So Collect, Requirements what we'll need to do, will need to talk to people. Interview people, use techniques of the information, gathering Delphi analysis, SWOT analysis, to understand what is this project is about, to understand all the food show. Now Requirements place the ability of all Requirements and to create all the documentation and with this documentation then will be great.

The Scope Statement but not the playlist Menari Scope Statement but the final Scope Statement is so interesting because We Collect Requirements and this will be an issue put to define the Scope. So let's return back and let's compare the two with the president in the past first process for 0.1 Integration is to develop the project charter. After that developed the project Preliminary Scope Statement and then developed the final Scope Statement.

Now we took out to the second we put Collect requirements. So we developed the project charter, then we've revisited and a Gator, all the information about Requirements and then we prepare the Scope Statement. So it's much more clear, it's much more defined. And to finish this podcast, I'd like only to remember two, all of you, again, that the 42 processes in the PMBOK Guide for Edition are the standard and not the methodology.

You should not follow this, buy the book. It doesn't mean that if you do only 41 processes, you are not using the PMBOK to help. You know, the intent of the Guide is to help product managers to deliver better results. And if you use, you lose the 42, it's great. If you use 30, and if you mix this with audit kind of thing, standards are a methodology. Everything that you do to improve your project success rate 10, you will be using a good project management process.

And the idea of this Collect Requirements before the fight, the Scope Statement the find a Scope is to help everybody to understand that first, we need to talk to the stakeholders and we need to own understand what they needed for the project to build the scope Statement and the Preliminary scopes Statement does not exist any more. It doesn't mean that the Scope became less relevant. Noe, the scope now became much more relevant, splitting this and putting this in the right place.

I hope you enjoy this podcast and see you next week with another five minutes BM. Podcast. Bye. Bye.

Menu

Resources & Insights

Products & Services

More Resources & Insights

Ricardo Vargas

Podcasts

Changes Regarding Preliminary Scope Statement and Collect Requirements at PMBOK 4th Edition

Search in Podcasts

Latest podcast episodes

Book recommendations