Skip to Content

Scope

When you say "scope," are you referring to the product scope (the Website), project scope (work to produce the product), or operational scope (work done after the Website launches)? One of the most common issues that arise in projects is scope creep.

Defining Scope

The comment "that is out of scope" can come up a lot in projects where products are being designed and developed. Imagine this scenario:

You define your product scope to be a site with X number of features. You define your project scope to include the assembly of pre-existing modules. What happens when one or more of your product requirements can't be implemented within the boundaries of the project scope? Meaning, what happens if custom coding is required? Is that custom code outside your project scope even though your product scope includes that feature?

This scenario is not limited to the world of open source systems but it can happen. The opportunity you have with an open source community like Drupal is, you can search the modules that are there, get an idea of what is possible before you define your product scope.

Scope Impacts

There are other scope related challenges that might be fostered by the nature of an open source application, given the shear number of modules to choose from. Here are two scope related challenges to consider.

Product Scope Creep

Drupal has thousands of functions and features you can choose to add to your site. Having so much flexibility at your fingers tips can be overwhelming and hard to ignore. If not ignored, this type of flexibility can cause scope creep. It can happen very quickly so before adding a module that is not part of the plan, you will want to ask yourself “Is this cool to add or is it needed to meet the requirements already set forth?”

Project and Operations Scope Creep

Content management systems that make it easy to create your own functions and features can lead you down the path of needing to maintain one or more custom modules. As the system goes through updates, you will need to test and potentially update your custom modules in order to update/upgrade the system. This affects the project scope when system updates occur during site production. It also affects operational scope, maintaining the site in future. Do you have the resources to sustain development support after the site is launched?

Conclusion

The point is, keep your eye on the target. Try not to get distracted with functions and features that are just cool but can carry a price later.