In Agile, Scrum, in which situations is used the word "creep" ? Can I tag or define my stories added in an active sprint as creep?
In my current company, we work using Agile and Scrum methodologies. We try to respect the best practices but we also modified the method to fit our needs as recommended by Scrum itself. There are some things I do not agree to do but my product owner gives me no choice. My product owner sometimes adds urgent stories in active sprints. Our business requires it.
I want to be able to identify these stories that "break" the sprint. I wanted to tag them as "breaking stories" then I discovered the usage of the word "creep" and scope creep to identify all these features that increase the scope of a project during the project.
It seems that "scope creep" is used to identify all these requirements added to the scope, increasing the scope but that can be avoided. In my situation the added stories are very important for us. I cannot say no, I just can tell my product owner his management is bad and he should tell us the story in time.
Is there a way or a terminology that is given to such stories, requests, features? Is "creep" also ok. My objective is to use a good terminology for all members of the teams and my future reports. I must bring the idea, in my company, we have a problem with these stories. I must tag them, I must name them, I must evaluate them in my reports, I need to come with a good name and report to alert on the risk.
I don't want to open a debate here, I have the feeling something exists and some people already have the answer... You can just confirm that "creepy story" is the terminology.
I like the word but in my case the stories added by my business are not new features we can avoid. I have to say, the request are really urgent changes requested by our clients that require to be added at the last moment. For real, I cannot reject these stories.