http://360vendormanagement.com/2007/11/20/defects-in-requirements-change-control-and-performance-management/ Best Practices in Outsourcing and Vendor Management Thu, 13 May 2010 16:01:31 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://360vendormanagement.com/2007/11/20/defects-in-requirements-change-control-and-performance-management/comment-page-1/#comment-386 Vendor Management Articles of the Week: Scheduling, Forecasting, Requirements, and Inventory | 360° Vendor Management Thu, 29 Jan 2009 04:41:14 +0000 http://360vendormanagement.com/?p=4#comment-386 [...] Requirements Defects - How do effective outsourcing executives manage requirements accuracy and completeness? [...] [...] Requirements Defects - How do effective outsourcing executives manage requirements accuracy and completeness? [...]

]]> http://360vendormanagement.com/2007/11/20/defects-in-requirements-change-control-and-performance-management/comment-page-1/#comment-40 Sanjay Roy Fri, 21 Dec 2007 20:03:59 +0000 http://360vendormanagement.com/?p=4#comment-40 I fully agree with the above statement that requirement gathering and validation has formorst priority in the entire contract-to-delivery cycle. A well documented requirement is definitely reduces chances of defect. But as a vendor manager i would suggest that the Vendor team should engage the business analyst or a team of senior resources who will ensure that they have a good talkback session with the client team or the user community (select a project champion from client who has expertise of the business requirement of the process) to validate and verify that the requirement is well understood by both. In this kind of discussion itself, one will find that newer requirements get included as well thus early catching of missed requirement in the inital phase of requirement gathering...Well !! i have used such model while i was working for a IT service company and it worked very well for us... I fully agree with the above statement that requirement gathering and validation has formorst priority in the entire contract-to-delivery cycle. A well documented requirement is definitely reduces chances of defect. But as a vendor manager i would suggest that the Vendor team should engage the business analyst or a team of senior resources who will ensure that they have a good talkback session with the client team or the user community (select a project champion from client who has expertise of the business requirement of the process) to validate and verify that the requirement is well understood by both. In this kind of discussion itself, one will find that newer requirements get included as well thus early catching of missed requirement in the inital phase of requirement gathering…Well !! i have used such model while i was working for a IT service company and it worked very well for us…

]]>