Continous Improvement (9%)

Question 1

lessons learned vs

retrospectives

Answer 1

traditional projects want to learn after a project

agile wants to learn after every iteration

Question 2

kaizen

Answer 2

change for the better 
continuous improvement 
1950s 
kaizen: PDCA
agile: plan develop evaluate learn 

5 why’s
fishbone
tools for retros but also for kaizen

Question 3

multiple levels of improvement in agile

Answer 3

pair programming
daily stand up
demo review retro
product release

Question 4

process tailoring

Answer 4

kanban - make it yours
scrum - stick to the rules

hybrid
form of process tailoring

Question 5

methodology anti-patterns

Answer 5

• one size for all projects
• intolerant: team should be able to decide on changes
• heavy: do not add much more procedures
• established:
• untried: se things that worked in practice, not something unseen

Question 6

success criteria

Answer 6

the project got shipped

the leadership remained intact

the team would work the same way again

Question 7

methodology success patterns

Answer 7

interactive face to face communication

only little documentation

larger teams need heavier methodologies

critical projects need more ceremony

feedback and communication reduce the need for intermediate deliverables

discipline and skills over process and formality

efficiency is expandable

Question 8

value stream mapping

Answer 8

map process
improve process

total cycle time
value added time
no value added time
process cycle efficiency

Question 9

project pre mortems

Answer 9

1. imagine the failure
2. generate the reason for failure
3. consolidate the list
4. revisit the plan