Final Year Project Proposal Best Practices

Chapter 2 of 8 · 4 practices · 3 min · 3-question quiz

Scope the project to fit the calendar

Most final year projects that fail do not fail on ideas. They fail on scope. Fix the time you have and decide what fits inside it.

Start: Fix the deadline and let the scope flex

4 practices in this chapter

  1. 1Fix the deadline and let the scope flexYour deadlines are already fixed: the proposal defence, the mid evaluation and the final evaluation dates come from your department. What you control is how much you try to build. Basecamp's Shape Up…
  2. 2Define the smallest version you would be proud to demoBefore writing the proposal, describe the demo you want to give at the final evaluation in five or six steps. For example: A pharmacist signs in on a phone; They scan a medicine's barcode and enter…
  3. 3Write down what the project will not doA short out of scope list protects you all year. When an examiner asks "does it handle payments?" at the mid evaluation, you can point to the proposal that said, from the start, that payments were…
  4. 4Avoid scope that depends on data, hardware or people you do not controlMany projects stall for weeks waiting on something outside the team: a hospital that promised a dataset, a company API key that never arrives, sensors that have to be imported, a client who stops…

Check yourself on this chapter

3 questions, right here once you are signed in. Your progress is saved as you read.

Sign up for the quiz