diff --git a/contributions/presentation/week3/streuli-mnem/README.md b/contributions/presentation/week3/streuli-mnem/README.md
new file mode 100644
index 0000000000..7a63f121de
--- /dev/null
+++ b/contributions/presentation/week3/streuli-mnem/README.md
@@ -0,0 +1,26 @@
+# Assignment Proposal
+
+## Title
+
+Flyway: Version Control for Databases
+
+## Names and KTH ID
+
+- David Streuli (streuli@kth.se)
+- Muhammadsodiq Nematjanov (mnem@kth.se)
+
+## Deadline
+
+- Week 3
+
+## Category
+
+- Presentation
+
+## Description
+
+In this presentation, we will delve into the critical role of automated database version control within the framework of Continuous Deployment. We'll begin by outlining the necessity for managing database schema changes seamlessly alongside application updates to ensure system integrity and performance. We will examine the popular tool Flyway, a popular tool for database versioning. Flyway has been in continual development since 2010 and remains to be the industry standard for database migration and supports over 50 different database platforms. We will discuss how to integrate Flyway into the CI/CD pipeline, ensuring that every deployment reflects both application and database state changes accurately. This presentation will highlight the importance of database versioning to ensure consistency throughout different environments. 
+
+**Relevance**
+
+Database versioning is essential in CD as it ensures that database schema changes are consistently and accurately applied across all environments. This automation minimizes downtime and reduces the risk of errors during deployments and thus supports the continuous releasing in typical CD practices.