I would like to offer an answer to another question:
How can I quantify progress in a programming project?
I prefer flexible methodologies, so I would introduce a burning schedule that takes into account the total number of user stories / maps / tasks, complexity / estimated time and displays it against the rest.
I think you need to do something simpler, but I expect simpler:
- Start by breaking the entire project into units - tasks / errors / areas of functionality
- Evaluate the amount of effort required for each and consider risk + complexity
- For each unit, evaluate the amount it has completed - units must be small enough to be completed within a day or two maximum.
- From this you can build statistics
I expect that just a project planning plan will be enough to improve your position with your teacher, as it shows maturity in understanding that a project is more than just code.
source share