There continues to be some confusion over the definition and meaning of scenario in MSF. We know this is causing some pain for our customers. It's been pointed out to me that Scott Ambler has a definition of usage scenario in his agile modeling body of knowledge. This is fueling the confusion.

Last Tuesday I offered our new definitive definition of scenario in MSF. Scenario in MSF is indeed short for usage scenario but those usage scenarios have nothing to do with legacy from OOSE and the requirements and analysis technique called use cases. There are no use cases in MSF. MSF does not describe procedures of interaction in the system architecture. And there are no abstract analysis concepts such as actors and the use cases they perform. MSF uses very specific, detailed definitions called personas and scenarios. I hope this helps to clear up any confusion. Technorati tag: Agile, David+Anderson, MSF