Discovery Principle 7/10: Include feasibility!

Simply put, teams need to validate the feasibility of their upcoming features or products during discovery, not after.

Teams that tackle feasibility risks in their feasibility sprints will go through many surprises, impediments and issues. It will ruin the team's predictability and put the team in a situation of constant failure.

Involving developers and engineering during discovery also greatly benefits teams: most innovations come from engineers, not clients or executives. So they tend to be excellent catalysts to improve features and products!