Nice job distinguishing the concept of Fidelity and its usefulness across the spectrum of development approaches. I think the visuals really help.

In the last project on which I was a Scrum Coach, Fidelity was especially important in defining a new UI paradigm. Lower fidelity models built in an Agile fashion really help to educate customers and stakeholders on the important design elemens being presented without unnecessary debates about visuals elements that come with higher fidelity implementations.

I wonder if there is value in developing an exercise to practice building low fidelity solutions. It seems to me that it’s generally easier to visualize / design a full fidelity solution than a low fidelity one. But in general, you can save the business both time and money by providing a low fidelity solution first. In some cases you may be able to use the low fidelity solution to pay for development of a high fidelity one.

Anyway, those are just stray thoughts. Thanks for the great post!