Скачать с ютуб What is Scope Creep? (4 tips and tactics to deal with Scope Creep) в хорошем качестве

What is Scope Creep? (4 tips and tactics to deal with Scope Creep)

What is Scope Creep and is it Necessarily Bad? In this video we will define what scope creep is, its causes, and how to control it. If you have been involved in projects, you might have heard the concept of Scope Creep. So, let’s understand what scope creep is. Timecodes: 0:00 - Intro 0:31 - Project Scope 1:25 - Scope Creep 2:05 - Causes of Scope Creep 2:50 - Avoiding Scope Creep 3:43 - Managing Scope Creep 3:43 - Managing Scope Creep Usually, both product and project scope are defined in the beginning of the project. However, during the implementation, stakeholders may try adding new requirements and features to the scope, which were not defined in the beginning. Sometimes, this can have a positive impact as it can help to make the final product better. However, from time to time this process becomes unmanageable which results in scope creep. Hence, Scope Creep refers to the uncontrolled process of change requests, additional features, and multiplied requirements that can arise from various demands of stakeholders as well as due to lack of communication and teamwork. Causes of Scope Creep The process of any project scope creep is quite disruptive, resulting in financial issues, extended deadlines, unsatisfied customers, and most importantly undesirable results. According to PMI's 2018 Pulse of the Profession report (https://www.pmi.org/learning/thought-..., more than half of completed Projects (52%) experienced scope creep. There are certain activities which usually lead to scope creep. The causes can be the following: - Weak scope definition - Lack of formal scope and requirements management - Inconsistent process for collecting product requirements - Lack of stakeholder involvement - Project length How to Avoid Scope Creep? - Make sure that you have a baselined Scope, and the terms on the Statement of Work (SOW) are clear and touch upon all the questions that may get misunderstood or disregarded in the process. - Identify rules, responsibilities, and expectations for both your team and the customer. Ensure the smooth process of the project by developing certain discipline in your cooperation. - Establish and follow proper scope change management processes. - Be transparent with your customer. Lay out the project scope and explain additional changes and modifications that can harm the final result. How to Manage Scope Creep? Prior to any change request, have a discussion with the customer and come to an agreement with a focus on the following 4 points: - Finances Once you receive additional requests, start calculating the costs separate from the original scope. Keep the costs separate to have a clear understanding of added or eliminated requirements in case of acceptance or rejection. - Impact Thoroughly analyze the consequences of change from each and every aspect of the project. It will be beneficial to create a separate checklist of all the expected results of scope change. - Communication Talk to the customer and help them analyze the end goal of their request. By doing so, you aim to minimize the change if possible, and consequently, minimize the risks associated with it. - Skipping Don’t ignore the risks and don’t multitask without a clear analysis of impact. Such a hasty approach can result in unexpected issues, which will accumulate due to the lack of a structured plan. Any change request resulting in scope creep should be controlled to some extent, otherwise the project will cause issues or eventually fail. So, always look for the best project management practices for avoiding and controlling scope creep in your projects. #ProjectManagement #ScopeCreep #ScopeCreepMeaning #ProjectScope #ScopeCreepManagement Connect us: LinkedIn:   / projectonomy   Facebook:   / projectonomy   Instagram:   / projectonomy   https://www.projectonomy.org/ Reference: Larson, R. & Larson, E. (2009). “Top five causes of scope creep and what to do about them” Paper presented at PMI® Global Congress 2009—North America, Orlando, FL. Newtown Square, PA: Project Management Institute. Abramovici, A. (2000). “Controlling scope creep” PM Network, 14(1), 44–48 Hunsberger, K. (2011). “Change is good” PM Network, 25(2), 48–53. Sliger, M. (2010). “Goodbye, scope creep—hello, agile!” Paper presented at PMI® Global Congress 2010—North America, Washington, DC. Newtown Square, PA: Project Management Institute.