A capstone project plan that connects the build, report, and presentation
A capstone is easier to manage when the practical output and academic argument develop together. Evidence from design decisions, tests, and setbacks should feed the report instead of being reconstructed at the end.
Define the minimum defensible project
Translate the rubric into outcomes the marker can observe. Separate essential functions and evidence from optional improvements. This protects the project when research, access, procurement, or implementation takes longer than expected.
Write one sentence that states the problem, intended user or context, proposed response, and how success will be evaluated.
Build milestones around evidence
A milestone should produce something reviewable: a requirements document, literature map, prototype, dataset, test result, chapter draft, or presentation rehearsal. Dates alone do not show whether the project is moving.
- Scope approved
- Evidence reviewed
- Design recorded
- Prototype tested
- Results analysed
- Report revised
- Presentation rehearsed
Keep a decision log
Record important choices, alternatives considered, evidence used, and consequences. The log preserves reasoning that can later support the methodology, design, evaluation, and limitations sections.
Document failures as evidence. A test that exposes a limitation can strengthen the academic evaluation when it leads to a reasoned improvement or a clear boundary on the final claim.
Prepare the defense while building
Keep a short answer to four questions: What problem did you address, why did you choose this approach, what evidence shows the result, and what would you change next? Update the answers at each milestone so the final presentation is a synthesis rather than a memory test.
Questions students ask next.
How do I narrow a capstone topic?+
Limit the user group, setting, core function, data source, or evaluation target. Prefer one defensible result over several incomplete features.
What belongs in a capstone project report?+
Follow the rubric. Common elements include the problem, evidence or literature, requirements, method, design decisions, implementation, evaluation, limitations, and recommendations.