Project Management

Please login or join to subscribe to this thread

The Relationship Between Scope and Risk in Project Management

linkedin twitter facebook   Risk Management   Scope Management  
avatar
Marco Riberio Brazil
Hello everyone.

It is my pleasure to begin a new topic to get value advices and exchange ideas with different minds.
I am gonna develop a final paper to get my certification in Project Management in an accredited university.
I would like to prepare a meaningful project highlighting the relationship between these two areas "Scope and Risk". In my point of view, these areas needs a special attention, of course, without forsake the others.

Please, feel free to share an interesting content to me and help me with this task.

Thank you so much.
Sort By:
< 1 2 >
avatar
PARAG KANDEKAR VP Operations| SoftNice Inc Allentown, Pa, United States
Marco: this subject can be discussed in many dimensions. I had some thoughts put in for Scope Cree/ Possible Risk and how one can act on it proactive to avoid the Scope Cree

https://www.linkedin.com/pulse/successful-...-parag-kandekar

I hope it helps you
avatar
PANKAJ KUMAR JOSHI General Manager| Transrail Lighting Limited Nainital, Uttrakhand, India
There is a risk if you define scope improperly. Sometime that risk may force you to change in scope of work. So it is interlinked because both are part of project management plan which links all plans as a input.
avatar
MAEN QADDOURAH Project Director| AJ SAUDI Jeddah, Saudi Arabia
Risk is to be studied with define scope.
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
Take into account that there are two types of scope: project scope and product scope. The second is defined from the first one. And that will determine the risk management approach.
avatar
Marco Riberio Brazil
HI Everyone.

Thanks for every comment upon my doubts. And Parag, thank you for sharing the content on linkedin.

Have a nice week.
avatar
Eduard Hernandez
Community Champion
Product Operations Program Manager Barcelona, Cataluña, Spain
High level risks may be already studied during Project Initiation (Project charter draft). More in depth risk analysis and management shall be carried out throughout the whole project life cycle, which includes frequently revisiting the risk register.
avatar
John Herman . Us, Aa, United States
On a traditional waterfall project, Scope is a constraint. Requirements are based on the Scope Statement for the project. Traditional projects require a Scope Management Plan. What are the steps that are to be followed when the scope is requested to change, either due to changing requirements, or risks or unknowns coming into view?

1. Not having a Scope Management Plan (Change Control Board) and Change Control process for the project would be a risk. As would be failing to follow that process.

2. In a nutshell, changing scope, scope creep, and failure to control scope is one of the major reasons that traditional projects go over budget or come in late. Look for supporting statistics on the web.

3. Agile processes avoid many of the scope issues because they are time constrained. Take a 4 week sprint and see what can be put into it. How much scope can fit into that 4 week time box?
avatar
Stéphane Parent Self Employed / Semi-retired| Leader Maker Prince Edward Island, Canada
You definitely want to do your risk and scope planning in parallel. As you add scope, you will be increasing risks. As you add work to mitigate and handle risks, you will be increasing your scope.
avatar
Brian Mukoyi Projects Manager| J R Goddard Contracting Bulawayo, Zimbabwe
By clearing defining and understanding your scope first, you can then articulate the risks associated with each activity defined in the scope. This can be done at the simultaneously but the most important thing is not to start altering the scope before you even define it. you will struggle to come up with the scope as you debate in your mind the risks and scope activities.

if scope is not clearly defined on the onset, there is a risk of scope creep, or "scope at large" where continuous revisions and additions are done resulting is cost escalations. Remember in projects costs are best controlled on the onset of the project with proper scope and design. Once the project is in progress the cost of altering the project is very high due to reworks and project risks are higher as changes may not be compatible with original design/scope.

In projects i have handled the risk register is implement right from the onset alongside the scope so that any risks arising are immediately brought to attention and risk reduction meeting held to see the cost impact and impact on the scope. its is not imaginable to just address the risks without keeping an eye on the scope.
avatar
Eduard Hernandez
Community Champion
Product Operations Program Manager Barcelona, Cataluña, Spain
Also note that Risk may be either a Threat or an Opportunity. I have noticed that risk is often used in a "negative" way, but it may very well turn into something positive (I see this all the time in my current organization)
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

The second day of a diet is always easier than the first. By the second day you're off it.

- Jackie Gleason

ADVERTISEMENT

Sponsors