Search results

Page title matches

• Product review meeting
  |background=During the {{p|sprint review meeting}}, the {{p|development team}} demonstrates completed functionality to inter ...e surveys can provide quick quantitative feedback during {{p|sprint review meeting}}s. Not everything needs to be perfect—'''focus on core and differentiati
  4 KB (523 words) - 20:45, 18 March 2016
• Sprint review meeting
  #REDIRECT [[Product review meeting]]
  36 bytes (4 words) - 18:12, 10 July 2015

Page text matches

• Sprint review meeting
  #REDIRECT [[Product review meeting]]
  36 bytes (4 words) - 18:12, 10 July 2015
• Perfection game
  ...oving-from-critical-review-to-critique/ Jared Spool » Moving from Critical Review to Critique] *{{p|product review meeting}}
  554 bytes (61 words) - 13:53, 18 February 2016
• Sprint
  #{{p|sprint review meeting}} to review the product results of the previous {{p|sprint}}; #{{p|sprint planning meeting}} to plan the {{p|user stories}} of the product for the next {{p|sprint}};
  1 KB (213 words) - 13:12, 10 May 2013
• Agile Foundation Training
  *{{u|retrospective meeting}}. *{{u|review meeting}}.
  1 KB (187 words) - 17:06, 26 November 2015
• Operations review
  Why do you want to hold {{p|operations review}} meetings: {{quote|I also am very pleased by the recent {{p|operations review}} meeting. The presentation by the groups was concise, had good KPIs showing where th
  2 KB (366 words) - 09:07, 17 May 2016
• Agile shock therapy
  ...t review meeting}}, {{p|retrospective gathering}} and {{p|product planning meeting}} to a total of four hours.
  1 KB (154 words) - 18:33, 6 January 2014
• Mission Critical Agile
  **eliminate {{p|code review}}—there's a ton of objective, scientific even, information on why and how ...t backlog grooming meeting}}, {{p|sprint review meeting}}, {{p|daily scrum meeting}}
  3 KB (490 words) - 14:02, 12 July 2013
• Product review meeting
  |background=During the {{p|sprint review meeting}}, the {{p|development team}} demonstrates completed functionality to inter ...e surveys can provide quick quantitative feedback during {{p|sprint review meeting}}s. Not everything needs to be perfect—'''focus on core and differentiati
  4 KB (523 words) - 20:45, 18 March 2016
• Scrumming the scrum
  ...t. The {{p|build crew}} must have effective {{p|sprint}} {{p|retrospective meeting}} and have {{p|popped the happy bubble}}. The basic {{p|scrum}} mechanisms ...etermine when it is done. Evaluate the state of the item in the {{p|review meeting}} like any other item.
  3 KB (402 words) - 14:34, 12 July 2013
• Retrospective meeting
  ...meeting deserves a good structure. A default structure for a retrospective meeting looks like: ...ow it will radically improve your performance: AARs (After-Action Reviews) review projects, missions, training exercises or any other event you want to refle
  8 KB (1,193 words) - 16:13, 15 November 2023
• Ready to build
  ...g the planning session. Make it you goal to reduce the {{p|sprint planning meeting}} to a mere reconfirmation of the {{pb}} that emerged during the {{p|sprint *how it will be implemented, meeting or exceeding the non-functional requirements and within the technological a
  7 KB (1,220 words) - 06:58, 10 August 2016
• Fitness for purpose
  #daily, during the {{p|daily standup}} meeting to assess operational flow; #weekly, {{p|service delivery retroprospective}} or system capability review to retroprospect service delivery performance against quantitative fitness
  5 KB (788 words) - 15:41, 2 August 2016
• OKR
  ...{okrs}} with a {{p|season beat}} and make it a part of your {{p|operations review}}. Hold people publicly accountable for failing to regularly update their { ==Typical Progress Meeting==
  10 KB (1,561 words) - 15:24, 23 July 2023
• Product portfolio
  *Penalize any handover. Replace handovers by having any documentation be the meeting minutes of an collaborative conversation about discovery. *Track and review the {{p|product portfolio}} every three to four weeks on an operational and
  12 KB (1,746 words) - 13:48, 22 October 2014
• Product owner
  ...lving product at the end of each {{p|sprint}} during the {{p|sprint review meeting}}, soliciting feedback from key stakeholders. Keep everyone excited and int *comes to the {{p|sprint planning meeting}} with a clear business objective in mind and works with the {{p|build crew
  15 KB (2,380 words) - 08:05, 11 June 2019
• Team charter
  **Sprint Review: Wednesday 14:00 ***Estimation meeting
  11 KB (1,487 words) - 20:02, 30 May 2016
• Metric drives behavior
  *#*Meeting deadlines The {{p|operations review}} is a monthly feedback loop for a number of these metrics.
  16 KB (2,430 words) - 08:03, 4 August 2020