Comments on: Mastering the Hand-off http://webgambit.com/2008/02/12/mastering-the-hand-off/ Thoughts on Software Development from Karthik Hariharan Fri, 27 Nov 2009 00:11:26 -0700 http://wordpress.org/?v=2.8.4 hourly 1 By: Karthik http://webgambit.com/2008/02/12/mastering-the-hand-off/comment-page-1/#comment-101 Karthik Tue, 12 Feb 2008 11:43:06 +0000 http://www.webgambit.com/?p=65#comment-101 <p>Great point, Tom. I think deployment can definitely vary from company to company. Often I've worked in situations where the client had a separate build team all together that we worked with all the way through the dev cycle. In this company developers only had to worry about making sure the solutions were checked into source control. </p> <p>But in cases where the devs handle deployment as well, it is definitely crucial to get the hand off resource involved early on, perhaps transitioning that piece prior to even the first production push.</p> Great point, Tom. I think deployment can definitely vary from company to company. Often I’ve worked in situations where the client had a separate build team all together that we worked with all the way through the dev cycle. In this company developers only had to worry about making sure the solutions were checked into source control.

But in cases where the devs handle deployment as well, it is definitely crucial to get the hand off resource involved early on, perhaps transitioning that piece prior to even the first production push.

]]> By: Tom Opgenorth http://webgambit.com/2008/02/12/mastering-the-hand-off/comment-page-1/#comment-100 Tom Opgenorth Tue, 12 Feb 2008 09:22:49 +0000 http://www.webgambit.com/?p=65#comment-100 <p>Well said at lot of points. I'd suggest that perhaps it's better, instead of tackling bugs, to first get the client up to speed on the build & deployment procedures you have in place, and then with lower priority bugs. It gives them a feel for what is where in the code base.</p> Well said at lot of points. I’d suggest that perhaps it’s better, instead of tackling bugs, to first get the client up to speed on the build & deployment procedures you have in place, and then with lower priority bugs. It gives them a feel for what is where in the code base.

]]>