The Agile Development Process
Requirements often change while the project is under development.
Traditionally this meant starting the project over from the beginning.
However, implementing multiple short project life-cycle iterrations
allow us to obtain customer feedback to ensure that the project is on
track. By taking this approach our customers are able to make changes
to the original requirements without throwing the whole project off
In order to ensure accuracy in our understanding of the desired results, we
document all aspects of our development process. Below are the types of
documents you may expect to receive during the development of your project:
Prototyping / Visual Design
- Use Case Diagrams
- Activity Diagrams
- State Charts
- Class Diagrams
- Sequence Diagram
The look and feel of the application is critical to its success.
Therefore a significant amount of effort is put into creating
prototypes of the application and letting our customers / end users
work with the application to ensure that design is both easy to use and