Timing of business analysis work
determine when the business analysis should take place. More specifically how the business analysis efforts should change over time. Does the project already have set phases? How many of the phases require business analysis deliverables.
If the timing of the business analysis need is front loaded the approach may need to be more plan driven and take framework elements from frameworks on the side of the Spectrum. However change driven approaches may be more appropriate if the need is stretched across a long period of time, or is needed throughout the product.
Formality and level of detail of business analysis deliverables
Plan driven approaches generally require a high level of formality and detail. The planning phase of the project relies heavily on a dependance and accuracy of the business analysis activities done. Often this need for formality will present itself though documentation and validation rigour. Documents may need to follow strict standardised templates and require a formal approval process.
Therefor initiatives which require high levels of formality will require a business analysis approach which pulls elements from the framework on the plan driven side of the spectrum. Other initiatives, however, which prioritise fast turn around and consistent delivery are more likely to pull from the change driven frameworks. projects which are focused on easy team interactions and don’t have place such a high priority on documentation may also get value out of a change driven approach.
Requirements Prioritisation
A approach will need a method for prioritising Requirements. Change-driven approaches tend to place a great deal of emphasis on effective requirements prioritisation methods, due to the small scope of each iteration or release. ^[A Guide to the Business Analysis Body of Knowledge® (BABOK ( PDFDrive ).pdf]
Change management
How often the requirements will change can play a large factor in how you evaluate an initiative. When changes may be minimal or accurately predicted