Scenarios and Features
Product Development team define scenarios. Features are identified that will enable scenarios. Many time features are proposed directly as team has prior knowledge of missing feature.
During development cycle features get cut, changed. Team building feature lose focus on scenarios. It is important to pay attention to impact on scenarios. Any decision related to feature change, cut should consider impact on scenario.
You will see thousands of article emphasizing need to focus on scenario.
Here is opposite advice : Keep a Balance
When you work with team that are less technical, they focus on scenario and experience including UI screens and less priority is given to define featureset that will enable scenario
Here is an example:
A team need to deliver 3 scenarios using 3 month release. They discuss Actors, scenarios for 1 month.
In 2nd month too they discuss scenarios. In 3rd month they discussed screen and experience.
It is already late. If the scenario were just displaying information on screen they might get lucky, however if scenario require logic (e.g. recommendation engine, algorithm) team have missed it.
If scenario have non functional aspect such as Scalaing for X number of user, display page in < N sec - team have missed feature such as caching, compression. Because they only talked about scenario and not defined feature to enable the scenario.
Moral: Scenarios are VERY IMPORTANT. Features will be waste if these do not enable right scenarios!
If you only have worked on scenario and forget to design feature, it will be waste too as you have not enabled scenario