Agile Modeling is a practice-based methodology for modeling and documentation of software-based systems. It is intended to be a collection of values, principles, and practices for Modeling software that can be applied on a software development project in a more flexible manner than traditional Modeling methods.
Most agile methodologies are aimed at minimizing the risk by reducing the development of a series of short cycles called iterations, which typically last two to three weeks. Each iteration of itself looks like a miniature software project, and includes all tasks required for the issuance of the mini-increment of functionality: planning, requirements analysis, design, coding, testing and documentation. Although a single iteration is usually sufficient to produce a new version of the product, it is understood that the flexible software project is ready for release at the end of each iteration. At the end of each iteration, the team performs a re-evaluation of priorities for development.
Agile-methods focus on direct face-to-face. Most of the agile-teams are located in the same office, sometimes called the bullpen. At a minimum, it includes a "customer» (product owner - the customer or his authorized representative, determines the requirements for the product, this role can perform the project manager, business analyst or a client). Office may also include testers, interface designers, technical writers and managers.The basic metric is the agile-methods work product. Giving preference to direct communication, agile-methods reduce the amount of written documentation, in comparison with other methods. This has led to criticism of these methods, as undisciplined.
The basic metric is work product. Giving preference to direct communication, agile-methods reduce the amount of written documentation, in comparison with other methods. This has led to criticism of these methods, as undisciplined.