That's perfect - you get to write your own specs! :-)
- Developer: What's the spec for feature X?
- Marketing: Uhhh ... well, what does it do now?
- Developer: It should do foo, bar, and baz.
- Marketing: Ok, sounds good to me.
- Developer: Do you mind if I write that up and send it to you for a signature?
- Marketing: (worried tone) Why would you do that?
- Developer: Just so that if I screw up, you can hold my feet to the fire.
- Marketing: (relieved tone) Oh, ok!
So, you then write whatever you want, Marketing signs off on it, and you go write your test suite, refactor against it, and everyone goes home.
| [reply] [Watch: Dir/Any] |
| [reply] [Watch: Dir/Any] |
. . . in a organization of any significant size, it's generally a bad idea for developers to make unilateral decisions about how the product should be changed.
Yes, you are absolutely correct. Now, if only Marketing or the business units would get their heads out of the collective asses long enough to actually provide usable direction to us developers, we could all go home and have milk and cookies before naptime.
I have worked at 9 different places in the past 7 years. At 5 of them, developers wrote specifications. At 2 of them, developers co-wrote specifications. So, in less than a quarter of the places I have worked at, developers received usable specs.
I've been lucky.
| [reply] [Watch: Dir/Any] |