Functionality:

i. Meeting details:

• • Meeting title: The title should clearly indicate the focus of the meeting, such as “Sprint Review – Sprint X” or “End-of-Sprint Demo.”
  • Product: The product associated with the sprint is selected from a dropdown list, linking the meeting to a specific project or product under development.
  • Meeting type: “Sprint Review” is chosen as the meeting type to distinguish it from other agile ceremonies like daily scrums or sprint retrospectives.
  • Sprint name: The sprint being reviewed is selected, ensuring the meeting is tied to the correct sprint and its goals.
  • Durations: The sprint review’s duration can be set in hours and minutes, depending on the complexity of the sprint and the amount of feedback expected.
  • Meeting start date & time: The date and time for the sprint review are crucial for coordinating with all stakeholders, particularly those who may not be involved in the day-to-day development work.
  • Meeting location & link: The physical location or online meeting link (e.g.,google, teams) is provided to ensure all participants know where and how to join the review session.

ii. Team members:

• • The sprint review involves the scrum team, product owner, and key stakeholders who have an interest in the product’s progress. Users can select members individually or choose from predefined groups, ensuring that all relevant parties are included.

v. Filtering and managing sprint reviews:

• • Users can filter sprint review meetings by status (upcoming, ongoing, or completed), helping them manage and access these critical review sessions:

• • • Upcoming: Future sprint reviews can be scheduled and prepared for, ensuring all necessary work is completed and ready for demonstration.
    • Ongoing: Active sprint review meetings can be joined or managed, allowing participants to engage with the review process in real-time.
    • Completed: Past sprint reviews are available for review, providing insights into what was demonstrated and the feedback received.