87:. Instead, a scrum team and its product owner will typically begin by writing down every relevant feature they can think of for the project's agile backlog prioritization, and the initial agile product backlog is almost always more than enough for a first sprint. The scrum product backlog is then allowed to grow further throughout the project life cycle and change as more is learned about the product and its customers.
82:
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
32:
software development framework. The product backlog is referred to with different names in different project management frameworks, such as
205:
52:. In the scrum framework, creation and continuous maintenance of the product backlog is part of the responsibility of the
290:
74:
is defined as a measure of the relationships between backlog items which make them worthy of consideration as a whole.
64:
63:
consists of selected elements from the product backlog which are planned to be developed within that particular
285:
24:
refers to a prioritized list of functionality which a product should contain. It is sometimes referred to as a
53:
29:
41:
17:
181:
152:
8:
83:
requirements as is more common with traditional project management methods following the
229:
49:
249:
94:
268:
125:
84:
279:
99:
90:
A typical scrum backlog comprises the following different types of items:
28:, and is considered an 'artifact' (a form of documentation) within the
25:
277:
182:"Agile Core Practice: Prioritized Requirements"
126:"The product backlog: your ultimate to-do list"
230:"Produkteier | Digitaliseringsdirektoratet"
250:"Sprintkø | Digitaliseringsdirektoratet"
278:
123:
176:
174:
172:
147:
145:
13:
14:
302:
169:
142:
262:
242:
222:
198:
117:
1:
111:
153:"What is a Product Backlog?"
7:
206:"Artifact: Work Items List"
10:
307:
291:Agile software development
269:Scrum Glossary | Scrum.org
77:
18:agile project management
286:Computing terminology
107:Knowledge acquisition
186:agilemodeling.com
42:disciplined agile
298:
271:
266:
260:
259:
257:
256:
246:
240:
239:
237:
236:
226:
220:
219:
217:
216:
202:
196:
195:
193:
192:
178:
167:
166:
164:
163:
149:
140:
139:
137:
136:
121:
306:
305:
301:
300:
299:
297:
296:
295:
276:
275:
274:
267:
263:
254:
252:
248:
247:
243:
234:
232:
228:
227:
223:
214:
212:
204:
203:
199:
190:
188:
180:
179:
170:
161:
159:
151:
150:
143:
134:
132:
122:
118:
114:
85:waterfall model
80:
34:product backlog
22:product backlog
12:
11:
5:
304:
294:
293:
288:
273:
272:
261:
241:
221:
197:
168:
141:
115:
113:
110:
109:
108:
105:
104:Technical work
102:
97:
79:
76:
61:sprint backlog
38:work item list
9:
6:
4:
3:
2:
303:
292:
289:
287:
284:
283:
281:
270:
265:
251:
245:
231:
225:
211:
207:
201:
187:
183:
177:
175:
173:
158:
154:
148:
146:
131:
127:
120:
116:
106:
103:
101:
98:
96:
93:
92:
91:
88:
86:
75:
73:
68:
66:
62:
57:
55:
54:product owner
51:
47:
43:
39:
35:
31:
27:
23:
19:
264:
253:. Retrieved
244:
233:. Retrieved
224:
213:. Retrieved
209:
200:
189:. Retrieved
185:
160:. Retrieved
156:
133:. Retrieved
129:
119:
89:
81:
71:
69:
60:
58:
45:
37:
33:
21:
15:
124:Atlassian.
46:option pool
280:Categories
255:2021-11-15
235:2021-11-15
215:2021-12-19
210:www.utm.mx
191:2021-12-19
162:2021-12-19
135:2021-12-19
112:References
70:In scrum,
36:in scrum,
26:to-do list
157:Scrum.org
130:Atlassian
72:coherence
95:Features
78:Outline
16:Within
65:sprint
44:, and
30:scrum
100:Bugs
50:lean
48:in
40:in
282::
208:.
184:.
171:^
155:.
144:^
128:.
67:.
59:A
56:.
20:,
258:.
238:.
218:.
194:.
165:.
138:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.