Defining Project Scope

Scope is one of the most important project management decisions. A learner may be tempted to build a large system with many forms and complex dashboards. A smaller project with clear logic, good documentation, and reliable scripts is usually stronger. The project should have enough complexity to demonstrate learning, but not so much that quality suffers. A good final project scope includes: 1. One concise study scenario. 2. Three to six CRFs or data domains. 3. Fifteen to forty key variables. 4. At least five validation or data quality rules. 5. At least one derived variable. 6. At least one query listing. 7. At least two descriptive tables. 8. At least one visualization. 9. A short reproducible report. 10. A documentation package.

The project should also include explicit exclusions. For example, the learner may state that the project does not implement randomization, laboratory API integration, or full safety reporting because those are outside the capstone scope. Defining exclusions is a sign of professional planning, not weakness.