We really feel that any approach we take to execute a project should be simple yet effective. It should not be like "oh man the work process is like a whirl pool". We use KISS process to work with the scope to implement the solution and execute the project successfully.
Our project management methodology is mainly based on Agile/Scrum. We have adapted the best practices of Agile and merged them with the realities of working with offshore teams in differing time-zones. If you are aware of other SDLCs methodologies you may also notice some best practices from Waterfall, Spiral, etc. during the course of the entire project lifecycle. In brief, it will roughly comprise of the following:
Sometimes called "Project Backlog", this is a collection of all the tasks that have been identified by the project team from the scope and Analysis. This is essentially a blueprint of the final product. In some cases, it's not frozen and may continue to evolve throughout the project lifecycle.
The entire project execution is divided into "time boxes" of equal duration with tasks from Backlog distributed across them. At the end of each Sprint, the project team reaches a milestone in development and almost always releases a build for client review.
The whole lifecycle is based around the concept of continuous regular feedback. Therefore our team will be in regular contact with your team to keep them informed of the progress, and as detailed above, provide incremental builds of the solution culminating in the final build which we shall use for sign-off.
As we run through the project, depending on the scope of the project, the project will go through the following stages during its lifecycle:
The Business Analysis team will work with your team to analyse your project requirements, create the backlog against the scope, and create requirement specification and wireframes for design and development.
The design team will design the necessary UI screens identified by the development team and provide the necessary design support to development team. The build of these UI screens into HTML (where applicable) will also be probably handled within the team but in some cases might be done directly by the development team.
The core development of the solution will then be taken up by the development team. This stage may start before the Design phase is over depending on the actual requirements of the project. As the project is developed, each sprint release will go through various testing stages and will be released only after taking due mandate to do so from the testing team and Project Owner.
Once the solution has been confirmed to have been delivered according to scope, it will be deployed in the agreed-upon deployment environment.
Since we use an iterative development methodology, the sign-off is also iterative. It can roughly be classified to three levels:
Almost every sprint will lead to a build review being released to your team and we shall solicit and expect feedback and a Sprint-Level sign-off from you. This is an informal sign-off and is primarily used by Project Owners to course-correct the remaining sprints to achieve a timely, within-budget delivery that you will be happy about.
When the solution has been implemented as per the scope, it will be put up for your formal review and sign-off. The project team will take your feedback and that stage and correct any functionality changes or misses to take the formal sign-off. This sign-off will authorize deployment and mark the beginning of the Warranty.
Once the solution has been deployed, the team shall again ask you to sign-off that the deployment has been done to your satisfaction.
Once a solution has been signed-off, we go into a warranty period where the project team will continue to be available to fix any bugs you may discover in the period of the warranty. This period is defined in the offered solution and may be extended through maintenance contracts.