|
|
## User Story: Product Owner (Study Program)
|
|
|
|
|
|
**What is this user story?**
|
|
|
|
|
|
This user story describes the role and responsibilities of the Product Owner for the WMW projects (Bachelor or Master). The Product Owner has overall responsibility for the smooth running of the study program. This includes planning and conducting sprint reviews, creating and maintaining a clear Nextcloud structure for student submissions, correcting those submissions and providing feedback, and monitoring submissions to ensure they are on time. The Product Owner also communicates regularly with students using various channels, including Webex and WhatsApp, to share important information and announcements. Finally, the Product Owner plans and organizes events for students, collaborating with the Student Council (StuRa) and the Student Convention (StuK) to ensure successful execution.
|
|
|
|
|
|
**What stage has the project reached??**
|
|
|
|
|
|
The role of the Product Owner is established and the tasks are defined. The processes for sprint reviews, submission management, and communication are implemented. Collaboration with StuRa and StuK is established.
|
|
|
|
|
|
**Description of the work in the semester:**
|
|
|
|
|
|
The Product Owner acts as a liaison between students and professors (customers). They have defined tasks such as creating posters, conducting sprint reviews, maintaining wikis, and managing weekly reports. The Product Owner works continuously on organizing and executing teaching activities, planning and conducting events, and communicating with students. Throughout the semester, they perform the defined tasks and optimize the processes.
|
|
|
|
|
|
**Possible obstacles and how to avoid them:**
|
|
|
|
|
|
* **Communication problems:** Establish clear communication channels and guidelines, conduct regular meetings and feedback sessions, use various communication channels (Webex, WhatsApp, email).
|
|
|
* **Time management:** Create realistic schedules, prioritize tasks, use task management tools, use NexctCloud Decks.
|
|
|
* **Conflicts with students:** Deal with criticism openly and constructively, address the needs of students, seek support from lecturers or the study program director if in doubt.
|
|
|
* **Low participation in events:** Plan attractive events that meet the interests of the students, involve students in the planning, inform about the events early and comprehensively.
|
|
|
|
|
|
**Competencies of the Product Owner:**
|
|
|
|
|
|
* **Organizational skills:** The Product Owner must be able to organize and coordinate complex tasks.
|
|
|
* **Communication skills:** The Product Owner must be able to communicate effectively with students, lecturers, and other stakeholders.
|
|
|
* **Time management:** The Product Owner must be able to manage their time effectively and meet deadlines.
|
|
|
* **Teamwork skills:** The Product Owner must be able to work in a team and promote collaboration with StuRa and StuK.
|
|
|
* **Digital competence:** The Product Owner should be familiar with digital tools such as Nextcloud and Webex.
|
|
|
|
|
|
**Tools of the Product Owner:**
|
|
|
|
|
|
* **Nextcloud:** For organizing files and collaborating with students.
|
|
|
* **Webex:** For communicating with students and conducting online meetings.
|
|
|
* **Microsoft Office/ Google Workspace:** For creating documents and presentations.
|
|
|
|
|
|
**Success factors for the Product Owner:**
|
|
|
|
|
|
* **Proactive communication:** The Product Owner should regularly inform students about important events and changes.
|
|
|
* **Gather feedback:** The Product Owner should regularly gather feedback from students to improve the organization and execution of the study program.
|
|
|
* **Transparency:** The Product Owner should be transparent about decisions and processes.
|
|
|
* **Reliability:** The Product Owner should be reliable and accessible to students. |
|
|
\ No newline at end of file |