http://www.gettingagile.com/2008/02/16/product-owner-tells-in-planning-poker/ with Sterling Barton Sun, 04 Jul 2010 16:55:57 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://www.gettingagile.com/2008/02/16/product-owner-tells-in-planning-poker/comment-page-1/#comment-66 Chris Sterling Sat, 20 Dec 2008 04:26:57 +0000 http://chrissterling.gettingagile.com/2008/02/16/product-owner-tells-in-planning-poker/#comment-66 If that is working for you and the rest of the team than I would never ask you to change something that works. Have fun and good luck. If that is working for you and the rest of the team than I would never ask you to change something that works. Have fun and good luck.

]]> http://www.gettingagile.com/2008/02/16/product-owner-tells-in-planning-poker/comment-page-1/#comment-67 Agile Bloke Thu, 18 Dec 2008 10:25:48 +0000 http://chrissterling.gettingagile.com/2008/02/16/product-owner-tells-in-planning-poker/#comment-67 We do agile but never used planning poker. I get the estimates done by senior tech people on the team who do detailed analysis and come up with detailed work break down and the estimates (in days not story points). The estimates are then peer reviewed by other senior techies. We create iterations and schedule requirements within iterations beased on effort and risks. This works like a dream. The product is complex, requirements (stories) are complex and not everyone on the team knows the details all the requirements at the beginning of the release. Once estimates are done we work like normal agile. Till now we have not missed a single release deadline and have completed all initially committed requirements for a release. So why should I use planning poker? We do agile but never used planning poker. I get the estimates done by senior tech people on the team who do detailed analysis and come up with detailed work break down and the estimates (in days not story points). The estimates are then peer reviewed by other senior techies. We create iterations and schedule requirements within iterations beased on effort and risks. This works like a dream. The product is complex, requirements (stories) are complex and not everyone on the team knows the details all the requirements at the beginning of the release. Once estimates are done we work like normal agile. Till now we have not missed a single release deadline and have completed all initially committed requirements for a release.
So why should I use planning poker?

]]> http://www.gettingagile.com/2008/02/16/product-owner-tells-in-planning-poker/comment-page-1/#comment-65 Bryan Smith Mon, 03 Mar 2008 17:56:49 +0000 http://chrissterling.gettingagile.com/2008/02/16/product-owner-tells-in-planning-poker/#comment-65 Interesting variation on jazz hands ... In our scrums we have estimated via "rochambeau", counting to three and holding out a finger-based estimation. "Jazz Hands" is when someone throws down all ten digits, indicating an inability to estimate the story as currently defined -- too many unknowns to know. Interesting variation on jazz hands … In our scrums we have estimated via “rochambeau”, counting to three and holding out a finger-based estimation. “Jazz Hands” is when someone throws down all ten digits, indicating an inability to estimate the story as currently defined — too many unknowns to know.

]]> http://www.gettingagile.com/2008/02/16/product-owner-tells-in-planning-poker/comment-page-1/#comment-64 Product Owner “Tells” in Planning Poker Sun, 17 Feb 2008 21:11:32 +0000 http://chrissterling.gettingagile.com/2008/02/16/product-owner-tells-in-planning-poker/#comment-64 [...] maverickusc@gmail.com wrote an interesting post today onHere’s a quick excerptMany of you may have heard of Planning Poker for estimating your Product Backlog items. Each team member gets their own set of cards with sizes identified on them in either story points (1, 2, 3, 5, 8, 13…) or t-shirt sizes (XS, S, M, … [...] [...] maverickusc@gmail.com wrote an interesting post today onHere’s a quick excerptMany of you may have heard of Planning Poker for estimating your Product Backlog items. Each team member gets their own set of cards with sizes identified on them in either story points (1, 2, 3, 5, 8, 13…) or t-shirt sizes (XS, S, M, … [...]

]]>