Barcove
Practice
Twenty-three years of this has taught us a plain sequence. Understand the day as it is lived. Agree the software that belongs in it. Put working pieces in people’s hands early. Stay after the launch date, because that is when the real grain shows.
01
A brief that starts with features usually describes a product the team has seen somewhere else. We start with the day: who touches the work, where it stalls, what cannot be dropped. At CEMRI that was a clinic with no reliable line. At Unifi it was an editor who needed to publish a promotion without a developer in the room. At CLEA it was a result that had to be trusted, and accepted by MySejahtera.
02
We write down the system in the language of the operation, and we name what “working” means. Offline sync. A flow a non-engineer can change. A match a recruiter will actually use. Scope is a decision about the work, not a pile of screens. Changing it later is allowed. Changing it silently is not.
03
The stack follows the problem. A national content site wanted Drupal. A phone-first money product wanted a mobile build. A product story wanted a 3D page. People who will live with the software try it while the direction can still move. Eight developers on CLEA, three on Luminare: the team is sized to the job.
04
Handover includes the people, not only the repository. We watch the first real weeks. Sime Darby Property, YES, and Nippon Paint included the maintenance after launch. Shorter jobs get the same habit on a smaller clock.
These are ways of making, not a catalogue to pick from. A job often crosses two of them.
A conversation, not a questionnaire