And here's what we got:
I despise scope creep with every part of my being. To me, scope creep is comparable to nails on a chalk board, or having my hand slammed in a door again and again and again. It is the ruiner of projects, products, and I’m sure I could find some way to tie it into how Rock and/or Roll music is obviously ruining society. It takes what would in most cases be a solid project, a solid time line, and solid analysis, and tosses them all to the winds.
A quick, simple, and generalized definition: Scope Creep is when someone (yourself or otherwise) adds new functionality, features, or other additions while still expecting your project/product/whatever to still be due by the same time.
I went to college.
Shocking, I know. I did though, and on the lovely diploma that I earned and gently stuffed in a drawer somewhere it says that I am both a computer programmer and a systems analyst. What that means is not only am I (supposedly) competent at coding solutions, I am also (apparently) competent at looking at a system and figuring out how things should work.
I always chuckled in my Analysis classes. “Come on, this is all common sense!” I would proclaim. I took what the teacher said for a grain of salt and left it at that.