Removed mklink for git

_-Review/user-story.md

@@ -0,0 +1,29 @@
+---
+created: 2024-09-12T21:43:16.244Z
+type: note
+updated: 2024-09-13T15:47:59.137Z
+---
+
+# user-story
+
+- [confluencewikiprod](https://confluencewikiprod.intra.infineon.com/display/FIOT/OES+Scrum+Master+Sync+Meeting)
+
+## User Story Description
+
+- A user story is a description of a desired function (functional requirement) from the user's perspective: 
+As a ```<role/person>``` I want to ```<function>``` so that ```<benefit>```. One user story per workflow step. 
+
+## User Acceptance Criteria
+
+-  Describe test flow from user-perspective (expected result). Describe good cases, but also exceptional scenarios and unchanged scenarios. Describe Non-functional criteria's (e.g. amount of data; performance). 
+
+## Important info 	
+
+- Can the team members create the User story? 
+ 1. PO prepares the User Story and Team members create the tasks. PO will write what he wants from the tam. The team figures out how to implement/deliver what PO wants.
+ 1. However, anyone from team can create the user story.  PO still needs to govern the user story and backlog.
+ 1. The important thing is to have the description and acceptance criteria. 
+ 1. The assignees of the User story have to be team members , but if PO is doing the User Story, the assignee name can be PO. 
+ 1. The team themselves have to create the tasks. PO cannot create the tasks and assign the team members. 
+
+- [writing-and-splitting-stories](https://confluencewikiprod.intra.infineon.com/download/attachments/1587143335/01%20Writing%20and%20Splitting%20Stories%20Guide%20%28V5.0%29.pdf?version=1&modificationDate=1709810911000&api=v2)