Understanding the
requirements and
Discovery

Why this process is required

As Brian Tracy says: “Every minute you spend in planning saves 10 minutes in execution…”. Discovery is all about planning.

Together, we talk through each feature to determine how exactly it will work and what benefits it brings to the end product, define the exact pain you want to resolve, and build a product that exactly fits your business needs.

After studying and understanding requirements, we establish what else can be added or improved.

These and many more points are covered by the Discovery process and all together they are an integral part of a good development process.
Core of the process

Is it required?

Web projects often include work with old legacy code, so one of the main priorities is to check the state of existing solutions. In most cases, rewriting the solution from scratch is not an option, so the best we can do is to integrate modern frameworks and libraries in the existing product and optimize legacy code.

Defining the basics

Before actual discovery is started, we define what problem You need to resolve and how exactly the product You want to build is resolving it. We should form a shared vision on the end product, so both you and developers know exactly what should be built. Based on the vision, we set goals to achieve. Likewise, we collect key project information which allows us to make the discovery process more efficient, by passing the initial FAQs that almost always arise. It’s also important to set limitations as there is always a temptation to add more and more features to the product, even if they are not really needed.
discovery basics

Collect the requirements

The next step is to gather all sources of requirements, like functional specifications, user stories, use cases, wireframes, etc., and process them to see what can be added or improved. Besides technical requirements, we also discuss things like budget, specific deadlines, and milestones. Once we have a complete picture and understanding of the requirements, we can clearly set the amount of resources for development, both time and cost.

Project Scope and WBS

Once requirements are gathered and estimates discussed, we start work on the project scope, describing what exactly should be done in this iteration and what can be moved to the next one. Based on the scope of work, we form a Work Breakdown Structure document, that helps us to separate the entire project into logical parts. These logical parts are later used to set milestones for delivery, where each milestone is a completed piece of functionality you can fully check and confirm it’s working.

Wireframes and prototype

Simultaneously with WBS, we create a set of wireframes in order to schematically represent the future UI of the designed product. Wireframes are very important to understand the concept of the entire solution, as well as to see and identify possible bottlenecks. The final step of wireframe creation is an interactive prototype, which allows You to click through the elements of the app and feel how it will work in real life.

Assumptions and limitations

Project success is not only about the development team, but also about how involved You will be in the process. Timely and accurate answers to the questions are just as important as good coding. In this section, we discuss what will be done from Your end (like server access, account creation, etc.) in order to achieve smooth and easy communication with the team.

Benefits for you

Clear Vision
A clear vision of what documents are required to build the product.
Define the problem
Definition of the problem you need to resolve and steps to do it.
Organizing Requirements
Organization and systematization of the project requirements
Total cost
The vision of the total cost and time required to build the product.
Clickable prototype
Clickable prototype to see how the solution will work in real life.
Huge discount
Huge discount on Discovery if development will be done by our team!
Work with your team
Scope of work that should be done by your team
Budget saving
Budget saving and in-time delivery thanks to good planning

Examples

some of solutions we built

FollowIt

Follow the news like never before

Lottery App

Best 4D Lottery application

The Cultivist

The world’s global art club

Halfy Hour

Restaurant food at half price

FollowIt

Follow the news like never before

Lottery App

Best 4D Lottery application

The Cultivist

The world’s global art club

Halfy Hour

Restaurant food at half price