IBS Journal October 2015


Figure 2: The CRISP framework About the author


Level prioritisation performed prior to signing off on the requirements enabling IT to prioritise delivery


Viable enough to be delivered through a technological solution


Extent to which requirements remain stable throughout the projects


S


Clear and specific enough that people know what is to be done


Indexing Independence


Requirements should be independent of the technological solution


Sudeep Nair is a Director at Cedar Management Consulting Interna- tional LLC. Sudeep has over 15 years of international experience (US, UK, continental Europe and India) in business transformation of banks and insurance companies, and is a recognised expert in delivering significant improvements for busi- nesses across organisation, process and technology. Sudeep completed his MBA from Indian Institute of Management (Ahmedabad) and is a PMP and TOGAF practitioner. He can be reached at


sudeep.nair@cedar-consulting.com I


Requirements should be indexed so IT has a clear idea of which requirement is referenced


R


Extent of requirements that are explicitly stated


P C


Clear enough for IT to implement


Effectiveness by which a representative user is able to articulate requirements of the entire user community


Ease by which the business can trace back the requirements to the specific module


Misalignment with functional specifica- tion documents (FSDs): vendors prepare FSDs aligned to business requirement doc- uments (BRDs) but many organisations lack internal resources to validate the alignment between the FSD and BRD documents.


Requirements should be CRISP


Ideal requirement specifications meet the ten criteria given in figure 2 above. The CRISP framework can help in


ensuring that requirement specifications serve as the basis for high-quality technol- ogy solutions. Each dimension of the CRISP framework can be measured as in figure 3.


© IBS Intelligence 2015


The CRISP framework helps organisa-


tions to define requirement specifications that accurately reflect business expecta- tions. The following key elements help in smooth requirement engineering based on the CRISP framework:


Consultative skills: seasoned business consultants capable of engaging with business and documenting requirements.


Requirements repository: a pre- defined set of requirements for each solution, which accelerates the process of documen- tation and lets business focus on the true differentiators.


www.ibsintelligence.com 51


analysis: requirement engineering


Prioritisation


Pragmatic


Coverage Clarity


Reference ability


Representation


Stability


Specificity


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60