Even before anyone starts thinking that I'm degrading the importance of the Definition of Done, let me assure you that this is not the case.
During any sprint planning and demo, the Definition of Done is treated as sacrosanct. Everybody in the Agile world tends to agree with the fact that the Definition of Done is highly important and that, without it, sprint planning can't be completed.
No doubt, the Definition of Done is important. Somehow, though, in sprint planning, the larger picture of the "Minimum Marketable Feature" is absolutely missing. In fact, it is not even one of the Scrum artifacts.
To explain why a definition of the Minimum Marketable Feature is important, I'd like to take an example that I've presented in an article titled A Real-Life Example of Agile
on this website.
In this example, I've explained how iterative delivery is important but that, at the same time, we also need to think about whether the iterative delivery is contributing to something that customers can use. The flyover in the cited article can be delivered iteratively without completing the one-way traffic path first.
The definition of the Minimum Marketable Feature will provide the blueprint for something that can be used by our sprint teams to pick up backlog items. An iterative delivery that doesn't lead to a Minimum Marketable Feature is simply a waste, as it cannot be used by anyone and no feedback can be obtained.
In my opinion, a definition of what constitutes a Minimum Marketable Feature should be defined with the product backlog, and all iterative increments should be aligned toward achieving it.
I'm steering my clients toward defining their Minimum Marketable Features, and they seem to like the idea.