enow.com Web Search

Search results

  1. Results from the WOW.Com Content Network
  2. Scrum (software development) - Wikipedia

    en.wikipedia.org/wiki/Scrum_(software_development)

    Conducted at the end of a sprint, a sprint review is a meeting that has a team share the work they've completed with stakeholders and liaise with them on feedback, expectations, and upcoming plans. At a sprint review completed deliverables are demonstrated to stakeholders. The recommended duration for a sprint review is one hour per week of sprint.

  3. Timeboxing - Wikipedia

    en.wikipedia.org/wiki/Timeboxing

    A typical length for a sprint is less than 30 days. [18] [19] Sprint planning, sprint retrospective and sprint review meetings are timeboxed. [18] In Extreme programming methodologies, development planning is timeboxed into iterations typically 1, 2 or 3 weeks in length. The business revalues pending user stories before each iteration. [20]

  4. Agile software development - Wikipedia

    en.wikipedia.org/wiki/Agile_software_development

    Scott Ambler explained: ... (sprint planning, sprint review and retrospective) ... timely meeting where all team members disseminate information. If problem-solving ...

  5. Stand-up meeting - Wikipedia

    en.wikipedia.org/wiki/Stand-up_meeting

    The meetings are usually timeboxed to between 5 and 15 minutes, and take place with participants standing up to remind people to keep the meeting short and to-the-point. [6] The stand-up meeting is sometimes also referred to as the "stand-up" when doing Extreme Programming, "morning rollcall" or "daily scrum" when following the scrum framework.

  6. Planning poker - Wikipedia

    en.wikipedia.org/wiki/Planning_poker

    Planning poker, also called Scrum poker, is a consensus-based, gamified technique for estimating, mostly used for timeboxing in Agile principles.In planning poker, members of the group make estimates by playing numbered cards face-down to the table, instead of speaking them aloud.

  7. Software review - Wikipedia

    en.wikipedia.org/wiki/Software_review

    A software review is "a process or meeting during which a software product is examined by a project personnel, managers, users, customers, user representatives, ...

  8. Design sprint - Wikipedia

    en.wikipedia.org/wiki/Design_sprint

    The concept sprint is a fast five-day process for cross-functional teams to brainstorm, define, and model new approaches to business issue. [ 10 ] [ 11 ] Another common variant is the Service Design Sprint , an approach to Design Sprints created in 2014 that uses Service Design tools and mechanics to tackle service innovation.

  9. After-action review - Wikipedia

    en.wikipedia.org/wiki/After-action_review

    An after action review (AAR) is a technique for improving process and execution by analyzing the intended outcome and actual outcome of an action and identifying practices to sustain, and practices to improve or initiate, and then practicing those changes at the next iteration of the action [1] [2] AARs in the formal sense were originally developed by the U.S. Army. [3]