I’m currently thinking about using scenarios more/better in our design process. Using them for community involvement at Wikidata seemed to work, and they also seem to do a good job in bridging research and concept work (and also allow to loop back; see "5 Reasons for Scenario Based Design" (pdf))
Do you have worked with scenarios in the past and possibly have some examples to share? – ideally under CC-BY or CC0, so they can be reused as examples easily.
I have created and used a scenario for a small usability session I’ve run with 9 users. The scenario is available here http://design.xwiki.org/xwiki/bin/view/Proposal/UsabilityScenario4
The task completion is available here http://design.xwiki.org/xwiki/bin/view/Proposal/UsabilityScenario4TaskStatus
and some conclusions, issues reported back to the development team presented here http://design.xwiki.org/xwiki/bin/download/Proposal/UsabilityScenario4Report/UsabilityReportScenario4.pdf
Not sure is the best scenario or the most successful / relevant, but there were some interesting results 
@evalica: Thanks a lot!
So you used them to define what people should attempt to do in a usability test, if I understand it right?
On twitter (via @peter_works) we got the metapolator scenarios meant to be “…the ‘paths to wonder along’ during expert evaluations”
Yes. That was just 1 example, there are multiple scenarios that I did. It all depends on what functionality / use case you are testing. But some parts are common.
For a usability test I collaborated with Ubuntu on for their photo manager, we had a really simple and broad scenario. This helped with people not being led by any terminology or specific commands. Of course this is also an advantage because a photo manager/editor is a pretty everyday tool.
@jtmorgan liked me these scenarios on anticipated use on Wikipedia’s “Tea house”. They are nice examples for detailed, narrative scenarios and they also show how you can make those accessible (each has a summary).
I use scenarios for pretty much every new feature I design for Cockpit. I feel they are good for keeping the discussion with the developers focused and get a common understanding of what we want to build and for who.
I didn’t write all of these, the ABRT one is written by the developer who needed that, as a tool to make me understand what they need from the design.
Some examples:
I wrote a little blogpost on scenarios, quoting the examples posted here and giving some background on possible use and research on scenarios: http://fordes.de/posts/usingscenariosindesign.html (If you find your example not described correctly, drop me a line!)