It takes around 2 weeks – 3 months to:

    • Document key business processes and how they’re covered with existing software.
    • Elicit business needs and concerns.
    • Draw up high-level functional and technical software requirements.
    • Evaluate risks of new software introduction, e.g., impact on business processes.

2.Business case composition

It takes from 1 week to conduct cost-benefit analysis, estimate NVP, ROI.

3.Architecture, UX and UI design

It takes from 2 weeks to 3 months to:

    • Define app architecture, techs, data flow and integration points.
    • Conduct UX research, design wireframes, prototypes, and interface mockups.

Note: Reusing parts of your existing enterprise systems can be more cost-effective and reliable than developing new software modules and enabling their communication with other systems. When you choose to repurpose legacy software components, we suggest considering IT Support and Service.

4.MVP launch (upon request)

The delivery of the first working version of enterprise software takes from 1 month.

5.Development and testing

    • Agile delivery of new software parts in 2-week releases. Continuous safe minor releases via automated CI/CD pipelines.
    • Analysis of emerging needs and the release planning.
    • Approving the release scope.
    • Delivering and reviewing mockups.
    • Developing and testing the approved software part, migrating the developed software part to the staging and production environment.
    • Getting feedback from a project sponsor and users on the results of the release.
    • Reviewing the results of the completed release and approving the scope of the next release.

Note: Small, well-defined projects can be delivered in a linear mode with one major release.

6.Deployment (and 3-month maintenance)

    • (if agreed with you) Switching to the Kanban methodology for support activities with advance notice.
    • Conducting workshops prior to user acceptance testing (UAT):
      • Walking you through the process of UAT.
      • Walking you through the post-go-live process.
    • Organizing UAT.
    • Establishing software monitoring processes.
    • Defining new roles and responsibilities for application support in your and our teams.

Note: Trial implementation is recommended for applications to minimize possible downtimes in production. It is done for a limited number of users and requires comprehensive technical support in case any problems are encountered. Trial stages usually take up to 1-3 months.

7.Project handover / continuous support (on demand)

    • Conducting project evaluation.
    • Performing knowledge transfer to your in-house IT team/other vendors.
    • Capturing, consolidating and analyzing project lessons learned, providing the final report and requesting your confirmation for the project closure.