Development Methodology

At MUSINGWAY, we have adopted Extreme Programming (XP) as the Development Methodology as we feel that it can positively and significantly impact our processes and the delivery of services. XP is a deliberate and disciplined approach to software development. The main advantage of XP is that it lays stress on customer satisfaction. The methodology is designed to clearly understand the client requirements and deliver the software within expected time frame. XP empowers the developers to confidently respond to changing client requirements, even late in the life cycle. Communication, simplicity, feedback, and courage consistently followed in all the phases of the XP programming methodology enable timely delivery to the client while maintaining high quality standards. With regular client feedback it becomes easier to thoroughly understand and address the changing client requirements confidently. The XP Programming Life Cycle Model emphasizes the following:

XP programmers communicate with their customers and fellow programmers Keep the design simple and clean - never add functionality early Get feedback by testing the software starting on day one XP programmers are able to courageously respond to changing requirements and technology

What differentiates XP?

The main drawback of the conventional life cycle models is that it does not lay stress on regular client feedback. Till the end, the client is apprehensive about the software that will be delivered ultimately. XP overcomes this drawback by showing the clients and the developers the complete picture. In Extreme Programming, every contributor to the project is an integral part of the "Whole Team".

• XP emphasizes teamwork
  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 emphasizes not just testing, but testing well
  The analysis phase of XP starts with 'User Stories' that forms the backbone of all the consecutive phases of the life cycle model. XP programmers communicate with their customers and fellow programmers. They keep their design simple and clean. They get feedback by testing their software starting on day one. They deliver the system to the customers as early as possible and implement changes as suggested.



• More confident approach towards changing requirements
  XP programmers are able to courageously respond to changing requirements and technology. Too often a customer will see a real opportunity for making a system useful after it has been delivered. XP short cuts this by getting customer feed back early while there is still time to change functionality or improve user acceptance.



• Continuous Client 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. A safety net of tight mesh is created. Bugs don't get through twice.