Development Speak nonsense

So, after the past few months I have heard many phrases said in development/management meetings, I thought I would just write them down so others can understand their meanings;

When I say… I actually mean…..
The schedule is aggressive Shit, doubt we can do that
We will makeup the slippage in the next few iterations Bugger, what can we miss out to ensure it gets in
Executive summary Fairytale version
The code base is unscalable I would have designed it differently
Work continues We don't really know, but we may have a small issue
Time will tell We are clueless and we admit it
Code complete Not actually tested, lets just see what happens
x Points Meh, sounds like a good figure, but try putting a cost on that!
Best practice Invented by people who do not work here and whom don't actually have a clue
Passed all testing 92% pass rate, not sure what the 8% failures were, but should work well
6 Month Iteration plan This'll keep you happy for a while, we don't actually have a plan after 2!
High-Level Not a clue, but sounds like a good figure
 
When I say… I actually mean…..
The schedule is aggressive Shit, doubt we can do that
We will makeup the slippage in the next few iterations Bugger, what can we miss out to ensure it gets in
Executive summary Fairytale version
The code base is unscalable I would have designed it differently
Work continues We don't really know, but we may have a small issue
Time will tell We are clueless and we admit it
Code complete Not actually tested, lets just see what happens
x Points Meh, sounds like a good figure, but try putting a cost on that!
Best practice Invented by people who do not work here and whom don't actually have a clue
Passed all testing 92% pass rate, not sure what the 8% failures were, but should work well
6 Month Iteration plan This'll keep you happy for a while, we don't actually have a plan after 2!
High-Level Not a clue, but sounds like a good figure
 
Show Comments