Identify and analyse all potential stakeholders for the proposed project or system. Stakeholders include anyone who has a vested interest in the product or system that is being developed. Stakeholders will have various levels of engagement throughout the project and will need to be communicated with along the way.
Agree on the business analysis methodology (e.g. waterfall, agile, six-sigma) to follow, based on the type of project and organisational standards. The level of tailoring and the combination of practices applied will determine the high-level deliverables from the analysis process, together with the nature and timing of the related tasks.
Determine and schedule the business analysis tasks that will be required. Prepare a plan that details how these tasks will be carried out, estimates of the work effort required, the sequence of events, and the resources that will be allocated to them. Include the nature and timing of stakeholder engagement in the plan.
The RACI model enables the BA to assign responsibilities(accountable, responsbile, consulted, informed) to each identified stakeholder or project team membe.
Fully analyse and define the business problem/opportunity, its impact on the business, and the potential benefits being sought from a solution. This will be the basis for justifying why the project is being undertaken.
Define the requirements management process, including how requirements are to be communicated, approved and changed. The plan will describe how requirements are to be recorded, what documents or artefacts are prepared from them, and how requirements will be prioritised.
Determine at a general level what is or isn’t going to be catered for in the solution (for example features). This is important for building the business case and managing expectations about the solution.
Evaluate and define the most viable solution-approach, to the level of detail required to define the solution scope and develop the business case.
Consolidate your analysis and findings from the Enterprise Analysis phase into a business case; providing the organisation with the information required to make an informed decision about the benefits and impacts of proceeding with the proposed solution.
Select the appropriate techniques and estimate the effort required to elicit requirements from the identified stakeholders.
Conduct the selected elicitation tasks to gather requirements.
This is a template for specifying solution requirements, communicating with stakeholders including business owners and solution architects and designers and obtaining approval.
Evaluate requirements to ensure they fulfil quality specifications and are sufficiently defined and structured to allow the technical teams to design, develop and implement an effective and efficient solution.
Create and maintain relationships between requirements and other solution components, such as test cases.
Documentation and communication of requirements, throughout the project, to ensure they are correctly understood by all stakeholders and effectively implemented.
Specify requirements in multiple ways to define for solution designers and developers what is required of the solution to meet users’ needs; using a combination of textual statements, matrices, diagrams and formal models, in non-technical language.
Assess proposed solutions to determine the value they provide and make recommendations about selection. Once a solution is selected, assess business value and timing of components.
Define the requirements of any transition tasks, including such things as organisational change, training, data migration, change over and decommissioning.
Review the constructed solution to ensure it meets the business need and determine appropriate resolution of any defects. Continue the validation process through the implementation and transition process.
Run a workshop
JAD Session with Developers