Currently Browsing : requirements validation

To technology or not to technology Over the past few years I have come to realise that business stakeholders are growing in their understanding of technology. Does this understanding carry an advantage, a risk, or aspects of both within the project world? In my early years as an analyst, I remember working on a particular project and jotting down business requirements that were delivered from a strategic perspective. It was blatantly clear that these requirements were carefully derived to support an organisation’s strategic mission. I discussed these with the technical stakeholder before committing to the business what could or could [&hellip

In today’s fast paced technology world it is common, if not mandatory, for financial institutions to replace legacy systems in order to gain competitive advantage. In my experience business stakeholders will often have decided on the technology before bringing an analyst or consultant on board. A lack of analysis from the onset means uninformed decisions and ultimately reputational risk if the wrong choice is made. Implementation projects that I have been involved in, have typically deferred the engaging of business analysts until project slippage has arisen. I’m not entirely sure whether this is a scapegoat tactic or a sincere attempt [&hellip