Many words have been written about the process of business analysis and how it can be performed on different types of projects. There are a multitude of tools and techniques which can be used plus methodologies and frameworks to suit a wide variety of circumstances. This makes it all too easy to get absorbed in the day-to-day detail and forget about the real purpose of business analysis – to fix a problem or provide the organisation with a new capability.
An easy way to stay focused on this objective is to think of business analysis as a journey – a journey from an as is to a to be system – from a current to a future state. Software development methodologies (SDLC’s) such as agile, iterative, waterfall, etc. are the means of travel but you don’t have to be an expert in methodologies to have a successful journey. The following extract from IRM’s Business Analysis workshop is a simple guide which can be used (whatever the methodology) to help you keep a clear picture of what the successful BA journey entails – reaching your destination.
Read the full paper here: The Business Analyst Journey
If you enjoyed this paper, you may also like these: