For any company it is important that it has its procedures defined. The same should be clear to its clients so that both the parties remain on the same page at any given point in time and can also anticipate the project progress status knowing at which phase the project has reached.

Below mentioned is our step by step approach in brief of proceeding with the development of the project. We have tried our best to keep our procedure simple but giving high quality output.

1.Requirement Gathering
Requirement_Gathering
In this step we have cycles of meetings with our client to understand the requirements. Get the mockups ready and approved so that there is clear understanding of the structure and flow of the project before we proceed further. Also discussion on further future development so that when we start the project we make it such that it can accomodate future changes/features with maximum ease as possible. Our past experience says that not everything can be handled at the start itself as some unpredicted changes can happen in future but to reduce the chances of such changes coming up we can have some dicussions at the end to forsee the changes which might have more then 60% chance of happening.


2.Getting designs ready
getting designs ready

Once we get the ‘Understanding Document’ approved, we start off with getting the wireframes ready.This we do using ‘Balsamiq’ mostly to give a projected view of how the screens will look/How the placement of various components will be on screen.If further better view is required, we can use ‘figma’ to share the layouts


3.Approval of layouts
Approval of layouts

These layouts are shared with the client for the feedback and better refining of the look as per the clients requirements.


4.Database structuring
Database structuring

When designs are approved, we next get into the database architecture. This will be done at the internal team level to chalk out how the data will be saved and retrieved.


5.Milestone/task creation: Asana
Milestone_task_creation

Next, The Project is broken into milestones and each milestone will have certain amount of tasks mentioned under it.
Task management will be done on ‘Asana’. Each task we assign it to the respective developer, who will mark it as ‘picked’ once she/he begins work over it and ‘completed’ once it is finished. This helps us to track the progress over the milestone.


6.Up on test site
Up_on_test_site
When all points mentioned in a milestone are ‘completed’, we can move the developed functionality to a ‘Test phase' where the output can be mapped to the requirements and tested for any issues/bugs if present.
To track the issues we can either use ‘Asana’ itself by creating a section under the milestone to hold all issues/bugs that were encountered during testing phase.


7.If required first look on staging site
look_on_staging_site

If required we can have a ‘Staging phase’ which will host a copy of data of ‘live’ site. Here client can give final look at the functionality if satisfactory before making it ‘live’ or if some minor amendments are required can be carried out at this stage. After a certain period we can update the ‘Staging phase’ database with the copy of live database so that we have mirror of how any functionality change will react to dataset on ‘Staging phase’ itself.


8.Up on live

Last stage will be of pushing across the complete functionality/changes from ‘Staging site’ to live. This will be done by placing maintenance banner on your website and uploading the changes, once completed we check for all the viewable changes (we do not promote to do any CRUD operations on live DB to avoid any test data - which is invalid, to enter on live DB).


We also encourage to have at minimum one meeting over a week, ideally start of the week to prioritise tasks and for both the parties to have the basic idea of what can be expected at the end of the week.


We are open to suggestions as well as to the project management procedures that are followed at clients end and can incorporate the same into the respective projects.