D5 - Adaptive Planning

Question 1

Examples of interactive planning

Answer 1

daily, BL prioritization, retro, iteration planning

Question 2

This is an elevator pitch that articulates the product end goal

Answer 2

product vision statement

Question 3

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

Answer 3

product roadmap

Question 4

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

Answer 4

release planning

Question 5

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

Answer 5

sprint/iteration backlog

Question 6

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

Answer 6

increment

Question 7

Characteristics of adaptive planning

Answer 7

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

Question 8

This will uncover true requiments

Answer 8

trial and demo

Question 9

Characteristics of iterative planning

Answer 9

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

Question 10

changes to plans in agile projects are

Answer 10

normal

Question 11

knowledge work doesn’t follow a

Answer 11

predictive plan

Question 12

we do this as more information becomes available

Answer 12

progressive elaboration

Question 13

This is way of planning in chunks

Answer 13

rolling wave

Question 14

This is then business benefit - the cost

Answer 14

value based analysis

Question 15

Characteristics of value based decompistion

Answer 15

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

Question 16

Tool to imagine product features and elements expressed as a graphic

Answer 16

product box

Question 17

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

Answer 17

course grained

Question 18

timebox of the daily

Answer 18

15 min

Question 19

timebox of the retro

Answer 19

2 hours

Question 20

timebox of the iterations

Answer 20

1-4 weeks

Question 21

timebox of the daily

Question 22

ideal work items per sprint

Answer 22

12

Question 23

work items not completed

Answer 23

go to backlog

Question 24

Parkinson’s law

Answer 24

work expands to fill allotted time

Question 25

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

Answer 25

estimate convergence graph

Question 26

estimating should happen

Answer 26

at the last responsible moment

Question 27

Who estimates?

Answer 27

the team

Question 28

ideal time is

Answer 28

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

Question 29

User story formats

Answer 29

given when then or as a I need so I can

Question 30

The three c's

Answer 30

card conversation confirmation

Question 31

invest

Answer 31

independent, negotiable, valuable estimate, small; and testable

Question 32

This estimates size based on analgous,

Answer 32

relative

Question 33

story points

Answer 33

overall effort and accounts for time, risk, complexity

Question 34

fib seq

Answer 34

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

Question 35

Who decides when the product is released

Answer 35

the po

Question 36

Question's to ask for release planning

Answer 36

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

Question 37

inputs for release planning

Answer 37

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

Question 38

this groups items based on similar feature size or pri

Answer 38

affinity estimating

Question 39

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

Answer 39

product roadmap

Question 40

Anonymous surveys to avoid group think

Answer 40

wide band delphi

Question 41

This is an aggregate in increments

Answer 41

a release

Question 42

first iteration with setup

Answer 42

iteration 0

Question 43

this iteration focusses on code cleanup, documentation and compiling

Answer 43

Iteration H

Question 44

This is a time boxed effort POC

Answer 44

architectural spike

Question 45

This is a short effort to review risk

Answer 45

risk based spike

Question 46

outputs of high level planning

Answer 46

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

Question 47

release planning

Answer 47

defines what stories are in which iteration to inform release