I am familiar with using story boarding for both film projects and platform-based design processes. During my film project, storyboards act as anchors to frame scenes from a film to prompt discussion on cinematography and the overall mood of the film. I would find that this was transferable in the design field as a method for ambiguous design outcomes and as a point of ideation.
When the platform relates to complex interactions between the user, system, and software, there can often be ambiguous and gray areas that can be a barrier to how design or development can move forward. A storyboard can bring some clarity or at least get the conversation started, similar to wireframes and quick prototype techniques.
In software, the use of storyboards usually can be straightforward. I have come across situations where there was quite a bit of abstraction on how a feature of the software could be experienced by a potential user, with the use of a storyboard and a script a great deal of clarity was met.
Storyboards are great prompts to explore non-linear storytelling and experience that contribute to the creative process of the development of the medium. Storyboards are great tools to bring clarity to abstraction when working within the intangible when discussing user scenarios.