Project Analysis

Requirements Gathering

Detailing your requirements and gaps

Clear and well defined briefs are key to accurate pricing and capability selection. Once your project vision and business objectives have been defined our Business Analysts can assist you in detailing your requirements scope both from technical and usability perspectives for inclusion in your supplier brief or for internal stakeholders.

We can also provide gap analysis for change in any area of your business. For example, data security, integrations or a new system implementation.

Change impact and risks can be analysed alongside any gap analysis as part of the project.

Optional Services

Depending on the project nature we offer:

  • Stakeholder Interviews – Running workshops to detail requirements identify best solutions to meet business objectives.
  • Process flow design – Technical diagrams required for development.
  • Swim lane design – Any required swim lane diagrams to visualise the solution.
  • Data structures and integration mapping – Mapping representations for system integration points.
  • User persona creation – Creating profiles to better understand how to optimise layouts for best conversions.
  • User type interviews and workshops – Meeting end users to get insights into behaviour and expectations.
  • Usability analysis – Checking layout against user types profiles and ease of use.
  • User Stories – Agile Epics and User Stories to bring the vision to life.
  • Non-functional requirements – Identifying system restraints and business logic.
  • Decomposition of user actions – Breaking down user actions.
  • User journeys – Full mapping of multiple user journey expectations and User Requirements.
  • Site taxonomies – Site map structure detailed with careful consideration for usability and SEO best practice if relevant.
  • Technology preferences and recommendations – Setting benchmarks for hardware and software platforms the the solution should adhere to.
  • Competitor analysis – Looking at competitor implementation and rankings with reports detailing how they can be improved upon.
  • Workflows – Detailing of any administration levels and actions that should form part of the build.
  • Language usage – Analysis of terms used, clarity in calls to action and any multi-lingual areas required.

The nature of requirements gathering is very much dependent on the project type and the above examples are very broad. If you would like to discuss requirements gathering or any of our other services please contact us and let us help you bring your project to life.

Privacy Settings
We use cookies to enhance your experience while using our website. If you are using our Services via a browser you can restrict, block or remove cookies through your web browser settings. We also use content and scripts from third parties that may use tracking technologies. You can selectively provide your consent below to allow such third party embeds. For complete information about the cookies we use, data we collect and how we process them, please check our Privacy Policy -
Consent to display content from Youtube
Consent to display content from Vimeo
Google Maps
Consent to display content from Google
Consent to display content from Spotify
Sound Cloud
Consent to display content from Sound