Most of us are familiar with the idea of scope creep--when the understanding of work grows, and the effort involved is larger than originally expected. A coworker was talking about the problem of scope creep and how it can be due to discovering technical debt in the codebase that needs to be addressed or it can be related to the complexity of business requirements. When this happens, he said, the user stories can be called "creepy." I love the term, and I wonder:
Does your product lead to a lot of creepy user stories?