Requirements Elicitation

Best Practice Overview 

Organizations need a proven set of core techniques, methods and tools for requirements elicitation and writing. Requirements written in human language can be subjective, ambiguous and subject to interpretation. To create “good” requirements, you need to become proficient in the “language and techniques” of requirements definition. This model needs to be embedded into the core BA process of the organization and supported with skills development.  Our team will provide templates and process covering how to write effective business requirements and where to integrate business analysis techniques. The BA Function within the organization starts with the requirements and ensuring there is a foundational best practice established will create value throughout the rest of the development cycle.

Best Practice Implementation Considerations

In order to create a stable and productive front-end presence for the BA and all related functions, the tools and templates must be leveraged in early and utilized in the same way a scalable lifecycle is applied.  Our best practices will generate a visible set of expectations for the BA function to use in the areas of:

  • Writing Business Requirements
  • 10 critical requirements questions
  • Translate business needs into well-structured business requirement statements
  • Four rules for managing a group of requirements
  • Prioritize requirements based on business and system needs
  • 5 improvement methods based on business process models
  • Business process models
  • Model the AS IS business process
  • Document the details of each process using the most appropriate technique
  • Document existing business processes

Best Practice Summary

Establishing visible and repeatable BA process is the cornerstone of a quality focused center of excellence.  The process and best practice noted above can be designed and integrated based on your organization’s needs, current gap areas and planned scale of the BA function.