presentation

[lisahns]

Each team then has 12 minutes to present, with 5 additional minutes for questions. This means each person has about 3 minutes of speaking time.

Structure

• show your process (Why, What, How, Who, how did we split work?)
• Briefly demo your project and explain how it conforms to your brief i.e. the user stories and acceptance criteria
• Talk about each project role, and how you divided up the work.
• Show your project board and (from Week 2) report on estimated vs actual velocity
• Walk us through your code. Emphasise the things you learnt that were new to you, which the rest of your cohort could benefit from hearing about (something we're proud of, something we found hard/struggled with, anything we don't understand yet)
• Have the people who didn’t write a piece of code talk through it - this is a great way to demonstrate knowledge of learning and collaboration. Your whole team should be able to explain the whole codebase - in other words, everyone is responsible for writing code the whole team understands.
• Avoid talking through the project brief for a long time - each team has the same brief and your time will be better spent talking about what was unique about your presentation