Welcome to ahex technologies

Ahex Development Process

Our mobile app developers know how to create top-notch user experiences on Android. We design applications with attention to detail, and have deep expertise in every aspect of Android app development, resulting in extraordinary digital experiences.

Ahex Development Process
01

Discovery Workshop

Objective 

  • To discuss the project with the stakeholders.
  • Establish a broad idea about the goals and business objectives of the project.
  • Understanding the competitive landscape, target audience, market, and geography.
  • Laying down assumptions and constraints.
  • Coming with a high-level epic mapping.

Team Members Involved

  • Project Manager
  • Project Owner / Stakeholders
  • Business Analyst
 

Outcomes

  • Have a clear idea about the initially conceived goals to be achieved from the project.
  • Understanding the project stakeholder’s expectations.
  • Identifying the long and short-term goals.
  • Getting the input and clarification on all open-ended points.
  • Gather as much information as possible required for the planning phase.

Outcomes

  • To get all the requirements documented in as much detail as possible.
  • Identify and communicate the assumptions and challenges.
  • To get the project stakeholder’s approval and signoff on the documentation and project plan.
Deliverables
  • Detailed technical Specification
  • Wire-frames
  • User Stories
  • Project plan with detailed milestone/sprint planning
  • Test cases and scenarios
02

Planning

 Objective 

  • Create all relevant documentation required for the successful execution of the project.
  • Getting confirmation and approval from the stakeholders on the documents and materials.
  • Defining the project plan.
  • Defining the Test plan.
  • Outline the design and branding guidelines of the project.
Team Members Involved
  • Project Manager
  • Tech Lead
  • IA & UX Lead
  • UI Design Lead
  • Test Lead
03

Design

Objective 

  • UI Design of all the project screens based on the approved wireframes and design guidelines.
  • Web, Tablet and Mobile specific designs.
  • Getting system UI Designs approved and confirmed by the client.
  • Design application architecture
  • Project workflow definition
  • API /Services request-response structure

Team Members Involved

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

Outcomes

  • UI design of the pages.
  • Visual prototype of the application.
  • Finalized application architecture.
  • API services definition.
Deliverables
  • UI Designs of the projects
  • Clickable prototype on Invision platform
  • Source files in either Photoshop or Sketch format

Outcomes

  •  API endpoints.
  • Functional FE with integration with the BE.
  • Application ready for further testing at the end of the development cycle.
Deliverables
  • API endpoints documentation.
  • Application codebase ready for further testing.
04

Development

 Objective 

  • Development of FE, BE, Services.
  • Module-wise development spread across sprints.
  • Stakeholders review at the end of each milestone/sprint and integrate changes.
Team Members Involved
  • Project Manager
  • Tech Lead
  • Front-End Developers
  • Back-End Developers
  • QA Engineer
05

Testing

Objective 

  • Testing the completed code at the end of each sprint.
  • Reporting and fixing of bugs.
  • High-quality code ready for UAT.
    .
Team Members Involved
  • Test Lead
  • Tech Lead
  • QA

Tools

Outcomes

  • Reported bug list
  • Fixed issues in the codebase.
  • Code ready for UAT.

Deliverables

  • Code ready for UAT

Maintenance

06

Objective 

  • Fixing reported bugs from the end user.
  • Product enhancement through an agile approach.
  • Keep application secure through a regular security audit.
  • Back up of application DB.
  • Upgradation of the system based on new version release.
  • Monitoring of the traffic and server load and optimizing according to the business needs.

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

“Improvements to process (No finger pointing!)”

Client along with the Project Manager & Team Lead

Sprint Delivery

2-3 weeks

1-2 hours

Demonstration for the client.

Client along with the Project Manager & Team Lead.

Code Reviews

Bi-Weekly

3-4 hours

Code Review

Tech Lead

Collaboration Tools

Let's Talk

Looking for a Solution? Let's Talk

100+

DEVELOPERS

11+

YEARS IN OPERATION

110+

GLOBAL CLIENTS

AWARDS & RECOGNITION

Hey! there 🙂


    Allowed file formats are (jpg, jpeg, png, docx, pdf, txt) less than 10 MB