CRM Projects should always start with the specification!
All too often the VP of Sales waltzes into the CIO’s office and says, “I need a CRM system, send me an email when you have found one and have it implemented.” Granted this is a bit of an extreme, somewhat cheeky example but, believe it or not, it can often be true. The most important thing is to begin with the specification or definition of the primary use cases. This allows all stakeholders to have a clear understanding of what business process need to be automated or improved. Once everyone agrees on what it actually is that the team will be doing it will be much easier to move into system selection or system design. So, let’s take a look at the framing of a software requirements specification.
What is a Software Requirements Specification? 
A Software Requirements Specification is the written expression and description of the software system requirements, dependences, integrations, and business processes to be created. The SRS is often a living document and is only relevant at a particular point in time. SRS documents are most valuable at the beginning of a project before actual design or development has begun.
A SRS document attempts to apply common language to the functions and capabilities the new software system will deliver. This mutually developed blueprint will be the initial starting point from which the developers will begin the actual application design. This “Lead” document will be the root document from which all other documents such as, design documents, statements of work (SOW), software architecture designs, training plans, user acceptance testing plans, and system documentation plans, are derived.
Resist Design During Requirements Gathering!
It is important to resist the temptation to design the system during the requirements gathering phase. This initial step and goal of the SRS is to adequately articulate the functional requirements.
Key Benefits of the SRS Process
Some of the key benefits of establishing a set of requirements are the following:
- Set the baseline – Establish a written baseline of understanding between the Supplier and the Client or the Project Team and the business stakeholders.
- Reduce development time – the requirements process forces business stakeholders to consider all scenarios rigorously prior to design activities ensue. This helps to eliminate redesign, recode, change orders and scope creep!
- Basis for initial cost estimates and project delivery targets – The thoughtful collection of requirements will empower Intelestream consultants to provide a realistic initial estimate of the level of effort required to meet requirements.
- Used as a basis for post project documentation or future enhancements – Because the SRS often expresses in business terms the system functions. It can often be used for the basis for system documentation or future requirements.
Conclusion
All but the smallest of projects should start with a SRS.
