Home Page
   SW CMM® 2
   ISO 9001:2000
 
 

XP lets small teams develop software quickly in an environment of rapidly changing requirements. And what software isn't developed in an environment of rapidly changing requirements?

XP focuses on software production—not mountains of documentation.

XP places a premium on analysis and design—not unnecessary meetings.

Here's how it works:

  • You give us your requirements.
  • We give you realistic cost estimates.
  • You decide which features should be developed first.
  • We quickly put a system into production. We write clear, consistent code that's easy to maintain and enhance.
  • You use the software and tell us what you like.
  • We change what you don't like in incremental releases.
  • You have software that works every day.
  • You shift priorities, modify requirements, or stop the project
    • altogether-at any phase of the development life cycle. What you have keeps working.

 

Extreme Programming, or XP, is probably the most widely known and accepted of the agile software development methods. Now in use by organizations on a world wide scale, its popularity has grown immensely in the last few years. Developers enjoy XP's flexibility, which allows them to deliver working code in a short amount of time. Customers are thrilled to be able to interject requirement changes without causing major project revisions.

At NOLA, we not only practice XP, but we have become a recognized implementation leader having built the Cyndrus ADS product exclusively using XP practices. As part of this implementation, we constructed an entire XP framework for testing, metrics, configuration management, and requirements tracking. Our framework allows developers to focus more time and attention on delivering software, which provides value to our customers.

So no matter if you are just getting started or simply need some help, we can provide you with the personnel and products to make your agile implementation a success.

Traditional software processes are based on defined methods, where you plan what you want and then enforce it. With agile methods, you lightly plan what you want and then adapt to what you get. So, if you don't modify requirements or deliver working code until all construction and testing is complete, traditional methods will work fine for you. However, if you are constantly assessing the impact of requirement revisions and you need to get software in your users' hands quickly, consider an agile development method.

 
Home Page