Discuss a Project

UNDERSTAND · ENGINEER · PROVE · OPERATE

The JustJava Standard

There is a difference between software that was built and software that was engineered.

The JustJava Standard is how we reduce uncertainty, protect quality and take software from business requirement to dependable operation.

UNDERSTAND → ENGINEER → PROVE → OPERATE

The principles behind it.

  • Engineering ReviewREV 2

    Clarity before code.

    We understand why the project exists before deciding what should be built.

  • PR #4822 APPROVALS

    Engineering over shortcuts.

    We make technical decisions for reliability, maintainability and ownership beyond the next demonstration.

  • JavaSpring Boot

    Java at the core.

    Java sits at the centre of much of our backend engineering because important systems benefit from structure, maturity and long-term maintainability. Surrounding technologies are selected according to the product, interface and operating environment.

  • US-024ACCEPTED

    Every feature earns acceptance.

    Testing and client validation happen throughout delivery, not only when development is supposedly finished.

  • JustJavaReady for your UAT

    Visibility by default.

    You should know what is happening without chasing us.

  • v2.4.0IN PRODUCTION

    Production is part of engineering.

    Software working in a development environment is not the finish line.

  • Handover packDELIVERED

    Client independence matters.

    Good engineering should create options, not lock-in.

How the Standard works.

Understand

  1. 01

    Discovery

    Understand the business before discussing the build.

    REQ-1042RECEIVED
  2. 02

    Solution Engineering

    Map processes, workflows, architecture, data, integrations and major risks.

    Risks3 named
  3. 03

    Scope Baseline

    Agree what belongs in the initial release and make responsibilities, dependencies and assumptions visible.

    Release 1written downTry it below ↓

Engineer

  1. 04

    Kick-off & User Stories

    Turn agreed capability into clear sprint-ready work.

    US-118READY
  2. 05

    Engineering

    Develop against the agreed product and technical direction.

    PR #482MERGED

Prove

  1. 06

    Quality Engineering

    Peer review, QA, testing and progressive acceptance.

    Tests148 / 148
  2. 07

    Final UAT

    Validate the complete release.

    ReleaseSIGNED OFF

Operate

  1. 08

    Production

    Deploy and prepare the software for real use.

    v1.0LIVE
  2. 09

    Launch Assurance

    Stay close during the first period of production.

    AssuranceDay 12 of 90
  3. 10

    CoreCare or Handover

    Continue with JustJava or transition responsibility.

    CoreCareHEALTHY

03 · Scope Baseline

Decide what belongs in the first release.

Tap capabilities in and out of the first release of an example payment reconciliation platform. Watch what happens to time, dependencies and risk.

Scope Baseline · ExampleRISK · MEDIUM
5capabilities in release 1
9two-week sprints
1external dependencies

    An illustration of how the Scope Baseline works. Real baselines are agreed with each client and written down before engineering begins.

    Have software that needs to be done properly?

    Tell us what the business is trying to achieve. You do not need to arrive with a technical specification. If the opportunity is a good fit, we will help turn the business requirement into an engineering problem we can solve.

    Discuss a Project

    We review the context before the first serious conversation.