Engagement Process for Enterprise Application Development

Published by Wes on

What to expect from Entexture

We have a proven process that delivers the highest level of quality custom application development. The expert technical team at Entexture will guide you through the software development process and ensure your project is a success.

This is the overview of our client engagement process.

1. Scope Of Work (Project Scope)

The first thing you need to do as a stakeholder is to define the scope of work for the project. See an example scope document. This document should define the goals and uses of the software. It should clearly explain the need and the expected deliverables. A scope of work normally includes a requested feature list and a description of the users and devices that will access the software.

The scope of work is not the final contractual document. Creating custom software takes a lot of planning and research. The development team needs to fully understand your business and the goals of the application.

Normally when you send out an RFP, you will include your scope as part of the RFP.

2. Scope Review and Ballpark Estimate

We will review your project scope and come up with a ballpark estimate for the project. We do not charge for ballpark estimates. You can email us your scope of work if you would like us to review it and provide you with a free estimate.

If our ballpark estimate is in line with your budget for the project we can proceed to Discovery.

3. Discovery

We will meet with your team to review your scope of work and get detailed information in order to create a requirements document. This gives us a chance to meet the team and get a more complete understanding of the project.

Depending on the scope and complexity this may require more than one meeting. It may also require a retainer to cover the cost of creating your requirement document. All of these details will be worked out in the first discovery meeting.

Not all projects require a retainer or R&D after discovery. Small and low-risk projects normally do not require more than a single meeting. In this case, we will not provide you with a requirements document beyond our formal proposal.*

4. Requirements Document

The requirements document is the counterpart to the scope of work. It will address each request in the scope and describe the solution and how it will be achieved. It will outline assumptions and deliverables.

The goal of the requirement document is to ensure that both parties have a complete and full understanding of what is expected. A well crafted and detailed requirement document helps avoid miscommunication and aligns expectations. It ensures we are all on the same page before any work begins.

If you purchased a requirements document we will provide you an electronic copy when it is completed.

5. Formal Proposal

Once we have a completed requirements document, we will create a formal proposal. The proposal will consist of the requirements document with dev hours estimated for each section. The proposal also contains various standard process documents that define what will be delivered and when it will be completed.

This proposal will also serve as the contract. Once it has been accepted, the document should be signed and returned with the specified deposit and work will begin. No work will begin without a deposit.

We coordinate our billing with our deliverables so you are paying for the work as you go. We normally invoice every two weeks over the span of the project. Final payment is due on delivery.

Contact Entexture today for a free ballpark estimate on your project.

*If there will be substantial work in creating an in-depth requirements document we do require a retainer. The retainer will bill for the hours needed to research and create the requirements document. Unlike our proposal, which is confidential, you are welcome to share your purchased requirements document with whomever you choose.


Leave a Reply

Your email address will not be published. Required fields are marked *