http://malvasiabianca.org/archives/2006/10/benefits-of-slack/ Tue, 22 May 2012 01:20:09 +0000 hourly 1 http://wordpress.org/?v=3.3.2 http://malvasiabianca.org/archives/2006/10/benefits-of-slack/comment-page-1/#comment-7392 malvasia bianca » Blog Archive » response time Sun, 05 Nov 2006 23:03:53 +0000 http://malvasiabianca.org/archives/2006/10/benefits-of-slack/#comment-7392 [...] Of course, there are more levels to this problem: in particular, we shouldn’t be inserting defects into our code in the first place. (We’re getting better at that, fortunately.) And we don’t want to use Bugzilla as a substitute for our product backlog: there should be some control over how features get scheduled for implementation. And it can be hard to maintain a steady implementation pace if you’re getting constantly interrupted by bug work. There are solutions to all these problems, however. (E.g. for the latter, a two-part strategy of not writing defects in the first place and allocating slack in your schedule in the second place.) For now, from my point of view, our most urgent issues are (first) reducing the defect backlog and (second) improving response time. [...] [...] Of course, there are more levels to this problem: in particular, we shouldn’t be inserting defects into our code in the first place. (We’re getting better at that, fortunately.) And we don’t want to use Bugzilla as a substitute for our product backlog: there should be some control over how features get scheduled for implementation. And it can be hard to maintain a steady implementation pace if you’re getting constantly interrupted by bug work. There are solutions to all these problems, however. (E.g. for the latter, a two-part strategy of not writing defects in the first place and allocating slack in your schedule in the second place.) For now, from my point of view, our most urgent issues are (first) reducing the defect backlog and (second) improving response time. [...]

]]>