Ultra fast scope definition - case study

This Case Study does not contain any confidential information which would allow to find out business plans of Equiniti. This Case Study does not contain any dates nor detailed description of requirements in order to protect interests of Equiniti.

The goal of this Case Study is to show in numbers the efficiency of Task Descriptions and what can be achieved with this requirements engineering method.

This Case Study is about using in practice Task Descriptions in Fin Tech project realized for Equiniti by EQTek for who I worked as System Analyst.

https://focusonbusiness.eu/en/news/equiniti-opens-its-first-office-in-poland/3189

https://equiniti.com/uk/news-and-views/eq-views/introducing-eq-tek/

The project I worked on consisted of creating from scratch a mobile application. The role of this application was to allow for investing in securities on London Stock Exchange. To do it the app was to be integrated with other Equiniti systems. The scope of the project was very broad with many supporting features.

I was working on this project for one month. I created domain model in form a single Entity Relationship Diagram. To define scope I created Task Descriptions. There was 40 Task Descriptions at the end. Every of them described a process of completing a specific task.

There were a few people engaged in the work on the scope but the main stakeholder and domain expert was a person who lead market research for a few months. I created list of Task Description together with this marketing person. This work took us 7 working days. Entity Relationship Diagram had been updated in parallel.

At the end this information was enough to estimate the implementation effort. The Tasks were also divided into groups which were assigned to specific release.

I wanted to mention this project because the scope was very big and the business domain very complex. Under such circumstances we were able to specify the scope in such detail that it was possible for IT to provide estimates. What was amazing is that work on the scope took only 7 days which is a great result. This was possible because we spend all time only on this activity and the marketing researcher understood the business needs very well.

The document with Task Descriptions was very concise - it had 12 pages but the level of details allowed for making decisions about releases. Managers could plan the project execution is a best way for going to the market.