We employ the latest Agile software development processes to give every customer the following benefits:
What HSS has to offer?
- Agile software development backed by a powerful software philosophy delivering working software in weekly iterations.
- Meeting the highest level of quality which is at the heart of the HSS philosophy.
- Partner with a small dedicated team of professionals who have thorough experience of embedded software development.
- Effective customer communication through on-site customers, web meetings, phone and email.
- A dedicated client desk is available for customers to drop in at any point and check the status of the project having access to all the latest code and progress done so far.
- Test Driven and Pair Programming development teams that deliver well tested, well engineered software that exceeds all customer expectations.
- Design simple and robust software adhering to well defined coding standards.
- ATP (Acceptance Test Plan) is agreed upon at initial stages of a project and worked upon throughout the project.
- Continuous Integration to catch problems early and fix them sooner. Rigorous testing is performed using a dedicated test machine performing comprehensive set of tests using automated scripts.
- In a nutshell, satisfied customers as they get exactly what they want, QUALITY.
Why Agile?
- Craig Larman, a notable consultant and author has done an extensive research in the book Agile and Iterative Development: a Manager's Guide about problems with the traditional waterfall model. Some quotes from the book below:
- "In a study of failure factors on 1,027 IT projects in the UK [1] (only 13% didn't fail), scope management related to attempting waterfall practices (including detailed up-front requirements) was the single largest contributing factor for failure, being cited in 82% of the projects as the number one problem, with an overall weighted failure influence of 25%."
- "Other significant evidence of failure applying the waterfall comes from one of its most frequent users in the past, the USA Department of Defense (DoD). Most DoD projects were required—by the standard DOD-STD-2167—to follow a waterfall lifecycle. A report on failure rates in a sample of earlier 2167-era DoD projects concluded that 75% of the projects failed or were never used [2]."
[1] Thomas, M. 2001. "IT Projects Sink or Swim." British Computer Society Review.
[2] Jarzombek, J. 1999. The 5th Annual JAWS S3 Proceedings.
