DEV Community

Cover image for THE DISCOVERY PHASE. WHAT IS IT, AND WHY IS IT IMPORTANT?
GravelSoft
GravelSoft

Posted on

THE DISCOVERY PHASE. WHAT IS IT, AND WHY IS IT IMPORTANT?

They said that just starting is already 50 percent of the success in any endeavor. However, the stage that precedes the project's start in software development is critical for business outcomes, especially startups, as they often only have a basic concept. The invention phase aims to answer essential questions:

Is the idea feasible?

Will the merchandise survive the competition?

How to make it highly demanded by end-users?

Let's have a glance at the method of the invention phase, its deliverables, and kinds of projects that it's an absolute must.

What is the invention phase?
The pre-development stage, firstly, aims to eliminate financial risks for the client and make the event process as predictable and smooth as it is able. All project goals and requirements are gathered and analyzed by multiple perspectives: optimum architecture, interface, functionality, etc., and, consequently, the most straightforward implementation strategy and deadlines. Mistakes with planning may cost an excessive amount and sometimes are very hard to repair at later stages, which may cause considerable delays with an MVP launch. Unfortunately, to several businesses, it means failure.

Objectives:

Formulate clear product requirements
Define successful outcomes
Conduct an in-depth user research
Develop and test the customer journey
Analyze competition

Who is engaged?
The team counts on the specifics of the project and consists of individuals with diverse expertise to hide all aspects.

Core:

A business analyst responsible for detailed marketing research, identifying functional and non-functional project requirements, and assessing them against business goals.
A solution architect who decides on the foremost promising technology stack to form the merchandise scalable and maintainable.
A UX/UI designer makes sure the longer-term product has high usability and intuitiveness and presents the vision within the screen blueprint.

On request:

Front-end and back-end software developers who have relevant knowledge and knowledge with this sort of result.
A project manager who ensures the compelling connection between the client and the team and prepares the resulting documentation.
A tech lead - helps to clarify tech requirements, maps out the event process, and makes time estimates.

What result do you have to expect?
A profound understanding of the merchandise scope and competitive functionality
Knowledge of the end-user needs and the way to best satisfy them together with your product
A well-planned budget
An estimate of your time necessary for an MVP

What are the deliverables?
Architecture — a document/code or both with information about that structure of the project, which one can demonstrate how technical challenges are going to be solved.
Wireframes — to point out user interaction with the system and how all workflows are going to work.
Backlog — a group of tasks that require execution by the event team to implement Prototype, MVP, or Release versions of the merchandise.

When does one need a Discovery phase?
Each project is exclusive. However, certain types skipping this stage may have far-reaching harmful consequences:

Functional requirements aren't understandable

You have a general understanding of what your app should do from a user's perspective.

Non-functional requirements are vague or evolving.

You don't know what technologies and tools are helpful for your project, and it will involve the trial and error method to seek out.

A Proof of Concept (POC) is required.

You want to urge evidence within the prototypes that your idea is possible and commercially viable within the world.
https://gravelsoft.com/blog/f/the-discovery-phase-what-is-it-and-why-is-it-important

Discussion (0)