Processes and methodology
You get into the software industry and we see that there are lots of jargons that get thrown around. Though the practice of due processes does have its benefits, we have actually seen that there is a large gap between the certified and claimed levels and the actual practice of such processes during project execution. Therefore, we tailor our processes typically aligning them to customer needs and practices and adding those processes and practices that will bring in most benefit with the least pain.
Software development practices do normally follow the waterfall model and also variations of the waterfall model in practice of the Rational Unified process, where there is a practice of iterative phases, each with its own waterfall cycle. Our normal project phases include:
- Requirements Definition
- Analysis (Also defines the scope of the work)
- Design (Technical architecture, Details of Development)
- Development (Individual units developed and tested)
- Testing ( All test cases - Separation from Development)
- Turn-over
- Critical Support period during initial production
Depending on the type of project, we can use RUP, Prince2, SWEBOK, Agile/XP practices or any other processes or practices that customers need. We normally have PMI based Project Management practices coupled with weekly/monthly status reporting tailored by our expertise of executing a multitude of projects over several years.
