Prepare SOW
This is the first step of project lifecycle where we define what we are going to cover in the project.
Budgetary Estimates
Based on the understanding we estimate that what will be the cost that will be involved in developing the project.
Integrated Project Plan
In integrated project plan, we make a detailed document on how we will proceed on the project and also we try to foresee all the roadblocks that we will face in the project and also how we remove those roadblocks.
Screen Design
Now we come to screen design where we discuss with the client in details and make screen designs and take design sign off from the client. Design sign off depends on the type of project.
Database Design
After taking the design sign off we are clear on almost all the features of the application and we start designing the database.
Technical Design
In technical design senior programmers design the total code structure for the application.
Work Breakdown Structure
Based on the understanding of the features of the application we will develop the timeline for each feature, programmer involved, expected date of completion, deviation in expected date if any.
Test Plan
When coding comes in progress, at the same time we make a test plan, we give a detail description of how we are going to proceed with the testing of each feature, what data will be entered and what result is expected and what is the actual result.
Project Schedule
Project schedule gives the broader timeline for each milestone and status of each milestone.
Setup Test Environment
We usually have a testing server where we make a testing URL and space for uploading the code. We upload the code cluster by cluster on to the server.
System Verification
On the testing server testing team test the application by entering the data to break the code and also note all the results that how the system is behaving.
System Validation
After the team has tested the application project manager coordinate with client to cross verify the code for bugs.
Setup Beta Server
After the validation is done and the client has approved the code is uploaded to the beta server. On this server, we run a password protected application.
User Acceptance Testing
Since the beta server is password protected, the limited number of users accesses the site and uses them to a real time normal users for a small period of time to get the real time feeling of the application. Once these users are satisfied the password is removed and the site is made live.
Project Closure Activities
After the site is made live, we make a file where we keep all the documents related to the project. All the members of the team meet and discuss the problems that they faced in the project and how they overcame that. They also discuss the learning from the project and archive project file for future reference.