First of all, we sign an NDA
A non-disclosure agreement is a contractual contract that prevents one party from releasing sensitive information to another.
We start with Pre-discovery stage for gathering information about requirements and client's expectations to estimate of the project
The pre-discovery stage is an important step in the development of a project, which involves ensuring that all of the parties have a common understanding of the goals and the team's approach.
When a client approaches us, we get in touch with them to discuss the process and proceed with all required formalities.
In the pre-discovery phase, the primary goals are to:
- Understand the problem space
- Ensure funding supports Agile delivery of service, not an output
- Align the team's desired outcomes, assumptions and expectations
- Plan how to approach the research in the discovery phase
- Set clear expectations with executives and stakeholders
NDAs are private contracts that can be used to protect trade secrets and confidential information. Having a signed non-disclosure agreement is very important to prevent the theft of confidential information. It can also help the parties reach an agreement in writing. Some NDAs provide for an extended period of secrecy to prevent the unauthorized disclosure of certain confidential information. The penalties for violating an NDA are usually included in the contract. These can include the loss of business opportunities or profits.
Being able to share information is very important when it comes to securing a loan, establishing a new client, or hiring a new team member. Since non-disclosure agreements have been around for a long time, they have helped preserve the trust that comes with this type of contract.
Some of the information that could require a non-disclosure agreement is sensitive or classified. It could include various details such as a company's manufacturing process or proprietary formulas and technologies.
We sign an NDA at the initial stage of collaboration. Our clients provide us with information about business processes, intellectual processes behind the existing systems and processes, product roadmaps, and in some cases, customer and financial data. Certainly, this information is classified as sensitive, and it needs to be protected legally.
Only after that we can move to data exchange.
We collect general information about the project
It includes information about the project, its requirements, the client's expectations. The right requirements help the development team get the most out of their work. It can result in faster project delivery and lower cost.
We divide requirements in 4 categories:
Business requirements are often defined as high-level goals that an organization needs to meet in order to maximize profits. These requirements can be created by end customers, investors, and software designers.
The user interface requirements allow the system to accomplish actions that can be performed by end users, and it should also provide the necessary information for the end users.
Functional requirements are usually focused on the features that can solve specific problems encountered by the end users.
Non-functional requirements are typically not focused on the main functional requirements. They can also include requirements related to the product's quality attributes, performance, and integrity
All this information allow us to a rough estimate of the project to provide you with an idea about how the development process will proceed.
By the end of stage, we prepare discovery proposal
The pre-discovery phase's deliverable is a fleshed out proposal document that includes a build spec, an estimate, schedule and terms.
But it is also the beginning of the next phase, the Discovery stage.
