One of the Analyst’s key activities will be to understand the context/situation in which a project sits, in order to gain a better understanding of what implications and impact the project will have. The analyst is responsible for gathering all requirements of the project that are (a) relevant to the project and (b) meet the deliverables of the project, which could typically be defined by any or all of the stakeholders ranging from, shareholders, employees to customers. The requirements document will then form the basis of the project.
In order to create a requirements catalogue for the project, a couple of activities within the process need to be conducted; the first of which is:
1. Investigating a Situation
This is the stage in which you gather high level information about the problem, issue or gap that needs addressing. This data is important because it will provide a good reference point on which to build upon. The situation will contextualise the problem and the potential solution’s practical application within the business.
This can typically done through gathering details on the following:
- Speaking with stakeholders on the issues, gaps, problems they are facing, that the project will help to achieve
- Consider company strategy and strategic objectives
- Consider the Project Initiation documentation (if there is one) to gather further details on who the stakeholders are, who will be using the system, risks, costs controls, business case
- Consider the terms of reference (if there is one) which will provide details on Objectives, Scope, Constraints, Authority and Resources (OSCAR)
- Stakeholder analysis
- Understand documentation that is related to the project
- Review process maps
- Review non-documented processes with actors
- Speak with relevant stakeholders
At this point it is worth considering what problems, issues, gaps etc the output is facing. You might want to refer to the following to gain a better understanding of this.
- Quality control documentation
- Issues Log
- Complaints received
- Performance management reports; KPI’s etc
- Speaking with relevant stakeholders
Some of the techniques you might use to gather the above information are:
- Activity Sampling
- Document Analysis
- Updating/creating draft Business Needs Log
This above gathered information can be documented under the following headings:
- Summary of information gathered
- Data gathered
- Draft business needs
- Draft world view
- Mind maps
- Use case (as-is)
- Rich picture diagrams
- Create a draft business needs log, documenting the high level business requirements based on the stakeholders you have spoken with; this may need revising based on subsequent activities
- Fishbone diagrams
- Knowledge on structure, management, policy and change processes
- Any other details that may come in handy for later stages to help support with questions, interviews, workshops analysis etc
- The input vs output analysis would be equip you to create a draft gap analysis
With the above information you would be able to document the very high level requirements you will be able to review for the compilation of your business needs log and consider when doing further analysis; you may alternatively encapsulate gathered thoughts, comments etc in to a general “world” view. You will also have good information on the organisational structure, divisions, policies, strategy and more to have a better understanding of the process of change and management within the company when doing further analysis, which is always useful, for context.
And there you have it; you’re now ready to move on to your second activity; considering the perspectives of your stakeholders. The next stage is concerned with analysing stakeholders and their perspectives on the situation/project, to get a better understanding of their values and beliefs for the project.
The end result of the complete business analysis process will be a clear, non-ambiguous, relevant, reasonable and testable requirements document. The document will take the company’s internal structure, management and policies in to consideration, meeting all relevant requirements and deliverables of the project and your stakeholders, hopefully getting them to buy you a drink at the end of it. Or in my case a can of Dr Pepper; I love that stuff.