{"id":399269,"date":"2016-07-12T10:53:00","date_gmt":"2016-07-12T17:53:00","guid":{"rendered":"http:\/\/feedproxy.google.com\/~r\/crmsearch\/~3\/wSVMcCGVqFI\/agile-versus-waterfall-crm.php"},"modified":"2016-07-12T10:55:06","modified_gmt":"2016-07-12T17:55:06","slug":"agile-versus-waterfall-for-crm-implementation-success","status":"publish","type":"post","link":"https:\/\/customerthink.com\/agile-versus-waterfall-for-crm-implementation-success\/","title":{"rendered":"Agile versus Waterfall for CRM Implementation Success"},"content":{"rendered":"
Waterfall implementation methodologies have been the norm for over two decades of CRM deployments. These approaches are often visually depicted in cascading or linear diagrams and follow a progressive sequence of phases (for example, Requirements to Design to Development to Testing to Deployment). A significant risk with this deployment approach is that it can be unforgiving as success or failure is realized in largest part at the end of the project \u2013 thereby severely limiting remediation measures if outcomes don\u2019t match objectives.<\/p>\n
<\/td>\n | <\/td>\n | <\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||||||||||
With frequent deliveries, inspections and user verification, agile provides continuous visibility of project progress and outcomes.<\/td>\n | Agile testing is continuous. Delays, defects or missed value are evident with each sprint. Early recognition of these risks permits earlier invention measures.<\/td>\n | Agile projects deliver and demonstrate increments of value throughout the project. The highest value functions are normally delivered first.<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||||||||||
Due to value being delivered at the end of the project, waterfall projects have limited visibility until the end.<\/td>\n | Waterfall delivery of features and value is held until project completion. Delays or lack of value generally aren\u2019t recognized until it’s too late.<\/td>\n | Waterfall projects deliver all value at the end of the project. If objectives don\u2019t match outcomes the project will incur waste and rework.<\/td>\n<\/tr>\n<\/table>\nAgile or Waterfall?<\/h2>\nWhile agile methods offer some unique merits it\u2019s important to recognize there is no one size fits all CRM implementation methodology. Below are some of the primary differences that may influence which method is right for any given CRM implementation.<\/p>\n
|