When packaged software does not fit the way a company works, there are usually two choices: change the process to suit the software, or build software to suit the process. VASCOM takes the second route, and says plainly when the first is the better one.
Map the flow as it actually runs, including the steps done verbally. Record who enters, who checks, who approves, and where errors tend to occur.
Build the core first so it can be used and commented on. The trial runs on one month of real data, not sample data.
Add permissions, reports, notifications and edge cases. Tested against the company’s own real situations.
Source code, documentation, user training; agreed arrangements for maintenance and future extension.
A narrow process usually takes a few weeks to reach a trial build. Most of the time goes into assessment and testing rather than writing code.
No. Handover includes source code and documentation, so another provider can continue if a change is ever wanted.
Changes are made on the existing foundation, or by adding another module. The architecture and documentation are written to be read by people other than the author.
Write down the three steps that take the most time. VASCOM sets out which parts can be built and which parts should not be.