Deliberate Discovery by Dan North

Jetzt loslegen. Gratis!
oder registrieren mit Ihrer E-Mail-Adresse
Deliberate Discovery by Dan North von Mind Map: Deliberate Discovery by Dan North

1. Project estimation tips

1.1. Assume the following as fact when you estimate:

1.1.1. Several (pick a number) Unpredictable Bad Things will happen during your project

1.1.1.1. You cannot know in advance what those Bad Things will be. That’s what Unpredictable means.

1.1.1.2. The Bad Things will materially impact delivery. That’s what Bad means.

2. Our single biggest limiting factor to successful delivery is ignorance

2.1. During the life of the project our ignorance will reduce across a number of axes that are relevant to our project

2.2. Ignorance of certain factors right now are the things currently limiting us the most

2.3. We probably don’t know which ones those magic enabling factors are

2.3.1. We are second-order ignorant of which factors are currently the most constraining

2.4. Once we realise what these are, we can apply methods to consistently move forwards, but until we do, we’re shooting in the dark

3. We need to continuously invest in reducing that ignorance

3.1. We need to invest effort in firstly discovering which aspects of delivery we are most critically ignorant of

3.1.1. i.e. both where we are ignorant and where that ignorance is hampering throughput

3.2. and further to invest in reducing that ignorance

3.2.1. deliberately discovering enough to relieve the constraint and allow us to proceed

4. At the start of a project, when we are most ignorant about most aspects of the project

4.1. the best use we can possibly make of the time available is to attempt to identify and reduce our ignorance across all the axes we can think of

4.1.1. we should take a first stab at identifying these axes, and trying to figure out just how ignorant we are

4.2. beware that with up-front analysis we may be “locking in" our ignorance

4.2.1. death-by-stories

5. Example "Axes of Ignorance"

5.1. the particular technologies you are using

5.2. the breadth of technology options available to you

5.3. the domain

5.4. the ways in which you could address the problem or opportunity

5.5. ways of articulating the problem – a better model – that would make the solution obvious

5.6. the people in the team – their aspirations or fears, their motivation, their relationships with one another and out into to the wider organisation

5.7. organisational constraints

5.8. third party integration risks

5.9. who are the people you should be building relationships with

5.10. the delivery approach/method

5.11. the culture of the organisation

5.12. ...