This is the first of a series of posts I hope to present to explain the process followed at Auro Infotech while developing any project.
This series should help provide a full picture of the actual steps followed by the AI team members and help the clients get a better understanding of what goes into the minds of the AI folks when they are working on any project.
I hope to review each section on a regular basis and elaborate on the same.
Project Life Cycle Checklist:
CL – Client
PL – Project Lead
DH – Development Head
AC – Accounts Team
DE – Design Team
SU – Support Team
QA – QA Team
MGMT – Management Team
General:
All updates/emails should be posted in the forum before end of day.
All client emails/queries should be responded to within one hour of start of the day.
Send Weekly Project Report to Client – Project Lead
Post daily update on forum about the tasks handled in the project – Team Members
Enter time accurately under the right project version and phase in time tracker – Team members
Requirements Analysis:
CL – Come up with requirements
PL – Document requirements presented by the client and identify the modules involved
PL – study the modules and identify the time estimate for the project – after identifying the time estimates for each module, testing, etc.
PL – Prepare paper Workflow Design, scanned as PDF with AI copyright in all pages
DH – Review and approve the paper workflow design
DH – Present the paper workflow design and the time estimates to the client.
CL – Sign off on the paper workflow
PL – Prepare Resource Planning
DH – Review and approve resource planning
DH – Get client ok on the requirements and estimates
DH – Notify Accounts Team to raise invoice 1 of 3 for 25%.
AC – Raise invoice 1 of 3 for 25% to the client.
CL – Make initial payment.
AC – Notify DH and project team to go ahead with the project.
DH – Start project work if payment is received – Alternatively get management approval on forum to start project.
DH – Present Project Start Report with resource planning to AI management team and get approval for the same.
Design:
DE – Prepare static Screen Design with AI logo in all screens
PL – Review and approve Static Screen design
DH – Present Static Screen Design to client
CL – Sign off on the static screen design
PL – Prepare database design
DH – Review and approve database design
PL – Prepare component Design
DH – Review and approve component design
Coding:
PL – Complete coding
PL – Complete developer testing
PL – Coordinate with QA team and complete QA Testing Process
QA – Sign off on the application
PL – Present demo of the application to DH
DH – Review and sign off on the coding
DH – Notify Accounts team to raise invoice 2 of 3 for 50%.
AC – Raise invoice 2 of 3 for 50% to the client
CL – Make second payment
AC – Notify DH and project team to coordinate UAT
DH – If payment is received, Email Client with UAT links requesting them to schedule a time for demo – Alternatively get management approval on forum to start user testing
Testing
DH – Along with the PL, call the client and give a demo of the application on testing server
PL – Coordinate and complete User Acceptance Testing Process
CL – Sign off on the application on testing server
DH – Coordinate with client on the date of release of the application on live server
CL – Confirms the date and time when the application can be moved to live server
Deployment process:
PL – Coordinate the preparation of deployment document ahead of time and finalize it and submit it to the support team as soon as QA sign off is obtained.
PL – Work with the client and identify ‘Deployment Date and Time’ for migration when client will be available for ‘Promotion Completion Sign Off’. (This is not the Client Sign off, but a confirmation that the deployment looks ok and client can test later in detail to sign off.) – The client can give a written exception to the PL to complete this without the presence of the client.
PL – Decide and post the list of project team members to be available during the ‘Deployment Date and Time’. Each person identified by the PL must be present during this time. PL will take responsibility for any exceptions.
SU – Support team moves the files and dbs to live site and confirms to PL.
PL – Checks and confirm on forum if the site is up and working fine with out any error.
PL – Sends the details to the client and requesting them to sign off on ‘Promotion Completion’.
DH – Notify Accounts team to raise invoice 3 of 3 for 25%
Ac – Raise invoice 3 of 3 for 25% to the client
CL – Make third payment
AC – Notify DH on receipt of payment
DH – Release final code to clients if payment is received – Alternatively get management approval to release final code
DH – Email client asking for feedback on the project and status of any open issues, etc.
DH – Present Project Completion Report to the Management team to qualify for project appraisal and project reward.




QA Testing Process at Auro Infotech // Mar 10, 2009 at 2:38 pm
[...] Testing Process is embedded closely into our Auro Project Development Life Cycle model and hence is dependent on a few important [...]
Managing Scope Change or Scope Creep | Auro Infotech Blogs // May 14, 2009 at 3:32 pm
[...] 1. A well defined requirements analysis phase during which the team works with the client to come up with a full understanding of the project. This explained in detail in the Requirements Analysis Section of our Project Development Life Cycle [...]