How to successfully deliver your CRM project with Clarity, Simplicity and Certainty
This is the 2nd in a series of 6 articles looking at how to successfully deliver your CRM project. The full series contains: The purpose of the Architecture is to help teams develop the technical capability on time and on budget whilst ensuring it solves the problem for which it was designed. The Architecture will build on the very high-level view purported in the Charter and will contain: Concepts – A conceptual view of the stack and its moving parts for communication and context Option Analysis – Platforms, Languages and Tools in light of the functional and non-functional requirements. High Level Design – Features, phases and solution requirements at a Function level Detailed Design – More definition around areas of complexity Non-functional requirements including – Security, Performance, Maintainability, Scalability, Reliability, Usability and Risk The expected outcome is that both the business and technical requirements have been incorporated into a Solution. Specific technologies may be selected, short listed or used as examples as the Architecture develops over time. The Architecture is neither a Process Diagram nor the detailed User Requirements, which will be developed in the next phase of the project. 3 x Critical Success Factors These are CSFs for the Architecture, not the Project: Match the Solution to the Business Environment This is important in all major technology solutions but even more so with CRM deployments due to its role in supporting all customer facing interactions and integrating to all other teams. The Architecture must take a strategic view of the specific functional requirements and then the significance and importance of potential reliance’s on and impacts to other teams and their processes Desire vs Reality The simple approach of Why, What and How (Before When & Who) will assist in addressing this challenge: Why: The justification of the need for […]