WEBVTT

00:00:01.000 --> 00:00:04.410
This accompanies our article on custom software.

00:00:04.440 --> 00:00:07.930
First establish which limitation of existing software your

00:00:07.960 --> 00:00:10.010
organisation needs to solve.

00:00:10.280 --> 00:00:14.330
A fictional inspection service uses an existing product for customers

00:00:14.360 --> 00:00:15.450
and appointments.

00:00:15.640 --> 00:00:20.010
Its planner-to-inspector handover needs an additional check, currently

00:00:20.160 --> 00:00:22.730
tracked by employees in separate files.

00:00:23.000 --> 00:00:26.010
Follow one assignment from preparation to handover.

00:00:26.520 --> 00:00:30.330
What information does each user need, who can change it, and

00:00:30.360 --> 00:00:33.730
when is the assignment ready for the next responsible person?

00:00:34.040 --> 00:00:36.570
First investigate product configuration.

00:00:37.160 --> 00:00:39.770
Then examine a supported integration.

00:00:40.040 --> 00:00:44.010
Only a remaining relevant constraint establishes which part might

00:00:44.040 --> 00:00:48.810
justify custom development rather than replacing something that already works.

00:00:49.000 --> 00:00:53.090
Perhaps only a review screen beside the existing product is needed.

00:00:53.320 --> 00:00:56.050
Customer management and scheduling can remain.

00:00:56.280 --> 00:01:01.370
The first version covers one complete user flow rather than rebuilding everything.

00:01:01.640 --> 00:01:05.370
Ask intended users to complete the handover with permitted example

00:01:05.400 --> 00:01:06.290
records.

00:01:06.520 --> 00:01:09.570
Test missing information and limited permissions.

00:01:09.800 --> 00:01:14.770
A working demonstration does not establish support for everyday operational work.

00:01:15.000 --> 00:01:19.410
Compare development with maintenance, dependencies and change costs.

00:01:19.640 --> 00:01:23.930
Agree who controls records, source code and configuration, and who

00:01:23.960 --> 00:01:27.370
must be able to resolve problems after the initial delivery.

00:01:27.640 --> 00:01:30.450
Document the limitation and selected approach.

00:01:30.680 --> 00:01:35.610
Describe installation, access, data transfer and recovery, so another

00:01:35.640 --> 00:01:40.090
developer can understand the component and make controlled changes when required.

00:01:40.600 --> 00:01:44.690
Custom development starts with a justified choice for your process.

00:01:44.920 --> 00:01:49.130
Our source article on custom software compares configuration,

00:01:49.440 --> 00:01:54.170
integration, new development and the responsibilities of long-term maintenance.