Skip to main content

IT Strategy & Advisory

Functional scoping & business analysis

Formalise the need, structure the requirements and carry the business voice through the project — right up to the acceptance of deliverables.

EN UNE PHRASE

The cost of a badly written requirement is paid at design time.

THE PROBLEM

The situations that bring us in

  • 01

    The need is expressed in solutions, not in objectives and business rules.

  • 02

    Requirements are scattered across minutes and emails.

  • 03

    Gaps between expected and delivered surface at acceptance, too late to absorb.

  • 04

    No repository makes it possible to say whether a deliverable meets the original need.

  1. 01THE PROBLEM

    A project launched on a partial statement of need, where each party reads the perimeter differently.

  2. 02WHAT AXENEO DOES

    We run the business workshops, map the target processes, structure the requirements in a traced repository and assess the choice of solution.

  3. 03THE RESULT

    A requirements repository that stands up to scrutiny, a stable perimeter and acceptance criteria defined before work begins.

What we do

Scoping & stating the need

  • Business workshops and analysis of the existing processes
  • Target processes and management rules
  • Repository of functional and non-functional requirements
  • Traceability matrix from need to requirement to test
  • Perimeter, assumptions, exclusions and prerequisites

Solution selection & support

  • Evaluation grid and solution scenarios
  • Drafting of the specification and of the tender file
  • Analysis of responses, presentations and recommendation
  • Oversight of the design and arbitration of the gaps
  • Functional acceptance testing and validation of deliverables

The IT Strategy & Advisory method

This domain sits within the pillar’s overall method.
  1. 01

    Understand

    Interviews with the business and with IT, review of the application estate, analysis of processes and of what actually irritates people. We start from what happens, not from what is documented.

  2. 02

    Make it objective

    Gaps, dependencies, costs, risks. Scenarios are worked through with their organisational implications, not only the technical ones.

  3. 03

    Decide

    Options are put to decision-makers with what they really imply. A decision that has not been taken is identified as such and raised to the level where it can be.

  4. 04

    Sequence

    A trajectory in waves, with verifiable milestones, explicit prerequisites and a workload compatible with what the teams can actually absorb.

  5. 05

    Steer

    Governance, bodies and indicators put in place. The setup is designed to be sustainable by the teams once we have gone.

USE CASES

Where we step in

  • Go to market on a comparable basis

    A specification built on traced requirements makes it possible to assess the responses on substance.

  • Carry the business side of a technically led project

    Keep the business intent and the implementation consistent, arbitrate the gaps and avoid decisions taken by default.

Contact

Functional scoping & business analysis: let’s talk about your context

A first conversation is usually enough to tell whether the subject calls for scoping, a portfolio decision, or putting the steering back in order. We will tell you plainly.