Hi Rob, pleased to meet you. I came to reply to my 'Or / And' post but Roberts started a good topic here.
For me the 'InOrderTo' really needs to stay; "If you can't provide justification for this feature, then why are you even building it?" yeah that's it exactly Rob.
Actually i was going to suggest changing the order to "AsA->IWant->InOrderTo" but your putting the benefit first with that ordering!
Roberts story does become more justifyable with an InOrderTo there. There is still technical information, which might be no problem if the user is a developer, but I'm taking the stand point from the User Stories book that says keep technical details away
from stories. Should 'reading an app settings file' be 'reading configuration from file' or is that to general, to pedantic. Not sure just thinking out loud.
Yeah Robert the scenario...
Given the appSettingsFileReader
When the appSettingsFileReader.Read is excecuted
Then the result for $_appSettingsResult.AdminUserName should be $admin_username
And the result for $_appSettingsResult.AdminPassword should be $admin_password
It's too technical for me, it's steeped in Readers and method names. It's this as a unit test....
var appSettingsResult = appSettingsFileReader.Read();
But treating it as a scenario with StoryQ your splitting that up into 4 methods....Given, When and two Thens.
Any I hope this is helpful feedback...