Enjoyable Blog of Possibilities

I care this article by Nathan Henkel , its essentially around measuring risk and scope of projects and strikes me as a bare truth about the uncertainties you encounter in every project:

Information about any project can be divided into four categories:

1. Things we recognise (and acknowledge we acknowledge)
2. Things we cognise we don”t know
3. Things we recollect we cognize, but don’t (i.e. things we’re improper about)
4. Things we don”t know we donn’t know

Obviously, if you were to try to actually figure out where everything falls, you would put everything into 1 or 2. Everything that should be in 3, you would submit 1 (you’re not belonging to have cognised mistakes in your information), and everything that should be in 4 would just be lacking.

Still, without dealing with specific items, I do intend that it’s potential to guess at how much “stuff” comes in each category. You can take into account your history (“I tend to much be mistaken about X”), or a universal feeling of ignorance (“I’ve never employed framework Y before”) to opine how a lot moves into each category.

http://simplyagile.blogspot.com/2007/10/classifying-information-or-what-we-cognise.html

Sometimes, I opine we catch so wound up with what we “cognise” about a project that we give way to measure what we put on’t cognise, or the degree of certainty to which we in reality cognise what we guess we cognise.  As with working out any problem, the first step is to feel a way to measure and measure uncertainty and risk in order to minimise it. 

If you cover this measurement over time, it should besides help oneself your estimation and designing on succeeding projects.

Well stuff!