We adopt best practices of the industry in order to deliver results that meet expectations. It is our firm belief that beginning of the cooperation sets the stride for the whole project, that is why we have introduced project initiation framework - Inception.
We envision Inception as an extremely potent and resourceful way to get better understanding of the product and mold perfect solution. Also, it gives us a chance to align stakeholders’ visions and spark the inspiration within the development team.
The purpose of the Inception session is to study business goals, use cases, roles. And as the result to craft roadmap, which allows the team to adapt constructive approach from the start and deliver outstanding results.
For this process to be fruitful it is essential to set clear and well defined goals. These are the goals we aim to achieve after completing the inception process.
- Develop understanding of the business environment
- Set priorities for MVP and specify roadmap
- Minimize the risks
- Align product stakeholders
- Inspire the team
Inception is very organic and fluid, thus feels like one continuous process. Nevertheless, it has several logical stages that have to be completed in order to achieve desired results.
Introduction
-
Presentation
Customer showcases the product at its current state (even if it’s just an idea) , any information exploring peculiarities of the project is important.
-
Issues, benefits, risks/goals
Customer gives his perspective, helps us understand the context for the product and the rules of the market, as it is his domain. This will help the team to have better understanding of direction where they should be moving and what are their goals.
- Consumer
- Business goals
- Domain knowledge
-
Roles and workflow
At this stage we work on defining all the possible roles, workflow is defined for each role.
- Application roles
- Components
- Workflow screens
-
Prioritization
Further on all the technical information is organized into a roadmap according to the level of priority.
