. .
 
 Home  Capabilities  Development Methodology
   
picture  
submenu 5 Infrastructure Competency Center Quality Business Continuity Development Methodology Security Policysubmenu 5
 
 
Introduction  

netlinkblue, is always eager to provide methodology that will enhance customer satisfaction. As a result, we have adopted Extreme Programming (XP) as the Development Methodology since we felt that it could positively and significantly impact our processes and the delivery of services.

Extreme Programming (XP) was conceived and developed to address the specific needs of software development conducted by small teams in the face of vague and changing requirements. This new lightweight methodology recognizes that projects have to work to achieve this reduction in cost and exploit the savings once they have been earned.  

The XP programming methodology consistently follows communication, simplicity and feedback at all stages to enable timely delivery to clients meanwhile maintaining high quality standards. Regular client feedback helps in thoroughly understanding client requirements in order to address the issues confidently. The XP Programming Life Cycle Model highlights the following:

  • XP programmers value interaction with their customers and fellow programmers.  
  • Insist on keeping the design basic and easy by avoiding functionality early.
  • Tests software from day one to get feedback.
  • XP programmers are equipped to courageously respond to any changing requirements and technology.

What sets XP apart?
Conventional life cycle models do not lay stress on regular client feedback. This causes clients to be constantly apprehensive about the software that will be delivered in the end. XP’s transparency overcomes this obstacle by showing the clients and the developers the complete picture.

Advantages of XP:

  • XP emphasizes teamwork
    In Extreme Programming, every contributor to the project is an integral part of the "Whole Team". Managers, customers, and developers are all part of a team dedicated to delivering quality software. XP implements a simple, yet effective way to enable groupware style development.
  • XP only believes in sound testing.
     'User Stories' forms an integral part of all the consecutive phases of the life cycle model. Communicating with their customers and fellow programmers forms the backbone of XP. They keep their design simple and clean. They get feedback by testing their software starting day one and deliver the system to the customers as early as possible to implement the suggested changes.
  • Prepared for changing requirements
    XP programmers are prepared for any changing requirements and technology.  XP short cuts this by getting customer feed back early while there is still time to change functionality or improve user acceptance.
  • Consistent Customer Interaction.
    Tests are automated and provide a safety net for programmers and customers alike. Tests are created before the code is written, while the code is written, and after the code is written. As bugs are found new tests are added. This is to ensure that bugs don’t get through.