How we develop your software project

Tell us who needs to use the software, what they are trying to accomplish and where the current process falls short. Share any existing application, sketches or examples that help explain the need.

You can begin with an early idea. If you already have requirements, a budget range or a target date, those help frame the discussion and identify constraints.

The first conversation helps establish whether the project fits our development services and what needs clarification before a proposal can be prepared.

We look at the main user journey, relevant systems and the information involved. Existing software may already cover part of the need through configuration or integration. A custom build should address a clear gap.

Some projects need an application assessment, a prototype or a focused technical check before the larger scope can be defined. For example, an integration may depend on an external system providing the required access. We identify what needs investigation and agree that work where it is useful.

The proposed scope should give everyone a shared understanding of the work:

• The users, workflows and capabilities included, with clear exclusions.
• The expected deliverables and checks used to review whether they meet the requirements.
• Assumptions, dependencies and decisions that could change the effort or sequence.
• Responsibilities for information, access, review, release and subsequent operation.

Estimates reflect that scope and its assumptions. Hosting, external subscriptions and ongoing work should be identified separately where they apply.

Your input might include explaining business rules, arranging access to a test system or reviewing a proposed flow. We discuss those needs in context and agree who can make the relevant decisions.

Where the experience needs clarification, flows, wireframes or prototypes can help you review it before implementation. Once the requirements are sufficiently clear, development can proceed through agreed portions of working functionality.

Reviews connect the work to the original task: can the intended user complete it, is the right information recorded and does the result reflect the agreed rules?

We also consider relevant exceptions, such as missing information, restricted access or a failed connection. The review approach and communication arrangements should suit the project and the people making decisions.

Review can reveal a better approach or a requirement that was not apparent earlier. When that happens, we discuss how the request relates to the agreed scope and what it changes.

A change may affect design, development effort, dependencies or the release sequence. Agreeing its treatment before implementation helps keep priorities and estimates understandable. Some requests may belong in the current release; others can be considered for later work.

Before release, review the delivered work against the agreed acceptance checks. Confirm the important workflows, relevant access and connected systems, and record any outstanding issues or decisions.

Release preparation depends on the application. It can include deployment arrangements, required configuration, data preparation and checks in the intended environment. Agree who authorizes release and who is responsible for operating the application afterward.

Handover can include the agreed project materials, practical documentation and a walkthrough of administration or routine tasks. Identify any remaining work and the route for reporting issues so there is a clear next step after delivery.

Feedback and actual use can reveal defects, usability improvements or new capabilities worth considering. Assess those requests against the product's purpose and the work already delivered.

Software maintenance and improvements can cover an agreed scope after an assessment. Responsibilities, availability and the distinction between ongoing maintenance and new development should be defined for that engagement.

Aatman Chhatbar coordinates the commercial relationship, project understanding and communication. Specialist partners are matched to the work the project requires, with roles and responsibilities discussed as part of planning.

The aim is to keep requirements, decisions and progress understandable throughout the engagement.

Learn about BusinessEye Development

Share what you want to build or improve, who will use it and what already exists. We will discuss the questions that need answering and a practical next step.

Discuss your project