As we know, businesses are of various kinds and cater to many industries, across sectors. The focus of our training is on business analysis within a project environment, initially supporting the assessment of change proposals, assisting the development of business cases, defining the scope and objectives of the project, defining the requirements for change and then supporting both the technical and business delivery of those changes.
The information needs to be studied for any patterns and trends, and reviewed to make sure it is as current and accurate as it can be. The business analyst must then take the results of any observations and analysis and needs to document them as either text or in the form of graphs, charts or illustrations.
Proficient as long time liaison between business and technology with competence in Full Life Cycle of System (SLC) development with Waterfall, Agile, RUP methodology, IT Auditing and SOX Concepts as well as broad cross-functional experiences leveraging multiple frameworks.
For example, quality analyst at Skyline Technologies Tim Morrow says he has served his team as a scrum master, a traditional business analyst (where he reviewed requirements and worked on the backlog of tasks to maximize business value) and as a product owner.
Certainly, building an information technology system more than likely will mean getting specifications and building something from those requirements, but to acquire those specifications it helps to be familiar with the field that the organization is in. If the organization is in the investment industry, and if you may have an understanding of bank transactions and lending processes, it would be great for identifying requirements.