Thoughts on technology and innovation
Ted Husted, Release Engineer
The best way to avoid losing the benefit is to write benefit-driven stories.
Of course, Yoda phrasing gets pretty annoying pretty quick. Here's an actual user story of mine from an internal RFC:
Some folks refer to this sort of thing as "Feature Injection".
For more, see
Do you work from user stories? Do you sometimes find yourself scratching your head, and wondering why? Do you think benefit-first user stories would help you design better software?
Ted Husted is a Kaizen Squad developer on the Nimble AMS product crew. "We make the good changes that create a great product."