Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

What Is A Sprint Review

4.861 Aufrufe

Veröffentlicht am

This is a short introduction to the practice of Sprint Review in Scrum. It would be useful for people new to Scrum or Agile. For more, comment or write to read my blog : http://agilediary.wordpress.com/

Veröffentlicht in: Business, Sport, Technologie
  • Follow the link, new dating source: ❤❤❤ http://bit.ly/2Q98JRS ❤❤❤
       Antworten 
    Sind Sie sicher, dass Sie …  Ja  Nein
    Ihre Nachricht erscheint hier
  • Dating for everyone is here: ❶❶❶ http://bit.ly/2Q98JRS ❶❶❶
       Antworten 
    Sind Sie sicher, dass Sie …  Ja  Nein
    Ihre Nachricht erscheint hier
  • Is it possible to improve your memory? How can I improve my memory recall? more info... ▲▲▲ https://bit.ly/2GEWG9T
       Antworten 
    Sind Sie sicher, dass Sie …  Ja  Nein
    Ihre Nachricht erscheint hier
  • Memory Improvement: How To Improve Your Memory In Just 30 Days, click here.. ♣♣♣ https://bit.ly/2GEWG9T
       Antworten 
    Sind Sie sicher, dass Sie …  Ja  Nein
    Ihre Nachricht erscheint hier

What Is A Sprint Review

  1. 1. Sprint Review An Introduction
  2. 2. Planning Meeting Review Meeting Retrospective SPRINT
  3. 3. Sprint Review <ul><li>After the team has picked the requirements from the Project Backlog , during the Sprint Planning Meeting , the team normally drafts a Sprint Backlog , the team starts working on the requirements and through a Daily Stand Up during the Sprint and updates the Sprint Backlog . </li></ul><ul><li>Once the sprint is complete, the time comes to demonstrate working functionality. </li></ul><ul><li>For this, the team and product owner gather together for Sprint Review . </li></ul><ul><li>A Sprint Review is a meeting where the team demonstrates working software corresponding to project backlog items they have completed in a given sprint. </li></ul>
  4. 4. Rules of Sprint Review <ul><li>The meeting is kept very informal . The team should not have to spend time preparing for the same beyond getting working software ready. </li></ul><ul><li>PowerPoint's, presentations, speeches and lectures are not allowed. </li></ul><ul><li>You can only demonstrate working software . </li></ul><ul><li>The preparation [working environment, arranging room] is done by the Agile Coach or Scrum Master. </li></ul><ul><li>The meeting generally lasts about 1 hour per week of work [but this obviously can change depending on number of team members working for the project]. </li></ul><ul><li>The whole team , product owner or customers and stakeholders participate in the Sprint Review Meeting. </li></ul>
  5. 5. Rules of Sprint Review <ul><li>The team would typically demonstrate each code it has written either through GUI, mock objects or through API calls. </li></ul><ul><li>The feedback to the team is typically of these components: </li></ul><ul><ul><li>Whether they completed enough requirements </li></ul></ul><ul><ul><li>Whether they understood the requirements and translated them to working features well enough </li></ul></ul>
  6. 6. Demo <ul><li>The sprint review starts with a team member presenting the sprint goal, the product backlog committed to, and the product backlog completed. </li></ul><ul><li>‘ Done’ usually means that the functionality is completely engineered and could be potentially shipped or implemented. </li></ul><ul><li>Functionality that is not ‘done’ cannot be presented. </li></ul><ul><li>The majority of the sprint review is spent with team members presenting functionality, answering stakeholder questions regarding the presentation and noting changes that are desired. </li></ul>
  7. 7. Demo <ul><li>At the end of the presentations, the stakeholders are polled, one by one to get their impressions, any desired changes and the priority of these changes. </li></ul><ul><li>Stakeholders are free to voice any comments, observations or criticisms regarding the increment of potentially shippable product functionality between presentations. </li></ul><ul><li>Stakeholders can identify new functionality that occurs to them as they view the presentation and request that the functionality be added to the product backlog for prioritization. </li></ul>
  8. 8. After the Sprint Review <ul><li>At the end of sprint review meeting, Agile Coach or Scrum Master would announce the date for next Sprint Review and confirm the date for next Sprint Planning session. </li></ul><ul><li>This sets the tone for the next sprint. After the Sprint Review Meeting, the team moves towards the Sprint Retrospectives. </li></ul>

×