When.com Web Search

Search results

1. Results From The WOW.Com Content Network

2. 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.

3. 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 ...

4. 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.

5. Agile software development - Wikipedia

   en.wikipedia.org/wiki/Agile_software_development

   Agile software development is an umbrella term for approaches to developing software that reflect the values and principles agreed upon by The Agile Alliance, a group of 17 software practitioners, in 2001. [1] As documented in their Manifesto for Agile Software Development the practitioners value: [2] Individuals and interactions over processes ...

6. Specification by example - Wikipedia

   en.wikipedia.org/wiki/Specification_by_example

   Highly abstract or novel new concepts can be difficult to understand without concrete examples. [citation needed] Specification by example is intended to construct an accurate understanding, and significantly reduces feedback loops in software development, leading to less rework, higher product quality, faster turnaround time for software changes and better alignment of activities of various ...

7. Kanban board - Wikipedia

   en.wikipedia.org/wiki/Kanban_board

   A popular example of a kanban board for agile or lean software development consists of: Backlog, Ready, Coding, Testing, Approval and Done columns. It is also a common practice to name columns in a different way, for example: Next, In Development, Done, Customer Acceptance, Live. [5] Kanban for marketing teams [6] Kanban for HR teams [7]