Thanks for sharing your question Ayushi. I am sorry that you found the the wording confusing. The sentence wants to say that you should regularly demo or release product increments to the stakeholders. Hope this helps!

Thanks for sharing your question John. An example of a user interaction assumption for a healthy eating product would be that users are willing to share personal information like gender, age, weight, and dietary requirements before they start using the app. If this assumption turned out to be wrong, then users might not engage with the app. It would therefore be advisable to validate the assumption and select an appropriate sprint goal, for example, “Test that people are willing to share personal information before using the main features of the app”. Does this help?

Once the sprint goal has been selected, the team develops the appropriate product increment. This could be a throw-away prototype (such as a paper prototype or a spike) or working software that can be released —depending on what’s best to meet the sprint goal. A paper prototype might be best, for instance, to test assumptions about the user interactions .

What do you mean by this?

Hi Nick, Thanks for your feedback. I am not a DSDM Atern expert but I find it helpful to work with cycles that focus on exploration/experimentation or on delivery, as I have described in this post: http://www.romanpichler.com/blog/learning-and-execution-in-scrum/ Does this help?