One of the key goals of business analysis is to break down a problem or opportunity to its true underlying business requirements. Regrettably, far too frequently, what is presented as a business requirement is actually a description of a solution that meets the underlying requirement. This presentation uses real life examples to demonstrate the often subtle difference between a true business requirement and a solution description, looks a ways and business analyst may recognise the this difference and explains why it is so important to make this distinction in order to develop the best solution.
Key Learning Points:
• The importance of understanding the true business requirement
• How to distinguish between business requirements and solution
• How an understanding of requirements leads to a more optimal final solution
Helen has been a business analyst for over ten years now, the last five of which she has spent in New Zealand where she worked for a two years with Statistics New Zealand before joining the Bank of New Zealand in August 2008.
Prior to this she was ten years with UBS Investment Bank in London. She joined UBS as an analyst/programmer but got too frustrated at developing beautiful applications that were never really used by the business as no-one in technology had ever really bothered to find out what the business either wanted or needed. Hence the move to business analysis.
She has a PhD in theoretical particle physics from Southampton University in England, but gets a bit embarrassed about how little physics she can remember now!!!
Away from work she has two girls who take up most of her time. Any extra spare time she does get she like getting involved in amateur dramatics.