D5 - Adaptive Planning Flashcards

1
Q

Examples of interactive planning

A

daily, BL prioritization, retro, iteration planning

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

This is an elevator pitch that articulates the product end goal

A

product vision statement

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

This is a high level overview of functionality required to achieve product vision

A

product roadmap

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

This outlines the next set of functionality that will go into production

A

release planning

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

This is a list of tasks for the team to create a potentially shippable product

A

sprint/iteration backlog

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

This is a fully developed working product that is then outcome of a sprint

A

increment

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Characteristics of adaptive planning

A

value driven, minimize non value add work, plan to re-plan, early plans are flawed, uncertainty requires re-planning

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

This will uncover true requiments

A

trial and demo

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Characteristics of iterative planning

A

effort is distributed, agile projects are risky, and more planning is required

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

changes to plans in agile projects are

A

normal

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

knowledge work doesn’t follow a

A

predictive plan

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

we do this as more information becomes available

A

progressive elaboration

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

This is way of planning in chunks

A

rolling wave

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

This is then business benefit - the cost

A

value based analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Characteristics of value based decompistion

A

elicit requirements, group features, break down features, ranking and prioritization

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Tool to imagine product features and elements expressed as a graphic

A

product box

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

this level of requirement identification is high level and delays decisions to that last responsible moment

A

course grained

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

timebox of the daily

A

15 min

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

timebox of the retro

A

2 hours

20
Q

timebox of the iterations

A

1-4 weeks

21
Q

timebox of the daily

A
22
Q

ideal work items per sprint

A

12

23
Q

work items not completed

A

go to backlog

24
Q

Parkinson’s law

A

work expands to fill allotted time

25
Q

This graph shows flaws of original estimates, and variance change as more information becomes available

A

estimate convergence graph

26
Q

estimating should happen

A

at the last responsible moment

27
Q

Who estimates?

A

the team

28
Q

ideal time is

A

estimate if there were no interruptions and assumes all time in the estimate is for project work

29
Q

User story formats

A

given when then or as a I need so I can

30
Q

The three c’s

A

card conversation confirmation

31
Q

invest

A

independent, negotiable, valuable estimate, small; and testable

32
Q

This estimates size based on analgous,

A

relative

33
Q

story points

A

overall effort and accounts for time, risk, complexity

34
Q

fib seq

A

1, 2, 3,5, 8, 13, 21

35
Q

Who decides when the product is released

A

the po

36
Q

Question’s to ask for release planning

A

where is the po, do we have a pri backlog, how do we size, who is coming, plan logistics, multiple teams, do we need help

37
Q

inputs for release planning

A

previous release, feedback from SH, action plan and smart goals, for prior release or retro, items and defects to consider, dev or arch info, velocity, org calendars, input from other teams

38
Q

this groups items based on similar feature size or pri

A

affinity estimating

39
Q

This is a visualization of releases of high level functionality and initial cut of backlog

A

product roadmap

40
Q

Anonymous surveys to avoid group think

A

wide band delphi

41
Q

This is an aggregate in increments

A

a release

42
Q

first iteration with setup

A

iteration 0

43
Q

this iteration focusses on code cleanup, documentation and compiling

A

Iteration H

44
Q

This is a time boxed effort POC

A

architectural spike

45
Q

This is a short effort to review risk

A

risk based spike

46
Q

outputs of high level planning

A

updated backlog, course grained estimate, goals defined, release date

47
Q

release planning

A

defines what stories are in which iteration to inform release