Comments on: Scheduling Accuracy http://www.productbeautiful.com/2006/10/20/scheduling-accuracy/ Building Product Management from the Ground Up by Paul Young Thu, 26 Aug 2010 18:07:46 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Product Beautiful » Blog Archive » Problems of Estimation http://www.productbeautiful.com/2006/10/20/scheduling-accuracy/comment-page-1/#comment-1286 Product Beautiful » Blog Archive » Problems of Estimation Mon, 10 Dec 2007 17:24:55 +0000 http://www.productbeautiful.com/2006/10/20/scheduling-accuracy/#comment-1286 [...] issues I have seen a development team experience have been problems of estimation, not delivery. Estimation and delivery are explicitly linked - give a team forever and they can solve any problem, but the rest of the business can’t wait [...] [...] issues I have seen a development team experience have been problems of estimation, not delivery. Estimation and delivery are explicitly linked – give a team forever and they can solve any problem, but the rest of the business can’t wait [...]

]]> By: Product Beautiful » Blog Archive » Paul’s 3rd Postulate of Product Management http://www.productbeautiful.com/2006/10/20/scheduling-accuracy/comment-page-1/#comment-84 Product Beautiful » Blog Archive » Paul’s 3rd Postulate of Product Management Thu, 08 Feb 2007 08:16:11 +0000 http://www.productbeautiful.com/2006/10/20/scheduling-accuracy/#comment-84 [...] This is the 3rd in my series of The Postulates of Product Management. Closely related to an earlier post about accuracy in scheduling, this also deals with Development: Development’s initial estimate of time to develop a product or feature will be at least 50% aggressive or 50% conservative. [...] [...] This is the 3rd in my series of The Postulates of Product Management. Closely related to an earlier post about accuracy in scheduling, this also deals with Development: Development’s initial estimate of time to develop a product or feature will be at least 50% aggressive or 50% conservative. [...]

]]> By: Paul http://www.productbeautiful.com/2006/10/20/scheduling-accuracy/comment-page-1/#comment-47 Paul Sat, 02 Dec 2006 06:52:43 +0000 http://www.productbeautiful.com/2006/10/20/scheduling-accuracy/#comment-47 That's good feedback, it probably should only be log on the X axis, to denote that accuracy increases exponentially and you see more detail (the log lines) as you get closer to the eventual release date. That’s good feedback, it probably should only be log on the X axis, to denote that accuracy increases exponentially and you see more detail (the log lines) as you get closer to the eventual release date.

]]> By: Chris http://www.productbeautiful.com/2006/10/20/scheduling-accuracy/comment-page-1/#comment-46 Chris Sat, 02 Dec 2006 05:46:31 +0000 http://www.productbeautiful.com/2006/10/20/scheduling-accuracy/#comment-46 Hey, I hate to say this, but that graph is using a log scale and I can't figure out what it would look like on a normal (linear) scale... Great idea, but not very careful use of a background! Nice post otherwise, I learned something. Hey, I hate to say this, but that graph is using a log scale and I can’t figure out what it would look like on a normal (linear) scale… Great idea, but not very careful use of a background!

Nice post otherwise, I learned something.

]]> By: Prod Mktg VIP http://www.productbeautiful.com/2006/10/20/scheduling-accuracy/comment-page-1/#comment-11 Prod Mktg VIP Sat, 28 Oct 2006 01:31:16 +0000 http://www.productbeautiful.com/2006/10/20/scheduling-accuracy/#comment-11 Oh, btw, Loved the graph. That's a great representation of what SHOULD happen. Unfortunately it's tough to achieve. Oh, btw, Loved the graph. That’s a great representation of what SHOULD happen. Unfortunately it’s tough to achieve.

]]> By: Prod Mktg VIP http://www.productbeautiful.com/2006/10/20/scheduling-accuracy/comment-page-1/#comment-10 Prod Mktg VIP Sat, 28 Oct 2006 01:30:35 +0000 http://www.productbeautiful.com/2006/10/20/scheduling-accuracy/#comment-10 I work off of 3 different dates. Engineering gives me a date, I push back and we finally agree on an uncomfortable 10/1 launch. I then tell marketing that the launch is 10/15 but that they need to pretend that it's 10/1. And Marketing tells sales that its 10/31. Ultimately we always hit the marketing date. Development guys are terrible and we all know that. I use marketing to put pressure on the guys. I work off of 3 different dates. Engineering gives me a date, I push back and we finally agree on an uncomfortable 10/1 launch. I then tell marketing that the launch is 10/15 but that they need to pretend that it’s 10/1. And Marketing tells sales that its 10/31.

Ultimately we always hit the marketing date. Development guys are terrible and we all know that. I use marketing to put pressure on the guys.

]]>