‘Analysis’ is the process of detailed examination into smaller parts of a complex project in order to gain a better understanding to it. This technique is a formal concept and has great significance in the development of our products. We analyze the Product Development in three different stages that is Business, Requirement and Technical.
In the phase of Analysis, We focus on two main questions regarding the development:
- What problem are we trying to solve?
- Why will people choose our product to use?
Our Analysis team uses Kanban as a tool for defining ‘Epics’, ‘Features’ and ‘User-Stories’ and mapping of relevant user stories to each other neatly and then defining those stories as functional requirements as per business value, which helps with the smooth running. The Analysts work smartly by analyzing the mindsets of the users and future needs for taking the product to the next level constantly. Hence, it is an iterative process that circles between research, planning and analysis for constant upgradation of the product with respect to similar products available in the market of different competitors.
The responsibilities that are fulfilled in Analysis appear to be:
- Investigating Business Systems taking a holistic view of situation.
- Defining ‘Epic’, ‘Features’ and its underlying ‘User-Stories’ for the development team to implement after getting the sign-off from the business owners.
- Differentiating Most Viable Product (MVP) that is the backbone of the project and making sure that it remains the backbone, in spite of all the new upgradations.
- Regular Updation of stories as per the advancement of the project.
- Evaluating actions to improve the operation in line with proposed process design.
- Documenting the business requirements showing proper workflow with graphical representation and essential statements relative to the graphics.
Activities that we perform during Analysis:
- Our crucial working is primarily with the key stakeholders to formulate and communicate the business vision. It is a vigorous effort of translating the initial high level vision into something realistic.
- We then translate the requirements of the stakeholders into something that the developers can understand. Simultaneously, the resulting questions of the developers are translated into something the stakeholders can understand.
- The stakeholders are also explained about the technical issues behind what the developers are doing and why they need to do it.
- We validate the requirements of the stakeholders via technique such as reviews, walk-throughs, face-to-face communication etc.
- Last but not the least, we conclude the Analysis after identifying, modeling and then documenting the requirements along with business domain details.