Final Demo and Project Summary

Project Summary The team has gone through the project lifecycle and evaluated the progress. You have presented your thoughts on what should have been done differently, what decision should have been made at which stages, what went well, what kind of changes were made and what triggered those changes. There is a customer's opinion present about what are his/her plans with the project after the course finishes. Project summary has to be present in the course Wiki in the morning of the Demo Day.

In order to benefit from the deliverable, take time to analyse the project among the whole team, it will be a good exercise for you to look back to the last three months and try to understand what you have learned along the way.

Final Demo During your final demo, you should:

• Explain the purpose of the solution: what is the problem, what is your solution and who is going to be the end user.
• Demonstrate the usage of the working application (preferably live, but a pre-recorded video is allowed as a "backup" option or when a live demo is impractical)
• Demonstrate the use case(s) which represent some part(s) of the core functionality in action
• Manage to pull off an engaging demo. Remember - the key point is to tell a story instead of demonstrating the functionality randomly.

The demo should take no more than 5 minutes (plus time for questions).