Deliverable vs Expectation

Explore this topic further by using one of the tasks / questions below.

Application to your work

What's outside the boundaries?

This diagram is an illustration. If you were to use it, who would be your audience? What would you use it to illustrate?

If you were testing by working through your expectations, and deciding whether your deliverable meets them or does not, what artefacts would support you in your work? How would you prepare? Who would need to know your results?

If you were testing by working through system behaviours, and noting whether they are expected or surprising, what artefacts would support you in your work? How would you prepare? Who would need to know your results?

What might you do with surprises or risks recognised while checking your expectations? What might you do if you could not find a way to satisfy an expectaton, when exploring the deliverable?

Do you consider this distinction in your current work? If you do, what do you already do about it? If you don't, what other choices do you make?

Does your organisation work typically in one way or the other? If it blends these approaches, how does it deal with that in terms of who concentrates where, how their work is received, and whether the organisation considers work in the intersection to be duplicated?

These boundaries look well-defined. Are they? What might a fuzzy, wobbly boundary mean? Does it even make sense to talk of a wobbly boundary? What's the difference betweent the boundary and the are it encloses? Are the enclosed areas equivalent-enough that one can reasonably put them on the same picture?

You might have different expectations. How would you illustrate that? You might find different behaviours. Would you illustrate that in a similar way?

You could add a third circle, for stuff you desired. Or stuf that might be useful. What other label might you use? What would the different parts of your diagram mean now?