WEBVTT

1
00:00:00.450 --> 00:00:06.168
Start with the work your organisation needs to
do. We turn requirements, constraints

2
00:00:06.246 --> 00:00:10.257
and existing systems into an agreed plan with
clear responsibilities.

3
00:00:12.350 --> 00:00:16.582
Start by agreeing the result you need from it
requirements discovery & solution

4
00:00:16.595 --> 00:00:21.714
planning. Identify the people involved, the
information and systems already in

5
00:00:21.727 --> 00:00:27.547
use, and the decisions that require evidence. An
IT requirement often begins with

6
00:00:27.560 --> 00:00:32.626
a practical problem: information has to be
entered twice, a team cannot work reliably,

7
00:00:32.847 --> 00:00:38.198
or several suppliers own different parts of the
same issue. We start by understanding

8
00:00:38.211 --> 00:00:43.615
the people, workflows and systems involved. That
gives the subsequent software,

9
00:00:43.915 --> 00:00:47.027
infrastructure and support decisions a common
purpose.

10
00:00:49.117 --> 00:00:54.247
Before work begins, agree the scope, priorities,
responsibilities and the checks

11
00:00:54.260 --> 00:00:59.887
that will demonstrate a useful result. Clarify
the information, access, supplier

12
00:00:59.900 --> 00:01:05.421
dependencies and commercial terms involved. Keep
assumptions and exclusions visible,

13
00:01:05.655 --> 00:01:09.561
so everyone understands what is included and
what needs a separate decision.

14
00:01:11.650 --> 00:01:18.045
A shared requirements brief. The users,
workflows, desired outcomes and constraints

15
00:01:18.058 --> 00:01:23.488
are recorded in language the delivery team and
your stakeholders can use. A practical

16
00:01:23.501 --> 00:01:29.439
delivery scope. The proposed first release
identifies the services involved, assumptions,

17
00:01:29.621 --> 00:01:35.207
exclusions and acceptance criteria. Timescales
and commercial terms are agreed

18
00:01:35.220 --> 00:01:36.222
against that scope.

19
00:01:38.317 --> 00:01:44.165
An ownership and handover plan. We identify
decision-makers, access requirements,

20
00:01:44.347 --> 00:01:48.618
dependencies and the people responsible for
approving and operating the result.

21
00:01:49.517 --> 00:01:55.558
Supported operation. Your proposal confirms the
scope, responsibilities and evidence

22
00:01:55.571 --> 00:01:57.017
for this part of the service.

23
00:01:59.083 --> 00:02:03.745
Review the agreed work against representative
examples and the acceptance criteria.

24
00:02:04.645 --> 00:02:10.531
Check the information, access, hand-offs and
exceptions relevant to the scope. Record

25
00:02:10.544 --> 00:02:15.075
any unresolved limitations with an owner and a
next action, so acceptance remains

26
00:02:15.088 --> 00:02:17.536
an informed decision about the actual service.

27
00:02:19.617 --> 00:02:24.317
Agree what happens after the initial work: who
uses the result, who maintains the

28
00:02:24.330 --> 00:02:29.528
relevant records and how questions or changes
are raised. The operating arrangement

29
00:02:29.541 --> 00:02:34.918
follows your proposal. Review evidence from use
and support, then agree the next

30
00:02:34.931 --> 00:02:37.965
proportionate improvements as your organisation
develops.

31
00:02:40.050 --> 00:02:45.297
Britixo brings planning, software, integration,
infrastructure and support into

32
00:02:45.310 --> 00:02:51.016
a connected delivery approach. Your proposal
identifies what is included, who owns

33
00:02:51.029 --> 00:02:55.664
each dependency and how the service will be
supported. That gives your team a

34
00:02:55.677 --> 00:02:58.919
clear route from the original requirement to
everyday operation.

35
00:03:00.983 --> 00:03:05.476
Explore the matching Britixo service page for
the details and related guidance.

36
00:03:06.376 --> 00:03:10.985
Tell us what your organisation needs to achieve,
then discuss an appropriate scope,

37
00:03:11.194 --> 00:03:14.202
the responsibilities involved and a practical
next step.
