Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Document Properties Marker
overridefalse
Short DescriptionProduct Backlogs are means to collect user stories. 
Doctypedoctypehide
NameProduct Backlog 
IDproduct-backlog 
SetAgile Team 
Parent
Parent Property
parent-doctypetopic
property-nameName
 
Audience
Name List
doctyperole
render-no-hits-as-blanktrue
propertyAudience
 
Documentation Type
Name List
doctypedoctype-type
render-no-hits-as-blanktrue
namesQ2 - Project
propertyDocumentation Type
 
Categories
Name List
doctypecategory
names/ Work / Plan
propertyCategories
 
Tags
Tag List
namesAgile Planning
 
Iteration
Iteration
valuefocused
hide
Sort Keyhide
Section
indextrue
titleDescription

Create a backlog to collect user stories. You may organize user stories in different backlogs, although it is usually more effective for agile teams to stick with only one.

Backlogs aggregate prioritized user stories. Usually it is not a good idea to work with different backlogs, since this makes it difficult to define a clearly prioritized list of topics to work on. Therefore the main purpose of the Product Backlog Doctype is to define multiple views on the work. We expect that users work with their backlog on JIRA anyway. Backlogs provide views and allow to add additional information that is relevant for a group of related units of work.

...

Section
titleReferences

Section
titleResources

Piwik Set Multiple Custom Variables
NameValue
Departmentprojectdoc
Categoryprojectdoc-doctype
Typeagile