Default custom software
development offering

Which services are included and which are out of the default scope of work (this page was updated on 19 September 2022).

Intro

Intro

This document is created to present what's included in our standard software development procedures. It applies to any kind of software development services that we render on an hourly or budget-cap basis. It aims to clearly define which services are included and which are out of the default scope of work.

The main goal of a software development procedure is to convert business requirements into code, configurations, and assets. To make this happen, we outline all required services, expectations, and deliverables.

We are happy to adjust those to the client's unique needs and guide them through technical difficulties. As those needs are mostly individual, we can estimate them precisely after several technical discovery sessions that need to happen in the first two weeks of our cooperation.

Engineering

General Engineering

We render services by allocating a professional's time to bring value to the project. This means that the professional focuses all the attention span on the project. Thus, it does not mean the professional brainlessly types code all the allocated time.

BN Digital provides services on the "as is where is" basis. The client has the right to pause services rendering according to a relevant contractual agreement.

While rendering engineering services, the professional could commit time to:

  • Reading the documentation and analyzing its contents;
  • Thinking how requirements could be converted into tangible results;
  • Looking for solutions, alternatives, and options for the solution and investigating how they work;
  • Creating proofs-of-concept, drafts, or other supplementary materials that work as an interim result and bring no immediate value to the project;
  • Writing the code;
  • Re-writing the code or improving it if it is required to write another piece of code efficiently;
  • Building content or data to test the functionality;
  • Testing and interacting with engineering outcomes;
  • Writing and composing documents, enriching code with comments;
  • Consulting with co-workers, fellows, and managers about project-related topics.

We strongly believe that bn's professionals are capable of defining the proper allocation of their time resources. This vision could be different from the client's, and the client is encouraged to highlight those discrepancies at a meeting.

To guarantee that the professional brings value to the client, BN ensures that:

  • An assigned professional has the right skillset and the right amount of time to commit to the client's project;
  • An assigned professional dedicates time to the sole project at a time;
  • An assigned professional works on prioritized tasks in a defined sequence provided by the client;
  • An assigned professional works based on their internal understanding of tasks and priorities if there is no input from the client;
  • An assigned professional has the right equipment to render services effectively.

The client gets:

  • Ability to manage, prioritize, and assign tasks to a professional.
  • A professional's time committed to the project.
  • All files and tangible outcomes with the corresponding IP rights produced by the professional within the time dedicated to the project.

Front-end development

Building a front-end piece of a system has nuances to be aware of.

  • In the process of high-fidelity design implementation, provided mockups serve as guidance if the otherwise is not clearly stated in writing.
  • If a client provides wireframes, those serve as guidance and supplementary materials but not requirements. In this case, the visual implementation would be defined by the professional.
  • If an element exists on a high-fidelity design, but its behavior is not described in the requirements set, it would be implemented based on the personal understanding of the professional.
  • BN Digital's professional would clearly communicate discrepancies in a timely manner.

Service rendering outcomes could be different from the high-fidelity designs in the next set of dimensions:

  • Content. As the content is purely client-managed, BN Digital can not guarantee the exact match of it with the provided mockups.
  • Out-of-scope functionality. If an element does not correspond to the requirements set, it might be ignored.
  • Requirements mismatch. If a design element mismatches with the requirement, the requirement prevails.
  • Design elements and assets. If those are not prepared properly, they might look differently.

Back-end development

  • In the process of business logic implementation, provided logic serves as guidance if the otherwise is not clearly stated in writing.
  • If non-functional requirements are not clearly defined in requirements, they would be implemented based on the professional's capabilities and understanding.
  • Technology has its limitations that could have an impact on the implementation. Those limitations and expected impact could appear at the time of service rendering, and those would be communicated by the professional in a timely manner. In such a case, the professional would propose a way to adapt to those limitations.

what's not included

  • bn's content management services
    • Content creation

    • Initial and ongoing content filling and management

    • Copy proofreading

  • bn's design services
    • High-fidelity designs

    • Illustrations and complex animations

  • requirements documentation
    • Requirements and specifications

    • Any form of documentation, guides, instructions

  • bn's deployment and go-live activities
    • Staging, QA, or live environment setup

    • Domain or hosting configuration

    • Continuous integration / continuous deployment setup

process

Handover process

The development service tangible outcomes are handed over as described in Default deployment and go-live offering.

Let’s work together.
We’d love to hear from you