סקרים

[Virtual Presenter] VR Smart Rehabilitation Hospital Sprint 1 – Iteration Review Team Members & Roles:  Product Owner / Quality Assurance (QA) : Ahmad Badran  Scrum Master / Developer: Salameh Ayash Sprint Goal Sprint 1 Objective:  Build a functional VR Rehabilitation Room in Unity 6  Support Doctor–Patient VR sessions  Enable Doctor–Doctor consultation  Implement a Virtual Doctor interaction  Focus on voice communication, avatars, and UX flow The Problem.

[Audio] Challenges in Traditional Rehabilitation Sessions Rehabilitation processes today face several limitations:  Limited access to therapy Patients must physically travel to clinics, which is difficult for elderly or injured patients.  Low engagement during sessions Repetitive exercises and explanations reduce patient motivation and focus.  Lack of realistic interaction in remote care Video calls do not provide presence, body language, or spatial awareness.  Poor collaboration between medical professionals Doctors rarely meet together in a shared interactive environment to discuss patient cases.  Inefficient patient guidance outside the clinic Patients often forget instructions once the session ends. Result: Rehabilitation becomes less effective, less engaging, and harder to scale. The Solution.

[Audio] VR Smart Rehabilitation Hospital Our project introduces a Virtual Reality rehabilitation environment that improves therapy quality and accessibility. Key Solution Elements:  Immersive VR rehabilitation room Patients and doctors meet in a shared 3D environment that feels real and focused.  Doctor–Patient VR sessions Real-time voice communication and avatars enable natural medical interaction.  Doctor–Doctor consultation in VR Multiple doctors can join the same room and review medical cases together using 3D models.  Virtual Doctor assistance A virtual doctor avatar provides guidance, explanations, and structured rehabilitation dialogue.  Improved engagement and understanding Visual, spatial, and interactive elements increase patient motivation and clarity. Goal: Make rehabilitation sessions more effective, accessible, and engaging using VR technology. Target Audience ?Who Will Use This System.

[Audio]  Rehabilitation Patients After injury, surgery, or mobility limitations.  Rehabilitation Doctors & Physiotherapists For treatment, guidance, and follow-up in VR.  Medical Teams For consultation and collaboration in virtual meetings.  Rehabilitation Clinics & Centers To extend rehabilitation services remotely. User Stories User Story 1 - Feature 1: Doctor-Patient VR Meeting.

[Audio] As a patient, I want to meet my doctor in a VR environment so that I can receive explanations and rehabilitation guidance without needing to travel to .the hospital Scenario A - Doctor-Patient VR Meeting 1. User logs into the system 2. SessionData stores user role (Doctor / Patient) 3. User loads into the Meeting_Room 4. Local avatar + remote avatar are created 5. Avatar color + display name are applied 6. Meeting start/end times are logged User Story 2 – Feature 2: Doctor–Doctor Consultation As a rehabilitation doctor, I want to meet another specialist in VR so that we .can review a patient's case together and decide on the best treatment plan.

[Audio] Scenario B - Multi-Doctor Consultation 1. Doctor 1 enters the VR room 2. Doctor 2 enters the VR room 3. A 3D medical model is loaded 4. Doctors review the case together User Story 3 – Feature 3: Virtual Doctor As a patient, I want to talk with a virtual doctor in the VR room so that I can .receive explanations and guidance even when a real doctor is not available.

[Audio] Scenario C - Virtual Doctor Dialogue 1. The patient enters the VR room 2. The system detects the patient's presence 3. The "Talk to Virtual Doctor" button becomes available 4. The patient activates the button 5. The virtual doctor appears inside the room 6. The dialogue begins (step-by-step scripted conversation) 7. Interaction logs are recorded in the console 8. The dialogue ends with "Dialogue finished" Sprint Results.

[Audio] Retrospective: What Went Well  Clear and well-defined team roles  High transparency using ClickUp.

[Audio]  Good collaboration between QA and development  Consistent progress toward a working product  Positive team communication and cooperation What Didn't Go Well  Time estimation was not always accurate  High workload toward the end of the sprint  Voice and input stability issues  Some features were tested too late What We Will Change in the Next Iteration  Break tasks into smaller subtasks  Start QA testing earlier in the sprint  Improve planning for VR interactions  Enhance audio and input stability  Add clearer acceptance criteria for each user story (Full System Demo (Video Record.

[Audio] Thank You. Thank You.