The Art of Escalation in Software Requirement Meetings

Maybe you've dealt with The Escalator before. The conversations with The Escalator go something like this:

"Now, what about this scenario? This is a very high-priority scenario for our users. We have to have this feature in the next release".

"We costed that scenario, and we don't have the time in this release".

"But this is a high priority scenario."

"Every feature in this iteration is high priority".

"You don't understand, our user's can't do their jobs without this feature. If we don't deliver this, the project will fail".

"But, it was never that important before…"

"Look – if we don't deliver this – I … will … lose … my … job".

<blank stares>

"Please! For the love of God! The mafia will kill my family!" <tears>

"Um … ok. We might be able to bump something and squeeze it in…"

"Great! Now, about this other scenario. This is a very high-priority scenario for our users. We have to have this feature in the next release…."

Print | posted @ Tuesday, September 19, 2006 3:39 AM

Comments on this entry:

Gravatar # re: The Art of Escalation in Software Requirement Meetings
by Haacked at 9/19/2006 4:44 AM

That's so painful because it's TRUE.
  
Gravatar # re: The Art of Escalation in Software Requirement Meetings
by William at 9/19/2006 6:45 AM

The familiarity scares me... *shock*
  
Gravatar # re: The Art of Escalation in Software Requirement Meetings
by Sahil Malik at 9/19/2006 2:49 PM

LOL Man, funny true !! ROFL !! :)
  
Gravatar # re: The Art of Escalation in Software Requirement Meetings
by Moz at 9/20/2006 12:49 AM

The best bit is when they say "I could lose my job" and you go "sounds like a win-win".
  
Gravatar # re: The Art of Escalation in Software Requirement Meetings
by scott at 9/20/2006 2:54 AM

... or break into a fit of laughter :)
  
Comments have been closed on this topic.
Scott Allen
Posts - 869
Comments - 4493
Stories - 14