|
Yes we are doing it during the sprint planning with days as unit. We are a team with 5 developers and it works fine. It is also good to enhance the quality of the bug/issue description. If we cannot estimate a bug, it means it is not good defined. If we estimate a bug for more than 5 days we understand we should split it, and so on.
|
|
|
|
|
We did at my previous company - IMHO about as effective as the magic 8-ball.
|
|
|
|
|
I've done it, but found the whole story point thing a mess. We ended up equating 1 point to 4 hours of work. But I always tried to call out 4 or 6 
Hogan
|
|
|
|
|
I do, we use it every week (refining stories one week & planning the next)
As a Scrum Master it is useful in as much as it allows me to estimate the work my team can complete in a two week sprint.
Sometimes it works really well, other times we over/under estimate, but it all evens out. Using poker and making sure that the team have a refined backlog that covers one and a half to two sprints of work allows me to make sure the team are fully occupied.
The second part to the Poker is making sure you get your velocity right for the team (another estimation) as giving them too much work is demoralising and giving too little means you are re-planning too often.
|
|
|
|
|
I used planning poker for a few months. I didn't find it offered much advantage over just talking about how long things would take. We never understood why some numbers were on cards, and others were not. It wasn't powers-of-two or fibonacci.
We were told not to equate numbers to days, but nobody could make estimates unless they did equate numbers to days. There was endless confusion and disagreement on whether it was or was not possible to consider tasks that took less than one day. Could you realistically schedule two half-day tasks in one day, or would unexpected add-ons prevent you ever succeeding at this?
The scrum master would beat us up if we estimated too high, so the estimates were always too low. We totalled up the number of engineer work days, and always scheduled this many days of projects, so we always ran over. We had sixty minute standups where the team watched the scrum master update TFS. We never looked back to compute our velocity. The team all knew we were scheduling too much work, but we weren't allowed to change the process.
We were agile in exactly the same way as a rhinocerous in ballet slippers.
|
|
|
|
|
You need an up-goer that burns fire water apparently. Proof.[^]
|
|
|
|
|
You really shouldn't goto space. You should break or return instead.
Funny how programming and rocket science are so similar, yet so different 
|
|
|
|
|
Why I stopped contributing here.
I posted an alternative to a tip, and someone told me my code wasn't PCL compliant. I said I didn't care, and that he had the technology to do it if it was that important to him. My response was down-voted. Granted, it was a low-rep user that down-voted the response, but still, whoever it was is breathing oxygen that an otherwise real programmer could be using.
Simply.F*cking.Amazing.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Ah, the old "bitch about it in The Lounge hoping that lots of people go and find the message and up-vote it to counter the down-vote" trick, eh. 
Down-vote countered. Happy now? 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
|
No, I just wanted to rant. Like I said, it was a low-rep voter. I don't give a flyin' rat f*ck if anyone up-votes my sh|t ever again, but unreasonable down-votes piss me right the f*ck off.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Don't hold back - tell us how you really feel!
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Richard Deeming wrote: Don't hold back - tell us how you really feel!
And then we can all mark his response as abusive. Oh, you are baaaddddd. 
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
RyanDev wrote: we can all mark his response as abusive
Speak for yourself!
He's got guns! 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
RyanDev wrote: And then we can all mark his response as abusive.
Or just ignore him altogether.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
|
|
|
|
|
DavidCrow wrote: Or just ignore him altogether.
Boring. 
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Let me get this straight: You don't want to contribute because someone asked for something you don't want to add, you tell them "You're a big boy - do it yourself" and they downvote you.
They downvote you??
Dear God. The ignominy! The nerve! The horror!
Is it the downvote, the anonymity of the downvote, the fact that they didn't like your answer, or the fact that they were arguing in the first place when you'd gone out of your way to give stuff away for free that's bugging you?
cheers
Chris Maunder
|
|
|
|
|
Sounds like StackOverflow.
i cri evry tiem
|
|
|
|
|
Chris Maunder wrote: the fact that they were arguing in the first place when you'd gone out of your way to give stuff away for free that's bugging you
More than any of the rest of what you mentioned, this.
However, complaining about sh*t they can certainly do themselves - being that they're supposed to be programmers in the first place - and then having the temerity to down-vote my response when I mention that is what pisses me off (and I even did it without too much gnashing of teeth).
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Chris Maunder wrote: They downvote you??
If you think about it, it's really your fault. 
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
I've had a long, hard talk with myself about this. Again.
(frankly I'm not sure how willing I'm willing to put up with this attitude of mine.)
cheers
Chris Maunder
|
|
|
|
|
The rest of us have to put up with it. Why should you be exempt.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Now you're just being cruel.
cheers
Chris Maunder
|
|
|
|
|
Did you expect anything less?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Chris Maunder wrote: (frankly I'm not sure how willing I'm willing to put up with this attitude of mine.)
Yeah, it really sucks when you downvote yourself. 
Marc
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
