[Mr. Douglas]

Project Roadmap

Scope Creep

Small Wins

Reporting Metrics

Shifting Priorities

Project Refresh

Performance Benchmarks

---

I think most of those are bad because they are squishy terms. What does “reporting metrics” really mean, anyway.

But as a Business Analyst, I use the phrase “scope creep” all the time. Usually I’ll say, as someone wants to add functionality after the development phase has begun, “that sounds kinda scope creepy.” “Scope Creep” communicates a clear position.

[Bloody Sam Roberts]

Numbers 14 (Bottom line), 20 (Benchmark) and 32 (Action plan ) aren't really jargon. They are normal terms that describe definite items and have been in use for a very, very long time.

Now, in today's business/corporate environment that is populated largely by mis-educated illiterates, their usage is not at all proper.

[ConservativeWarrior]

Fair enough. haha

Sometimes, from the customer side, “scope creep” can annoy me. Usually when an assumed element of a project is not included and attempts are made to increase costs due to “scope creep”.

“What? You wanted tires on your car? Scope creep.”

I’m sure there’s a balance somewhere in the middle. :)

[M1903A1]

Sfl....