Best Practises

Agile XP in Action...

No methodology is just a collection of rules to be performed in rote fashion, and XP, in spite of its famous rules, is no exception. Ultimately, any team's software development methodology needs to be customized to the team and their circumstances.

Four Fundimental Values:
Current best practises in eXtreme programming are based on four values.

• Communication: What is communicated to whom and when is important. Communication guidelines for eXtreme programming are incorporated in activities and practices and focus on communication between programmers in a development team and between the development team and the customer.





• Simplicity: A program built with XP should be the simplest program that meets current requirements. Designing for uncertain future requirements incurs a risk of spending resources on something that may not be needed. Simplicity in design and code improves communication because clean simple code easily understood by the every programmer in the team.





• Feedback: Within eXtreme Programming, feedback is related to different dimensions of the system development:
  
  

  • Feedback from the system: unit tests give programmers direct feedback about system stability each time changes are implemented.

  
  
  

  • Feedback from the customer: Functional tests performed by the customer early in the development cycle and occurring every couple weeks provide feedback and assure customer satisfaction with the development direction.

  
  
  

  • Feedback from the team: When customers come up with new requirements in the planning game the team directly gives an estimation of the time that it will take to implement.





• Courage: Simplicity stated that you always designing and coding for today and not for tomorrow. This sometimes may result in that you’re stuck in your design and that for anything else to implement you will need a lot of effort. Courage says to do a refactoring of the system. This means reviewing what you already have and make it so that future changes can be implemented more easily. Another example is throwing code away. Every programmer is familiar when dealing with a complex piece of programming you get stuck in your own design and coding and you’re working on it all today. When you come back the next day with a clear and fresh view you’ve solved the problem in half an hour.

J2EE
Java Servlets
Java Beans
Javascript

Microsoft
Visual Basic
.Net
.asp

Php
Perl
html
Dhtml

MySQL
Postgres
Oracle
SQL Serve

We specialize in the following systems:

• Medical & Insurance
• Manufacuturing
• Small Business Management Systems
• Resource Management Systems
• Systems for BPO:
• Offshore Medical Transcription
• Call or Incident Tracking
• Technical Support Services
• Web Analysis
• Disaster Recovery

We specialize in the following services:

• osCommerce Customization
• Open Source Implementation & Customization
• Reporting Modules
• System Maintenance
• Q/A processes
• Technical Support Services
• Linux Hosting Services
• American Managed Offshore Programming