Comments on: Practical Process Improvement (Part 4) http://blog.nwcadence.com/2008/11/practical-process-improvement-part-4/ Thoughts on VSTS, Sharepoint and other collaborative technologies Thu, 28 May 2009 13:06:24 -0700 http://wordpress.org/?v=2.8.4 hourly 1 By: Practical Process Improvement (Part 5) :: Where Technology Meets Teamwork http://blog.nwcadence.com/2008/11/practical-process-improvement-part-4/comment-page-1/#comment-97 Practical Process Improvement (Part 5) :: Where Technology Meets Teamwork Sat, 27 Dec 2008 02:24:49 +0000 http://blog.nwcadence.com/?p=153#comment-97 [...] first four posts (Part 1, Part 2, Part 3, Part 4) dealt with working through a process for handling bugs and improving that process. But what about [...] [...] first four posts (Part 1, Part 2, Part 3, Part 4) dealt with working through a process for handling bugs and improving that process. But what about [...]

]]> By: Jeff Levinson http://blog.nwcadence.com/2008/11/practical-process-improvement-part-4/comment-page-1/#comment-91 Jeff Levinson Thu, 11 Dec 2008 13:52:10 +0000 http://blog.nwcadence.com/?p=153#comment-91 That's a good thought Monte and I'll have to think about it. The thought process here is that the bug that wasn't fixed would be assigned back to the developer since this was a priority bug for this iteration and it didn't need to go back to the PM for re-assignment. But I can see that in some cases this is not a bad option at all. I'll update the post when I get time. That’s a good thought Monte and I’ll have to think about it. The thought process here is that the bug that wasn’t fixed would be assigned back to the developer since this was a priority bug for this iteration and it didn’t need to go back to the PM for re-assignment. But I can see that in some cases this is not a bad option at all. I’ll update the post when I get time.

]]> By: montebertrand http://blog.nwcadence.com/2008/11/practical-process-improvement-part-4/comment-page-1/#comment-90 montebertrand Wed, 10 Dec 2008 09:48:11 +0000 http://blog.nwcadence.com/?p=153#comment-90 RE: "A tester will note that the bug fix has been verified. If the bug has not been fixed, a tester can also re-assign the bug to a developer." I have always found it better to go back to the PM. It avoids the conflict of testers being able to overload a single developer with work that he doesn't have bandwidth for ... but does this create waste? RE: “A tester will note that the bug fix has been verified. If the bug has not been fixed, a tester can also re-assign the bug to a developer.”

I have always found it better to go back to the PM. It avoids the conflict of testers being able to overload a single developer with work that he doesn’t have bandwidth for … but does this create waste?

]]> By: RamS http://blog.nwcadence.com/2008/11/practical-process-improvement-part-4/comment-page-1/#comment-89 RamS Wed, 03 Dec 2008 06:32:56 +0000 http://blog.nwcadence.com/?p=153#comment-89 Jeff, It was great to meet you at the SeaSPIN presentation this evening. -Ram Jeff,
It was great to meet you at the SeaSPIN presentation this evening.
-Ram

]]> By: Team System News : VSTS Links - 11/18/2008 http://blog.nwcadence.com/2008/11/practical-process-improvement-part-4/comment-page-1/#comment-85 Team System News : VSTS Links - 11/18/2008 Tue, 18 Nov 2008 14:25:24 +0000 http://blog.nwcadence.com/?p=153#comment-85 [...] NorthWest Cadence Blog on Practical Process Improvement (Part  4) and VSTS 2008 Team Suite with MSDN Professional for $3000 Published Tuesday, November 18, 2008 [...] [...] NorthWest Cadence Blog on Practical Process Improvement (Part  4) and VSTS 2008 Team Suite with MSDN Professional for $3000 Published Tuesday, November 18, 2008 [...]

]]>