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)

    Scrum Agile events, based on The 2020 Scrum Guide [1]. Scrum is an agile team collaboration framework commonly used in software development and other industries.. Scrum prescribes for teams to break work into goals to be completed within time-boxed iterations, called sprints.

  3. Burndown chart - Wikipedia

    en.wikipedia.org/wiki/Burndown_chart

    It is useful for predicting when all of the work will be completed. It is often used in agile software development methodologies such as Scrum. However, burndown charts can be applied to any project containing measurable progress over time. Remaining work can be represented in terms of either time or story points (a sort of arbitrary unit). [2]

  4. Agile software development - Wikipedia

    en.wikipedia.org/wiki/Agile_software_development

    Agile methods are mentioned in the Guide to the Project Management Body of Knowledge (PMBOK Guide 6th Edition) under the Product Development Lifecycle definition: Within a project life cycle, there are generally one or more phases that are associated with the development of the product, service, or result.

  5. Planning poker - Wikipedia

    en.wikipedia.org/wiki/Planning_poker

    Agile software development methods recommend the use of Planning Poker for estimating the size of user stories and developing release and iteration plans. [ 1 ] The method was first defined and named by James Grenning in 2002 [ 2 ] and later popularized by Mike Cohn in the book Agile Estimating and Planning , [ 3 ] whose company trade marked ...

  6. Design sprint - Wikipedia

    en.wikipedia.org/wiki/Design_sprint

    A design sprint is a time-constrained, five-phase process that uses design thinking with the aim of reducing the risk when bringing a new product, service or a feature to the market. The process aims to help teams to clearly define goals, validate assumptions and decide on a product roadmap before starting development. [ 1 ]

  7. Stand-up meeting - Wikipedia

    en.wikipedia.org/wiki/Stand-up_meeting

    The daily commitments allow participants to know about potential challenges as well as to coordinate efforts to resolve difficult or time-consuming issues. The stand-up has particular value in agile software development processes, [3] [4] such as scrum or Kanban, but can be utilized in context of any software-development methodology.

  8. Disciplined agile delivery - Wikipedia

    en.wikipedia.org/wiki/Disciplined_agile_delivery

    The phases are Inception (what is sometimes called "Sprint 0"), Construction, and Transition (what is sometimes called a Release sprint). Lean. A three-phase project lifecycle based on Kanban. Continuous delivery: Agile. An Agile-based product lifecycle that supports a continuous flow of work resulting in incremental releases (typically once a ...

  9. Spike (software development) - Wikipedia

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

    A spike in a sprint can be used in a number of ways: [2] As a way to familiarize the team with new hardware or software; To analyze a problem thoroughly and assist in properly dividing work among separate team members. Spike tests can also be used to mitigate future risk, and may uncover additional issues that have escaped notice.