1. Discovery workshop

Objective

  • Run through the entire project with the client based on the initial proposal and agreement.
  • Establish a detailed idea about the goals and business objectives of the client.
  • Understanding the competitive landscape.
  • Understanding the target audience, market & geography
  • Clarifying all queries and doubts which the team has, post initial analysis.
  • Understanding and documenting client’s design and branding preferences
  • Laying down assumptions and constrains!
  • Coming with a high level epic mapping.

outcome

  • Have a precise and clear idea about the client’s and project’s goals
  • Have a clear idea about the likes and dislikes of the client.
  • Getting client’s inputs and clarification on all open-ended points
  • Having all the information required for the planning phase.

team members involved

  • Project Manager
  • Tech Lead
  • IA & UX Lead
  • Project Owner / Client
  • Business Analyst

Tools

Figma

Google Jamboard

Confluence

Miro

Notion

2. Planning

Objective

  • Creation of all relevant documentation required for successful execution of the project
  • Getting confirmation and approval from the client on the documents and materials
  • Defining the project plan
  • Defining the design and branding guidelines of the project

outcome

  • To get everything documented in detail, leaving nothing for chance or assumption
  • To get client’s approval and signoff on the documentation and project plan
  • To have a well-defined and precise planning of the project

Deliverables

  • Detailed technical Specification
  • Detailed Functional Sheets
  • Wire-frames
  • User Stories
  • Project plan with detailed milestone/sprint planning
  • Test cases and scenarios

team members involved

  • Project Manager
  • Tech Lead
  • IA & UX Lead
  • UI Design Lead
  • Test Lead

Tools

Figma

Google Jamboard

Confluence

Jira Software

Notion

3. Design

Objective

  • UI Design of all the project screens based on the approved wire-frames and design/branding guidelines
  • Web, Tablet and Mobile specific designs depending on the project.
  • Getting the overall UI Screens approved by the client.

outcome

  • To get the UI elements approval
  • To get client’s approval and signoff on the project UI
  • To have a well-defined and precise user-flow of the project

Deliverables

  • UI Design Screens of the projects
  • Clickable Prototype
  • Source files

team members involved

  • Project Manager
  • IA & UX Lead
  • UI Design Lead
  • UI Designer

Tools

Figma

Adobe Illustrator

Adobe Photoshop

Jira Software

Zeplin

Notion

4. Development

Objective

  • Catering the requirement for frontend, backend, web services, and API development integration.
  • Prepare a strategy for Agile Scrum methodology
  • Factor the aspects of multi-tenancy, scalability, 3rd party integration
  • To set up a 2-3 week frequency for sprints/milestones
  • To set up a CI/CD methodology
  • Crafting an optimized clean code structure
  • Involve client review in each sprint/milestone

outcome

  • To keep the client updated with finished sprints
  • To get client’s approval for each finished milestones
  • To involve the client in the CI/CD process

Deliverables

  • Deployable version of the project
  • Git Repository with source code

team members involved

  • Project Manager
  • Team Lead
  • Front-End Developers
  • Back-End Developers
  • QA Engineer

Tools

Bitbucket

Gitlab

Kubernates

Jira Software

VS Code

Codemagic

5. Test & Deploy

Objective

  • Each sprint/milestone is tested manually.
  • Bugs are reported and added to product backlog.
  • Upon bug fixing, quality release is provided and then the final demo of the sprint is sent to the client for approval.
  • Regression testing after each sprint to ensure proper functioning of the previous approved sprints/milestones.

outcome

  • To get client feedback on each tested sprint
  • To get client confirmation to move from a milestone to another
  • To involve the client in the CI/CD process

Types of testing

  • Unit Testing
  • Manual Testing
  • Regression Testing
  • Security Testing
  • Automation Testing
  • Load & Stress Testing
  • Performance
  • Code Review

team members involved

  • Project Manager
  • Account Manager
  • DevOps Engineer
  • Lead Developer
  • QA Engineer

Tools

Selenium

X Ray

Kubernates

Digital Ocean

Amazon EC2

Google Cloud Run

6. Maintenance

Objective

  • Product enhancement through an Agile approach
  • Regular Security Audits
  • Bi-weekly code back-ups
  • Constant upgradation of the system based on new software/version release
  • Monthly System Testing to find bugs, incompatibility and error
  • Monitoring of the traffic and server load and optimizing according to the business needs.

outcome

  • To keep the client’s product available for his target
  • To optimize the product with the technology upgrades
  • To keep the client on track with his product performance

Tools

Bitbucket

Gitlab

Kubernates

Jira Software

VS Code

Codemagic

Project Communication Structure

Daily Scrum Standup



Mon -Fri
30 minutes



Check previous day’s work, current day’s plans, any queries, hurdles etc



Project Manager with the entire Project Team

Weekly Review



Weekly
45-60 minutes



Process Improvement, Feedback Gathering, Client updates, etc ...



Client along with the Project Manager & Team Lead

Sprint Delivery



2-3 Weeks
60 minutes



Demonstration for the client.




Client along with the Project Manager & Team Lead.

Code Reviews



Bi-Weekly
2-3 hours



Code review





Tech Lead


Collaboration Tools

We make sure to use the tools that are top of the market to bring your ideas into reality. Our careful selection of tools makes sure that your ideas are executed with the highest level of efficiency.

Engagement Models

We aim to deliver rockets out of every projects and finish our problem-solution approach with the top level of efficiency and dedication.

When the scope of your idea is not clear, we tend to go with the T&M based model to provide you with more efficiency as we continue with your project.

When the budget does not match your requirements, we tend to go with the Kanban based model which is a Story Point system to provide you with more efficiency as we continue with your project.

When the project is quite heavy and can take a lot of resources, we tend to go with the Sprint based model  to provide you with more efficiency as we continue with your project.