• You will be provided with a brief walkthrough of our company, to give you an idea of what we can do for you.
• We work with you to understand your business, your ideas and expectations.
• We will analyse your existing product to understand its current issues and its potential when moving forward.
• If there is difficulty in assessing the project requirements, then we will help you in creating a requirement documentation through a BA engagement.
• Once the requirements are clear we will recommend the best possible approach and tech stack to help achieve your product goals.
• A project management tool is used to track progress. Our preferred tool is GitLab. PM adds task & features to GitLab and prioritizes them based on requirements

MSA

• It's a contract between the vendor (NeoITO) and the Client (You) that outlines our general company policies.
• The MSA encompasses details like our payment models, guidelines to be followed by both parties.

SOW (Statement Of Work)/Work schedule

The SOW document is the working agreement between you and NeoITO. It includes details like:

• Project commencement date
• Project duration
• Project deliverables
• Payment terms
• A project can include multiple SOW depending on the different phases of the project like BA phase, design phase and development phase.

• Our BA interviews you and other key members of your team to achieve a deep understanding of your business, the existing product and your target customers.
• He will research the existing market for similar products and provide inputs on new features that will bolster your product.
• Contributes his ideas to improve upon your existing ones.
• He will help to set the workflow of your project.
• Create low fidelity wireframes.

• Our BA interviews you and other key members of your team to achieve a deep understanding of your business, your ideas and your target customers.
• He will research the existing market for similar products and provide inputs on features that will bolster your product.
• Contributes his ideas to improve upon your existing ones.
• He will help to set the workflow of your project.
• Create low fidelity wireframes.

• It includes the purpose, scope, risks and constraints and alternative solutions that pertain to your product requirements.
• The document will also define all the use cases (actionable items in the solution or product).
• It will include workflow diagrams of user journey, and wireframes of all the user interfaces.
• Functional requirements are also stated in the document which shows how each use case scenario is carried out by the system.
• The scalability, performance, responsiveness and security of the product are grouped as non-functional requirements in the document.

• He uses the BRD and system appreciation document to creates the system architecture and determines the feasibility, scalability and risks involved while developing the architecture.
• He determines the best combination of tech stacks, the number of developers required and how the different development tasks should be split.
• The architect confirms the budgets and timelines for the project.

• He uses the BRD and system appreciation document to creates the system architecture and determines the feasibility, scalability and risks involved while developing the architecture.
• He determines the best combination of tech stacks, the number of developers required and how the different development tasks should be split.
• The architect confirms the budgets and timelines for the project.

It includes:

• The overall description and functionality of the system.
• The software architecture diagram and DB design.
• The technologies to use and major constraints that can impact the design.
• A set of guidelines for developers to follow.

Technical Lead:

He is responsible for

• Overseeing the development process and leading the team.
• Creating development goals for every developer
• Reviewing the codes and conducting security audits
• Setting deadlines for each task

Frontend Developer:

He is responsible for

• Writing codes that run on the client-side (the user browser).
• Converting the designs to Html/UI screens.
• Builds the overall functionality of the app.
• Creating the user interface and architecture of the user experience.
• Ensuring designs are compatible with mobile devices.
• Common tech stack: Angular, React, Vue.js, React Native, Flutter.

Backend Developer:

He is responsible for

• Writing codes that run on the server side.
• Creating logic that helps the app function properly.
• Optimizing the app's speed and performance.
• Connecting the frontend of the app to the database.
• Common tech stack: AWS, Google Cloud, Firebase, MongoDB, PostgreSQL, MySQL.

Project Manager:

He is responsible for

• Splitting user stories into sprint backlogs
• Prioritisation of user stories
• Preparing estimates
• Assigning internal deadlines
• Tracking progress
• Conducting daily scrum calls
• Client interaction for additional requirements gathering

User stories: They define how a particular feature will work from a user perspective

GitLab board consists of 5 issue boards:

• Backlogs: All the tasks in the sprint
• To Do: Tasks assigned to each developer
• In progress: Tasks under development
• Test: Completed tasks for testing
• Closed: Finished tasks

• Sprints: They are short iterations of work that has to be completed and put up for review within that time frame.
• Each successive sprint involves the development of more features along with bug fixes of the previous sprint. This ensures a streamlined process is maintained throughout the development cycle.
• Milestones are placed after a set number of sprints where we showcase a functional product at various stages of completion