A couple of weeks ago I wrote the blog post The future of IT business analysis – moving from ‘what the business needs’ to ‘what the customer needs’ in which I suggested that it is becoming increasingly important for us Business Analysts to look after the needs of our organisation's customers.
In my last article The future of IT business analysis – moving from ‘what the business needs’ to ‘what the customer needs I positioned that the business analyst role needs to evolve for digital transformation projects where the focus is on ‘customer systems’ rather than ‘business systems’.
I can’t remember the last time I interacted with a real person at the bank for a “normal” transaction. Digital Transformation is here, and further along than we might realise. As the world continually evolves around us, we must also evolve to stay relevant.
In my role as an Equinox IT Senior Consultant specialising in business analysis, I often work on client projects with the goal of modernising and digitising their business processes. In a recent assignment, I was asked to work as part of an Agile project team for a regulatory body to analyse and specify the business requirements and system requirements for the development of a mobile application. In this article, I cover the requirements analysis activities that I performed to ensure we delivered an application that successfully met the business’s needs.
As an Equinox IT Senior Consultant specialising in business analysis I do a great deal of client work with user stories. A couple of weeks ago I attended two of Gojko Adzic’s training courses in Auckland, including his ‘Getting more value out of your User Stories’ course. In this article I share my top three key take outs from that course.