I need a good argument....
-
Why do you have a problem with writing down what you're going to do in plain language before you do it?
I wanna be a eunuchs developer! Pass me a bread knife!
Mark Wallace wrote:
Why do you have a problem with writing down what you're going to do in plain language before you do it?
What does that have to do with a user story? Wouldn't that be me writing down what a user would be doing? Assuming I'm not a user, what value is there in that?
Pete O'Hanlon wrote:
I'm looking forward to it; primarily because it should wipe that smug grin off Steve Jobs face.
-
I have a co-worker who is trying to push agile on everyone and it's getting to be a problem. I need a good argument to not have to write "user stories" other than "It's a complete waste of time and provides me nothing useful".
Pete O'Hanlon wrote:
I'm looking forward to it; primarily because it should wipe that smug grin off Steve Jobs face.
Arguing with religion is both futile and dangerous.
Christopher Duncan
www.PracticalUSA.com
Author of The Career Programmer and Unite the Tribes
Copywriting Services -
Why do you have a problem with writing down what you're going to do in plain language before you do it?
I wanna be a eunuchs developer! Pass me a bread knife!
it just confuses the issue
-
I have a co-worker who is trying to push agile on everyone and it's getting to be a problem. I need a good argument to not have to write "user stories" other than "It's a complete waste of time and provides me nothing useful".
Pete O'Hanlon wrote:
I'm looking forward to it; primarily because it should wipe that smug grin off Steve Jobs face.
Tell him he can do whatever he wants, then get back to work.
-
it just confuses the issue
You're right. It does have that in it's favour.
Henry Minute Do not read medical books! You could die of a misprint. - Mark Twain Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.”
-
I have a co-worker who is trying to push agile on everyone and it's getting to be a problem. I need a good argument to not have to write "user stories" other than "It's a complete waste of time and provides me nothing useful".
Pete O'Hanlon wrote:
I'm looking forward to it; primarily because it should wipe that smug grin off Steve Jobs face.
Work up the most intense wild-eyed gaze you can muster, and in a quiet, measured tone, tell him if he mentions it again, you'll be forced to punch him in the mouth. Whatever you do, don't smile. He'll take you seriously.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
Work up the most intense wild-eyed gaze you can muster, and in a quiet, measured tone, tell him if he mentions it again, you'll be forced to punch him in the mouth. Whatever you do, don't smile. He'll take you seriously.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
I have a co-worker who is trying to push agile on everyone and it's getting to be a problem. I need a good argument to not have to write "user stories" other than "It's a complete waste of time and provides me nothing useful".
Pete O'Hanlon wrote:
I'm looking forward to it; primarily because it should wipe that smug grin off Steve Jobs face.
User stories are a good method of communication between potential users and techs. Agile has much worse things. They have a good chance to catch the classic "this is not what I wanted" problem before any code is written if you use them to discuss the project with users As tech-to-tech spec, they are stupid - I agree with that. Beat him at his own game. Show him how agile is done right :cool:
Agh! Reality! My Archnemesis![^]
| FoldWithUs! | sighist | µLaunch - program launcher for server core and hyper-v server. -
I have a co-worker who is trying to push agile on everyone and it's getting to be a problem. I need a good argument to not have to write "user stories" other than "It's a complete waste of time and provides me nothing useful".
Pete O'Hanlon wrote:
I'm looking forward to it; primarily because it should wipe that smug grin off Steve Jobs face.
Actually, it's not a complete waste of time if done correctly (i.e. as an organization, not in isolation). The stakeholders (who typically aren't the developers) have to buy into, understand and follow the agile process, along with the devs, for it to be useful. Otherwise, it can easily lead to pure chaos. /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
I have a co-worker who is trying to push agile on everyone and it's getting to be a problem. I need a good argument to not have to write "user stories" other than "It's a complete waste of time and provides me nothing useful".
Pete O'Hanlon wrote:
I'm looking forward to it; primarily because it should wipe that smug grin off Steve Jobs face.
If you're a software developer, which I assume you are ... then you're not supposed to write user stories, the Product Owner does that, so ... as soon as you have a Product Owner, and they work the back log and write the necessary user stories, then you can start working on it. In the meantime, might I suggest taking some time off, whilst that co-worker of yours figures this out.
:..::. Douglas H. Troy ::..
Bad Astronomy |VCF|wxWidgets|WTL -
Grin with your mouth but your eyes and the rest of your face stay ice cold. Mixed up body language can really freak people out. [Evil grin]
Join the cool kids - Come fold with us[^]
It's tough to get that patented "crazy" grin. I've mastered it, but I didn't want to give too much to do in one lesson.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
I have a co-worker who is trying to push agile on everyone and it's getting to be a problem. I need a good argument to not have to write "user stories" other than "It's a complete waste of time and provides me nothing useful".
Pete O'Hanlon wrote:
I'm looking forward to it; primarily because it should wipe that smug grin off Steve Jobs face.
User stories can be great for testers but I've rarely seen them be much use for developers. I can use specs that tell me everything as form as to do. I don't have nearly as much use for a story telling me how Peggy in accounting will use the form.
Latest toys built for fun: 3D gravity simulation using xbap
full size Google image search. -
I have a co-worker who is trying to push agile on everyone and it's getting to be a problem. I need a good argument to not have to write "user stories" other than "It's a complete waste of time and provides me nothing useful".
Pete O'Hanlon wrote:
I'm looking forward to it; primarily because it should wipe that smug grin off Steve Jobs face.
-
Mark Wallace wrote:
Why do you have a problem with writing down what you're going to do in plain language before you do it?
What does that have to do with a user story? Wouldn't that be me writing down what a user would be doing? Assuming I'm not a user, what value is there in that?
Pete O'Hanlon wrote:
I'm looking forward to it; primarily because it should wipe that smug grin off Steve Jobs face.
Shelby Robertson wrote:
Wouldn't that be me writing down what a user would be doing?
No, it would be writing down the feature that you will be working on, and why you are working on it. If a user doesn't want what you're working on (which is so very often the case, with software), then don't do it. If you can't write, in plain language and from the user's perspective, what the item is wanted for and going to be used for, then you should have no say whatsoever in the features that are to be added to the product.
I wanna be a eunuchs developer! Pass me a bread knife!
-
Shelby Robertson wrote:
Wouldn't that be me writing down what a user would be doing?
No, it would be writing down the feature that you will be working on, and why you are working on it. If a user doesn't want what you're working on (which is so very often the case, with software), then don't do it. If you can't write, in plain language and from the user's perspective, what the item is wanted for and going to be used for, then you should have no say whatsoever in the features that are to be added to the product.
I wanna be a eunuchs developer! Pass me a bread knife!
Mark Wallace wrote:
No, it would be writing down the feature that you will be working on, and why you are working on it.
The project manager tells me what projects to work on...so in this case that does not apply.
Pete O'Hanlon wrote:
I'm looking forward to it; primarily because it should wipe that smug grin off Steve Jobs face.
-
Mark Wallace wrote:
No, it would be writing down the feature that you will be working on, and why you are working on it.
The project manager tells me what projects to work on...so in this case that does not apply.
Pete O'Hanlon wrote:
I'm looking forward to it; primarily because it should wipe that smug grin off Steve Jobs face.
The whole point of Agile is two-way communication with the user. It's fine if the PjM is doing this communcation, but in any case there should still be some kind of documentation, however brief, which describes the functionality that the user wants. If there is no two-way communication with the user don't bother pretending that it's Agile.