AGILE literally means active , nimble , apt or ready to move. This leads to the visual of a swift creature able to move deftly through dense areas with relative ease. Today – we apply this term to Software development cycle. Software development activity traditionally represented large documents , bound blue prints and an army to develop the design – turn it into reality. Still the rate of failure / cost overruns didn’t seem to reduce.
That is when it soon dawned that the blue print design model was not exactly the ideal way to proceed with the software development. AGILE Development processes were soon developed. SCRUM , XP started evolving.
What are the advantages of AGILE DEVELOPMENT ?
AGILE DEVELOPMENT does not force the team to design the entire application / software module before they begin development. Development can be broken down in smaller modules. Developers focus on the problem at hand rather than develop the entire application. The main advantage lies with the customer (Product Owner) who can actually start reviewing his product earlier and suggest changes accordingly. This saves a lot of time – customer does not have to wait till the product is built to suggest changes.
How does Siddhatech follow AGILE DEVELOPMENT practices?
Siddhatech has developers who understand the AGILE process well. We have executed projects using SCRUM in the past. SCRUM unites the team together . If tasks are distributed evenly amongst the team members – the ownership factor for the product grows. It takes a couple of SPRINTS (SCRUM Terminology) to adjust to SCRUM and the new team – but once the team velocity is calculated – SCRUM is an easier model to follow.
How has it benefited Siddhatech?
Siddhatech primarily provides services to it’s clients – the majority of the projects that are executed here are defined by clients – requirements are sent by the clients. Miscommunication with the client is the major cause of a project failure. We keep the sprint cycles as low as two weeks. This gives the client time to review and provide feedback on the modules delivered after the completion of the sprints. Miscommunications , design failures , vision failures are all absorbed to a large extent when a project is executed following SCRUM.