https://www.mountaingoatsoftware.com/blog/not-everything-needs-to-be-a-user-story-using-fdd-features

 

 

Here’s an older article by Mike Cohn where he talks about how to handle user stories that are more focused on back-end features and do not have custome-facing components. He advocates for a different syntax for these stories, leveraging FDD as example. Instead of saying “As a developer…” or “As a product owner…” say something like  “Merge the data for duplicate transactions” (<action> the <result> <by!for!of!to> <object>)

 

What does everyone think of this approach? How do you handle these types of user stories in your backlog?

 

 

 

 

Thanks!

 

Bob Shirley

Team Lead, PMO

Library of Congress

(202) 707-0166