It’s time to continue working on self-improvement. This fourth article in a series exploring A Guide to the Project Management Body of Knowledge (PMBOK Guide)—Fifth Edition through a lighthearted comparison to personal fitness improvement explores the Project Scope Management knowledge area.
When should scope change?
Connect with Influencers
Customer-facing project teams are the face of the organization, and that has to mean something. We need to help project teams understand the ground rules that they are operating within--and what is expected of them.
The most significant challenge for any project manager is when projects shift modes. The shift from startup to execution, and the shift from execution to closeout, requires a change in mindset. Each shift needs the PM to adjust their focus and emphasis--and a corresponding change to how they deal with people.
In the real world, scope changes can be expected during the life cycles of most projects. Scope changes implemented once work has begun will have a greater effect on the project schedule and cost than changes implemented during the project initiation or planning phase; therefore, it is imperative that the project scope be well defined before the project work begins. The purpose of this paper is to help the reader better define project scope, give examples of some of the difficulties of managing project scope and the consequences and recommendations for dealing with those difficulties.
Managing requirements successfully does not happen by accident. The project manager in charge should have a solid plan for making sure the requirements provide a solid basis for the rest of the project.
Organizations are becoming increasingly strategic in the way that projects are reviewed and approved. The decisions that we make around requirements are some of the most fundamental on a project, but do we consider the right factors when making those decisions?
The efficient delivery of construction projects will be greatly enhanced if project managers focus their efforts on developing measures for identifying, monitoring, and managing scope creep in projects of any size. This article seeks to provide answers to the following questions: What is scope creep? When does it happen (identifying? Why does it happen (monitoring)? And, how can it be prevented from happening (managing)?
For agile projects, redefining scope isn't such a creepy thing. This article
You won’t get the right benefits unless you start with the right scope. As project managers are increasingly asked to become involved in the business side of project execution, many elements they previously didn't have to worry about are now becoming relevant.
Are you making the same mistakes over and over again? Managing the requirements well is critical for project success. Do this, and you will succeed. Fail to do this, and you'll suffer the consequences.
Why is change control so important? With everything a project manager is responsible for, why so much concern over it? What does it really mean, and how do we perform it?