Comments on: Quality against a deadline http://lostechies.com/jimmybogard/2009/04/09/quality-against-a-deadline/ Strong opinions, weakly held Thu, 23 May 2013 23:40:00 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: Jon Kruger http://lostechies.com/jimmybogard/2009/04/09/quality-against-a-deadline/#comment-1422 Jon Kruger Thu, 09 Apr 2009 22:48:18 +0000 /blogs/jimmy_bogard/archive/2009/04/08/quality-against-a-deadline.aspx#comment-1422 I think you're right, but there's a problem here that needs to be fixed, and the problem is that people are expecting too much to get done in the fixed amount of time. I know that we can't always avoid this situation, but I'm trying to find ways to set realistic expectations up front so that you're more likely to avoid these situations. I think you’re right, but there’s a problem here that needs to be fixed, and the problem is that people are expecting too much to get done in the fixed amount of time. I know that we can’t always avoid this situation, but I’m trying to find ways to set realistic expectations up front so that you’re more likely to avoid these situations.

]]> By: bogardj http://lostechies.com/jimmybogard/2009/04/09/quality-against-a-deadline/#comment-1421 bogardj Thu, 09 Apr 2009 20:26:00 +0000 /blogs/jimmy_bogard/archive/2009/04/08/quality-against-a-deadline.aspx#comment-1421 @Darrell After a release, it's common to have a post-mortem to talk and analyze how things went down. This is in addition to our normal retrospectives and other feedback. @Darrell

After a release, it’s common to have a post-mortem to talk and analyze how things went down. This is in addition to our normal retrospectives and other feedback.

]]> By: Jeff Certain http://lostechies.com/jimmybogard/2009/04/09/quality-against-a-deadline/#comment-1420 Jeff Certain Thu, 09 Apr 2009 13:42:39 +0000 /blogs/jimmy_bogard/archive/2009/04/08/quality-against-a-deadline.aspx#comment-1420 @Scott Muc, Depends on your management team. I'm fortunate enough to work for a company that has a product that has been around for a very long time. Management has seen first-hand how big a time sink maintaining a complex code base can be. It makes it fairly easy to make the argument for allowing developers time to refactor and reduce technical debt. @Scott Muc,

Depends on your management team. I’m fortunate enough to work for a company that has a product that has been around for a very long time. Management has seen first-hand how big a time sink maintaining a complex code base can be. It makes it fairly easy to make the argument for allowing developers time to refactor and reduce technical debt.

]]> By: Scott Muc http://lostechies.com/jimmybogard/2009/04/09/quality-against-a-deadline/#comment-1419 Scott Muc Thu, 09 Apr 2009 05:45:49 +0000 /blogs/jimmy_bogard/archive/2009/04/08/quality-against-a-deadline.aspx#comment-1419 @Darrell Mozingo, I like the concept of a "feature breather". It's hard to convince higher ups that it needs doing because they can't perceive the benefits... nor can they ever because the benefits are purely for the developer. The developer benefits need to be translated into some sort of business value which is the one area that drives me nuts. @Darrell Mozingo, I like the concept of a “feature breather”. It’s hard to convince higher ups that it needs doing because they can’t perceive the benefits… nor can they ever because the benefits are purely for the developer. The developer benefits need to be translated into some sort of business value which is the one area that drives me nuts.

]]> By: Darrell Mozingo http://lostechies.com/jimmybogard/2009/04/09/quality-against-a-deadline/#comment-1418 Darrell Mozingo Thu, 09 Apr 2009 03:49:55 +0000 /blogs/jimmy_bogard/archive/2009/04/08/quality-against-a-deadline.aspx#comment-1418 Thanks, this was quite timely. We're facing a similar situation right now, and we're slowly but surely loosening up those control gates. How do you handle after the deadline passes though? Do you push for a refactoring iteration or two? Work it in (via padding) to future iterations? How do you communicate the need to take a feature breather to go back and fix things up for a large and long lived project? Thanks, this was quite timely. We’re facing a similar situation right now, and we’re slowly but surely loosening up those control gates.

How do you handle after the deadline passes though? Do you push for a refactoring iteration or two? Work it in (via padding) to future iterations? How do you communicate the need to take a feature breather to go back and fix things up for a large and long lived project?

]]> By: jdn http://lostechies.com/jimmybogard/2009/04/09/quality-against-a-deadline/#comment-1417 jdn Thu, 09 Apr 2009 02:52:20 +0000 /blogs/jimmy_bogard/archive/2009/04/08/quality-against-a-deadline.aspx#comment-1417 I think this is very well stated. Thanks. I think this is very well stated.

Thanks.

]]>