Levels of business analysis Strategic: Business transformations; Business change; Business architecture and Target operating models; Business agility; Business cases Operational: Business processes; Business data and information; Management information and Decision support; Business rules; Business requirements; Problem analysis Tactical: Software requirements; Functional and Non functional requirements; Use cases; User stories. Business Analyst Roles … [Read more...] about Levels and roles of business analysis
Business analysis fundamentals - Ideas that have stood the test of time
This section is aimed at business analysts who have recently started in the role as well as people who are considering becoming business analysts.
Business analysis fundamentals will provide links to articles on basic concepts for business analysis.
If you are a new business analyst, or are considering becoming a business analyst, this is a good place to start.
Why terms of reference? Terms of reference are a key tool of business analysis. They are a vital control for: projects activities and work packages within the project project governance and management project team members A useful mnemonic for possible elements of a terms of reference is BOSCARD. It provides a framework for a terms of reference and is the basis of a contract between the business analyst and other project team stakeholders. BOSCARD BOSCARD … [Read more...] about Terms of reference for a better service
Requirements analysis As requirements are discovered (elicited) and captured, they should periodically be analysed; they can be analysed for completeness, correctness, priority, release date, ambiguity, clarity, testability, achievability, cost, risk, scope, cultural feasibility, etc. This is true whether the requirements are captured as user stories, use cases, business tasks or any other format. The requirements analysis process involves checking backwards with the requirements owners … [Read more...] about Requirements analysis and modelling
There is no universally agreed, ‘standard’ definition of the term requirement; many groups and individuals will have their own definitions. In general, it is reasonable to assume that a requirement represents something of value to the person or group that expressed it. IEEE (Institute of Electrical and Electronic Engineers) offers the following definition: A condition or capability – needed by a user to solve a problem or achieve an objective – that must be met by a system or … [Read more...] about What is a requirement?
Go for business value – Not blind adherence to a particular approach The way that you undertake requirements elicitation and management your gives credibility to your requirements specifications. Your requirements elicitation process should be designed to achieve this credibility whilst being flexible enough to adapt to any software development and project management approach, agile or traditional. This post, ‘Requirements elicitation – 8 steps to success’, outlines an approach in … [Read more...] about Requirements elicitation – 8 Steps to requirements success