Book a Demo

Author Topic: Feature v.s. requirement  (Read 12864 times)

mikewhit

  • EA User
  • **
  • Posts: 608
  • Karma: +0/-0
  • Accessing ....
    • View Profile
Re: Feature v.s. requirement
« Reply #15 on: March 06, 2007, 08:51:20 am »
Pragmatic: Deliver what they'll pay for. Might not be the same as what they want or need.

JohnWSaundersIII

  • EA User
  • **
  • Posts: 50
  • Karma: +0/-0
    • View Profile
Re: Feature v.s. requirement
« Reply #16 on: March 07, 2007, 11:06:59 am »
Quote
Pragmatic: Deliver what they'll pay for. Might not be the same as what they want or need.


Even more pragmatic: deliver what they'll pay for today, and what they won't sue you for in the future.

John
John Saunders

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Feature v.s. requirement
« Reply #17 on: March 07, 2007, 02:02:30 pm »
Quote

Even more pragmatic: deliver what they'll pay for today, and what they won't sue you for in the future.

John
Took the words right out of my mouth...

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

sargasso

  • EA Practitioner
  • ***
  • Posts: 1406
  • Karma: +1/-2
  • 10 COMFROM 30; 20 HALT; 30 ONSUB(50,90,10)
    • View Profile
Re: Feature v.s. requirement
« Reply #18 on: March 08, 2007, 12:50:10 am »
Quote
deliver what they'll pay for today, and what they won't sue you for in the future.


Is this what's writ in large lettres on Geoff's wall???  ;D ;D ;D
« Last Edit: March 08, 2007, 12:51:49 am by sargasso »
"It is not so expressed, but what of that?
'Twere good you do so much for charity."

Oh I forgot, we aren't doing him are we.

mikewhit

  • EA User
  • **
  • Posts: 608
  • Karma: +0/-0
  • Accessing ....
    • View Profile
Re: Feature v.s. requirement
« Reply #19 on: March 08, 2007, 01:14:39 am »
Read the small print:
Settlement of invoice in full implies acceptance of project deliverables according to contract.

sargasso

  • EA Practitioner
  • ***
  • Posts: 1406
  • Karma: +1/-2
  • 10 COMFROM 30; 20 HALT; 30 ONSUB(50,90,10)
    • View Profile
Re: Feature v.s. requirement
« Reply #20 on: March 08, 2007, 01:51:45 am »
Even smaller print:

[size=10]ANYTHING, Mr Project Manager, you say in a project meeting will cause an immediate and priority 1 level event: ChangeRequest(<insert $$$ here)[/size]

::)
"It is not so expressed, but what of that?
'Twere good you do so much for charity."

Oh I forgot, we aren't doing him are we.

sl@sh

  • EA User
  • **
  • Posts: 85
  • Karma: +0/-0
    • View Profile
Re: Feature v.s. requirement
« Reply #21 on: March 09, 2007, 04:42:55 am »
Quote
Clue: Deliver what the b@st@rds "want", not what they "need". The science is in manipulating that which they "say" they want, into what they "mean" they want.  

----------
FWIW
bruce

Disagreed. In doing this you replace one set of features with another set of features that you think fulfil the customers *need* better than the set of features the customers originally wanted. You implicitely refer to the requirements anyway, so why not work them out with the customer?

Quote
amended..
Blooddy hell! thet was ret too obscure for even me, leddie.  I just meant that "we" have no right in determining what the user really "needs" just that they have goal to achieve.

That's not what I meant.

I don't claim the right to declare what the customers needs. What I quoted was from a customer, not from my company that was supposed to deliver the system. The customer - with a wink and smile - simply hinted at the fact he was very well aware of his inability to properly define his needs and talked in features instead. He basically asked us to translate them for him into proper requirements. And we did. With his help.

Quote
Its our job to (somehow)understand that goal and make it easier for them to achieve it.

Agreed on that one.

Stefan