You are here

Home

Sprint/Iteration Review

Error message

  • Deprecated function: TYPO3\PharStreamWrapper\Manager::initialize(): Implicitly marking parameter $resolver as nullable is deprecated, the explicit nullable type must be used instead in include_once() (line 19 of /homepages/11/d343571938/htdocs/drupal/includes/file.phar.inc).
  • Deprecated function: TYPO3\PharStreamWrapper\Manager::initialize(): Implicitly marking parameter $collection as nullable is deprecated, the explicit nullable type must be used instead in include_once() (line 19 of /homepages/11/d343571938/htdocs/drupal/includes/file.phar.inc).
  • Deprecated function: TYPO3\PharStreamWrapper\Manager::__construct(): Implicitly marking parameter $resolver as nullable is deprecated, the explicit nullable type must be used instead in include_once() (line 19 of /homepages/11/d343571938/htdocs/drupal/includes/file.phar.inc).
  • Deprecated function: TYPO3\PharStreamWrapper\Manager::__construct(): Implicitly marking parameter $collection as nullable is deprecated, the explicit nullable type must be used instead in include_once() (line 19 of /homepages/11/d343571938/htdocs/drupal/includes/file.phar.inc).

The point is not to show that your software works but that it is useful and valuable
No smoke and mirrors and never ever show anything that is not 100% done

Agenda

  1. The Scrum Master opens the review and reiterates the purpose
    • Show what the team has built during the last sprint
    • Engage with the audience
    • Collect feedback
  2. The Scrum Master presents the sprint
    • Tell the story of the sprint:
    • How did it go?
    • Leeches / Absence?
    • New team members?
    • Anything else important?
    • Give a status of the sprint and an overview of which stories were finished and which ones weren't
  3. For each story:
    • The team member shows the story description and describes the boundaries (explain the acceptance criteria without reading them out)
    • Demonstrate the feature on a real system
    • Take questions and listen to feedback
    • Collect ideas for new features and user stories to include on the product backlog.
    • Repeat for all user stories ‘Done’ during the sprint.
  4. The Product Owner discusses the Product Backlog
    • Are there Any Key Dates.
    • What is the upcoming Key Work
    • The entire group collaborates on what to do next. (Input to subsequent Sprint Planning Session)
  5. Scrum Master closes session
    • Wrap up
    • Communicate the time and date for the next end-of-sprint review.

Resources