Comments on: How to Improve Your Scheduling http://blog.brodzinski.com/2006/08/how-to-improve-your-scheduling.html Dealing with software projects in real life Fri, 10 Feb 2012 19:07:34 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Pawel Brodzinski http://blog.brodzinski.com/2006/08/how-to-improve-your-scheduling.html#comment-1726 Pawel Brodzinski Sat, 29 Sep 2007 20:43:00 +0000 http://blog.brodzinski.com/2006/08/how-to-improve-your-scheduling.html#comment-1726 A good estimate can sound like "2 weeks, 75% chance" too. Yes, estimates have to have some uncertainty and people often forget about that, treating them as they were written in the stone.<br/><br/>Anyway, the optimistic end of estimated range is almost always, well, way too optimistic. A good estimate can sound like “2 weeks, 75% chance” too. Yes, estimates have to have some uncertainty and people often forget about that, treating them as they were written in the stone.

Anyway, the optimistic end of estimated range is almost always, well, way too optimistic.

]]> By: Bruce http://blog.brodzinski.com/2006/08/how-to-improve-your-scheduling.html#comment-1725 Bruce Thu, 27 Sep 2007 22:59:00 +0000 http://blog.brodzinski.com/2006/08/how-to-improve-your-scheduling.html#comment-1725 At the core of good scheduling is providing good estimates. One of the biggest problems is that as project team members we’re giving estimates like “2 weeks”. “2 weeks” isn’t really an estimate, it’s a guess, a prediction.<br/><br/>A good estimate is something like “1-4 weeks” or “3-5 days”. It really must be a range.<br/><br/>For more see this post on <a HREF="http://brucebrain.blogspot.com/2007/09/breaking-down-project-how-much-detail.html" REL="nofollow"> Breaking Down a Project: How Much Detail?</a>. At the core of good scheduling is providing good estimates. One of the biggest problems is that as project team members we’re giving estimates like “2 weeks”. “2 weeks” isn’t really an estimate, it’s a guess, a prediction.

A good estimate is something like “1-4 weeks” or “3-5 days”. It really must be a range.

For more see this post on Breaking Down a Project: How Much Detail?.

]]> By: Austin Bob http://blog.brodzinski.com/2006/08/how-to-improve-your-scheduling.html#comment-1724 Austin Bob Wed, 22 Nov 2006 04:47:00 +0000 http://blog.brodzinski.com/2006/08/how-to-improve-your-scheduling.html#comment-1724 And if there are any other bosses out there, think twice before you schedule unnecessary meetings or arbitrarily dictate unreasonable deadlines. Given the "right" (sic) motivation, an employee can alwasy meet the deadline ... it is a question, then, of what "meet the deadline" means in terms of software quality and completeness. You don't want to go there, because you have probably not prepared your minders for anything less than perfection.<br /><br />http://hither-and-yon.blogspot.com And if there are any other bosses out there, think twice before you schedule unnecessary meetings or arbitrarily dictate unreasonable deadlines. Given the “right” (sic) motivation, an employee can alwasy meet the deadline … it is a question, then, of what “meet the deadline” means in terms of software quality and completeness. You don’t want to go there, because you have probably not prepared your minders for anything less than perfection.

http://hither-and-yon.blogspot.com

]]>