IT complex projects require a professional management methodology in order to respect rigorously the product expected QCD (Quality, Cost and Delivery Delay). Nowadays, most of those projects worldwide are using a software development oriented methodology called V-model. I’d recently worked on a big CRM (Customer Relationship Management) implementation project in the banking industry which aims to provide the tool to about 6000 users, and I think that following V-model used to be helpful and allowed us to define and allocate tasks easily.
Let’s start by giving an overview of what V-model seems to be. In fact, V-model is a process or we can say an organization into the main steps which have to lead to the implementation of your final product in total respect of customer requirements. The ultimate goal is to keep project deviation risks under control and guarantee the quality which is ensured by the regular process of verification/validation by both testing teams and end-users.