Demo day schedule

[luccalb]

User Story

1. As an AMOS project team
2. we want to deliver a well prepared and awesome demo day
3. so that we can bring the project to a successfull end and get a good grade!

Additional context

You can find the schedule here (Slide 7) https://github.com/dirkriehle/amos-course/blob/main/Generated/Lecture%20slides/AMOS%20C01%20-%20Demo%20Day%20Preparation.pdf

Opening

• For the opening 1 presenter shows 1 summary slide and introduces the project in 1 minute
• After the opening the audience will decide which break out room to join

Slot	Duration	Presenter
0	1 min	PO?

Demos

• There are 3 demo slots
• For each slot there should be two presenters
  • Software Demo: Runs the jupyter notebook
    • Make sure the code runs on your local machine, before the demo day
  • Explainer: Explains the story/components/data
  • It's up to you who shows the slides
• One demo slot should be 20 minutes long
  • 10 Minutes Demo/Presentation
  • 10 Minutes for Questions/Discussions

Slot	Duration	Software Demo	Explanation/Talking
1	20 min	Timm	Lucca
2	20 min	Felipe	Mert
3	20 min	Dominik	Minh

Demo structure

1. Show the slides, general introduction to RTDIP, tell the story of Alex the Data Scientist https://docs.google.com/presentation/d/1Qvavu7woQj1AIFUuCCY5IHdXFFgsk0CGJ4-JZhz3gdM/edit#slide=id.p
2. Show the Documentation using mkdocs serve or the github pages https://amosproj.github.io/amos2024ws01-rtdip-data-quality-checker/sdk/code-reference/pipelines/data_quality/monitoring/spark/check_value_ranges/
3. Go through and explain the components in the jupyter notebook https://github.com/amosproj/amos2024ws01-rtdip-data-quality-checker/blob/feature/096_rtdip_demo_pipeline/notebook/pipeline_showcase.ipynb

Acceptance Criteria

• The schedule above is filled out
• Everyone on the team knows who will present what and when during the demo day

Definition of Done

• Test cases have been created and are running successfully
• Documentation for the new component was added
• Github Actions are running without errors

[luccalb]

Idea for the demo by Shell: Also show and point out the comprehensive documentation using mkdocs serve

[luccalb]

Link to the demo slide deck: https://docs.google.com/presentation/d/1Qvavu7woQj1AIFUuCCY5IHdXFFgsk0CGJ4-JZhz3gdM/edit#slide=id.p