Comments on: Practical Software Practices http://svprojectmanagement.com/practical-software-practices Project management wisdom from practictioners and the UCSC Extension in Silicon Valley Sat, 13 Mar 2010 10:14:06 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Ashley http://svprojectmanagement.com/practical-software-practices/comment-page-1#comment-10798 Ashley Thu, 29 Oct 2009 09:58:41 +0000 http://svprojectmanagement.com/?p=1974#comment-10798 Thanks for such a wonderfully tips which we all should follow in our daily routine work. All Points are useful and practical. This is also very useful but very rarely used by people. Thanks for such a wonderfully tips which we all should follow in our daily routine work. All Points are useful and practical. This is also very useful but very rarely used by people.

]]> By: Anita Wotiz http://svprojectmanagement.com/practical-software-practices/comment-page-1#comment-3626 Anita Wotiz Wed, 08 Apr 2009 05:46:52 +0000 http://svprojectmanagement.com/?p=1974#comment-3626 I think you can tailor each of these practices to work for small teams. The titles make them sound heavy, but they really don't need to be. I'm going to write more on each of these the rest of the week, but in general, I truly believe that you can take the essence of each and make them work for even tiny teams. The small team just means that communication is easier, that requirements reviews and change reviews go more quickly. But getting the requirements down in writing, keeping up a current requirements baseline, putting every change through a process, testing every requirement (and checkmarking that it's been tested), keeping track of necessary tasks, it's all possible to do with 3 people. And, I'll suggest that you do these things from the beginning (even with a tiny team), rather than add in the practices later. It's easier as well as more comfortable. See if the rest of my posts this week help, and let me know if I can expand more on your question. I think you can tailor each of these practices to work for small teams. The titles make them sound heavy, but they really don’t need to be. I’m going to write more on each of these the rest of the week, but in general, I truly believe that you can take the essence of each and make them work for even tiny teams. The small team just means that communication is easier, that requirements reviews and change reviews go more quickly. But getting the requirements down in writing, keeping up a current requirements baseline, putting every change through a process, testing every requirement (and checkmarking that it’s been tested), keeping track of necessary tasks, it’s all possible to do with 3 people.

And, I’ll suggest that you do these things from the beginning (even with a tiny team), rather than add in the practices later. It’s easier as well as more comfortable.

See if the rest of my posts this week help, and let me know if I can expand more on your question.

]]> By: Gregg http://svprojectmanagement.com/practical-software-practices/comment-page-1#comment-3609 Gregg Tue, 07 Apr 2009 17:02:16 +0000 http://svprojectmanagement.com/?p=1974#comment-3609 Great point on listening towards the end, I think that is key no matter how big the team is. What about small teams (2-3 members) though when it comes to the 5 practices you mention above? Any tips or experience? Great point on listening towards the end, I think that is key no matter how big the team is. What about small teams (2-3 members) though when it comes to the 5 practices you mention above? Any tips or experience?

]]>