Agile development process
The development process is based on agile development practices and uses our project management system:
1. Invite resources in the system and allocate roles: Programmers, graphics designers, QA and clients are invited into the project management system and are given appropriate rights to the system. The rights include but are not limited to inviting others, posting messages and creating milestones, accessing source code etc.
2. Upload all assets, specs and introduce: Assets and documents gathered that define the project scope are put into messages. Participants have access so that they can comment and seek clarification.
3. Demo area setup: This step involves setting up of staging servers and specifying access information for everyone. The staging servers also double up as demo areas. Clients are given access to this area so as to make sure we get appropriate feedack at all times. Uploading to these servers is done multiple times during a day.
4. Setup Milestones: Projects are divided in n number of smaller phases each marked with milestones. Milestones are extremely important in the sense that they provide an opportunity to us to identify potential hold backs and take corrective measures and make sure we reach goals on time.
5. Dev and QA: This duo is the most frequently done activity. For each phase and otherwise QA team constantly hunts for bugs and puts them in tickets. Tickets are allocated to the concerned resource(tickets are open). When a resource starts working the given ticket is accepted. Upon taking appropriate actions the resource marks the ticket as resolved. QA then determines whether resolved tickets are to be closed. If a ticket is found to be corrected then its marked as closed by QA. Please note that tickets can be created everyone on the in-house team and on the client side and can be directed at anyone from whom action is required.
During all of these steps the client has the ability to direct the resources towards any or all aspects of the development and QA effort.