When.com Web Search

  1. Ads

    related to: safe agile best practices to capture details in the backlog

Search results

  1. Results From The WOW.Com Content Network
  2. Scaled agile framework - Wikipedia

    en.wikipedia.org/wiki/Scaled_agile_framework

    The scaled agile framework (SAFe) is a set of organization and workflow patterns intended to guide enterprises in scaling lean and agile practices. [1] [2] Along with disciplined agile delivery (DAD) and S@S (Scrum@Scale), SAFe is one of a growing number of frameworks that seek to address the problems encountered when scaling beyond a single team.

  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. Scrum (software development) - Wikipedia

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

    The product backlog is a breakdown of work to be done and contains an ordered list of product requirements (such as features, bug fixes and non-functional requirements) that the team maintains for a product. The order of a product backlog corresponds to the urgency of the task. Common formats for backlog items include user stories and use cases ...

  5. INVEST (mnemonic) - Wikipedia

    en.wikipedia.org/wiki/INVEST_(mnemonic)

    The INVEST mnemonic for Agile software development projects was created by Bill Wake [1] as a reminder of the characteristics of a good quality Product Backlog Item (commonly written in user story format, but not required to be) or PBI for short. Such PBIs may be used in a Scrum backlog, Kanban board or XP project.

  6. Agile architecture - Wikipedia

    en.wikipedia.org/wiki/Agile_architecture

    Agile architecture means how enterprise architects, system architects and software architects apply architectural practice in agile software development.A number of commentators have identified a tension between traditional software architecture and agile methods along the axis of adaptation (leaving architectural decisions until the last possible moment) versus anticipation (planning in ...

  7. Agile modeling - Wikipedia

    en.wikipedia.org/wiki/Agile_Modeling

    Agile modeling (AM) is a methodology for modeling and documenting software systems based on best practices. It is a collection of values and principles that can be applied on an (agile) software development project. This methodology is more flexible than traditional modeling methods, making it a better fit in a fast-changing environment. [1]

  8. Burndown chart - Wikipedia

    en.wikipedia.org/wiki/Burndown_chart

    The outstanding work (or backlog) is often on the vertical axis, with time along the horizontal. A burndown chart is a run chart of remaining work. 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 ...

  9. Agile management - Wikipedia

    en.wikipedia.org/wiki/Agile_management

    Agile management is a current leader in popular project and team management methods. However, new practices have emerged attuned to the complexities of advancing technologies and have evolved to cover specialized areas such as Platform engineering and Site reliability engineering. Agile management has been noted to bring about positive ...