SOFTWARE DEVELOPMENT METHODOLOGIES

Methodology – it’s a system of principles, as well as a set of ideas, concepts, methods, techniques and tools that define the style of software development.

Methodology is an implementation of the standard. Standards are only having some of the rules and leaving freedom of choice and adaptation.

Specific things implemented through the selected methodology. It determines how you will develop future applications. There are many successful software development methodologies. The choice of the methodology depends on team size, the specifics and project difficulty, stability and maturity of the processes in the company and personal qualities of employees.

Methodology is a core management theory of software development. To the existing classifications was added a general type of predictable and adaptive methodology, depending on the life cycle models (waterfall and iterative methodologies).

Projected methodology focused on the detailed planning for the future. There are scheduled tasks and resources for the entire project duration. The team barely reacts to possible changes. The plan is optimized based on work structure and existing requirements. Change of requirements can lead to substantial amendment of plans and project design.

Adaptive methodology aimed at overcoming the expected incomplete requirements and its constant changes. When the requirements change, the development team is also changing. Participating team can hardly predict the future of the project. There is a detailed plan only for the near future. More distant in time plans only exist as a declaration of project objectives, expected costs and benefits.

SCRUM – a methodology for small teams (up to 10 people). The whole project is divided into iterations (sprints) of 30 days duration. System functions are selected to be implemented in the next sprint. The most important requirement - immutability of the selected functions during the fulfillment of a single iteration and strict observance of deadlines for the next release, even if this product wouldn’t have all planned functionality. In order to determine the function of the system implemented by the previous day, the encountered difficulties and the next day plan Development Manager conducts daily 20 minute meetings that are called “Scrum”. Such meetings can constantly monitor the project progress to quickly identify problems and respond to them promptly.