At Acism, we are equipped to follow Waterfall or Agile practices, as per the project requirements.
Waterfall vs Agile Process
Waterfall calls for very elaborate planning and careful execution. It needs the requirements and the software design to be detailed out in elaborate documents. Also, requirements once defined cannot be tweaked at a later stage. Most customers find these restrictions difficult to live with.
Agile processes are less rigorous. We follow agile best practices (such as scrum, planning poker, retrospectives, burndown tracking) on our engagements. Incremental releases at the end of every second week give a great visibility to our customers, as they get to see the real application as it gets developed. Agile processes impart flexibility to the project, which means the ability to do course corrections as we go, while keeping the overheads low. This works well for most customers.
Acism has its own checklists for common tasks in development, testing and project communication. The use of checklists brings down the possibility of missing out on any of the items.
Some other best practices such as unit testing, code reviews, automation testing, performance testing, tighter security are optional on engagements. They need an upfront investment of effort, but give benefits over the long run. We help the customers to weigh the value vs overheads of these practices.
Project communication is the single-most important area which can make or break an engagement. We take it very seriously at Acism. We built a tool Kommbox to manage the project communications in a central place. The status of the project tasks and discussions are available to all the stakeholders through Kommbox.