Project 0 Expectations - 042020-dotnet-uta/curriculumCode GitHub Wiki

**### .NET Batch Expectations for project 0 presentation ** **### Wednesday, 03.24.20 **

  • 5 minutes for each presentation.
  • When it's your turn, you should be ready to go... Not "Oh, I forgot to start Visual Studio. Oh, where is my solution?”

Preparation

  • It is essential to practice and plan. It is obvious when someone has not practiced.
  • You don't have to show any code in the presentation, but if you have time for it, there's nothing wrong with it.

P0 functionality requirements

  • Anything you do not show or mention verbally will be assumed to be incomplete.
  • We don't have time to ask about every feature you forgot to mention.
  • You should prepare a demo workflow which:
    • Effectively and rapidly shows as much functionality as you can.
    • A good concluding sentence or two, so the presentation doesn't just trail off.
    • Ask for questions from the audience.
    • Batchmates are encouraged to ask questions.

Presentation

  • Begin with an introduction.
  • Speak with volume, energy, and confidence.
  • Give your name.
  • Use your webcam to start out.
  • Then move to screen-sharing for the demo.
  • Cover the business purpose of the app.
  • Cover the technologies used.
  • Demo the application.
    • Walk through its features.
    • Explaining features as you go.
    • There may not be time to show everything.
      • Show us most features.
      • Tell us about the rest.

Questions

  • Expect questions from QC and from the instructor(s).
  • Questions could be about the project's overall design.
  • How you used or didn’t use features of C# or SQL in p0.
  • Questions might also just be on week 2 content in general.

If you have not finished a majority of the requirements or are far from a working console application

  • The requirement is that you present what you have.
  • Talk about what you did accomplish.
  • Show what you did implement.
  • Talk about what your application plan was and what obstacles you ran into.
  • Talk specifically about what technologies you don’t fully understand and how you plan on resolving that difficulty.
  • You may be required to continue working and represent a more completed application at a later date.