Learn why weak scope definition happens in the first place, how it can cause scope creep, and what you can do to avoid derailing your project.
- What can derail your project faster than a runaway train?…Weak scope definition.…Weak scope definition occurs when the product, service,…or end result isn't described in enough detail…to determine the project's boundaries…and acceptance criteria.…In other words, if the requirements are not clearly defined,…then the scope can't be clearly defined.…For example, you're building a website…to capture leads for a consulting firm.…If you don't determine how the leads will be captured,…where the leads will be stored,…and what website integrations need to take place…to make this happen, there's a good chance you'll end up…with weak scope definition.…
There are some approaches that allow…for scope to be defined over time.…For example, agile.…However, you still need…to clarify your scope in enough detail…so you can properly manage your other project constraints.…Vague scope is problematic.…So, why does it happen in the first place?…Well, let's see.…One of the big reasons is…because you kick off your project…with a poorly defined statement of work, SOW.…
Released
8/21/2018- What is scope creep?
- Causes of scope creep
- Preventing scope creep
- Learning from a case study
Share this video
Embed this video
Video: Weak definition of scope