When.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)

    A common approach to adapting scrum is the combination of scrum with other software development methodologies, as scrum does not cover the whole product development lifecycle. [42] Various scrum practitioners have also suggested more detailed techniques for how to apply or adapt scrum to particular problems or organizations.

  3. Product backlog - Wikipedia

    en.wikipedia.org/wiki/Product_backlog

    The agile product backlog in scrum is a prioritized features list, containing short descriptions of all functionality desired in the product. When applying the scrum or other agile development methodology, it is not necessary to start a project with a lengthy, upfront effort to document all requirements as is more common with traditional project management methods following the waterfall model.

  4. Agile software development - Wikipedia

    en.wikipedia.org/wiki/Agile_software_development

    Agile software development methods lie on the adaptive side of this continuum. One key of adaptive development methods is a rolling wave approach to schedule planning, which identifies milestones but leaves flexibility in the path to reach them, and also allows for the milestones themselves to change. [44]

  5. Software development process - Wikipedia

    en.wikipedia.org/wiki/Software_development_process

    In software engineering, a software development process or software development life cycle (SDLC) is a process of planning and managing software development. It typically involves dividing software development work into smaller, parallel, or sequential steps or sub-processes to improve design and/or product management .

  6. 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]

  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. Application lifecycle management - Wikipedia

    en.wikipedia.org/wiki/Application_lifecycle...

    ALM is a broader perspective than the Software Development Life Cycle (SDLC), which is limited to the phases of software development such as requirements, design, coding, testing, configuration, project management, and change management. ALM continues after development until the application is no longer used, and may span many SDLCs.

  9. Iterative and incremental development - Wikipedia

    en.wikipedia.org/wiki/Iterative_and_incremental...

    Iterative and incremental development is any combination of both iterative design (or iterative method) and incremental build model for development. Usage of the term began in software development , with a long-standing combination of the two terms iterative and incremental [ 1 ] having been widely suggested for large development efforts.