The XP development cycle consists of two phases: ‘Release Planning’ and ‘Iteration Planning’. In release planning, we decide what should be delivered and in what priority. In iteration planning, we break the requirements into tasks and plan how to deliver those activities decided in release planning. The below figure ‘Actual… Continue reading
Extreme Programming (also termed as XP) is an agile software development methodology. XP focuses on coding of software. XP has four core values and fourteen principles. XP has these four core values: Communication: The team should communicate on a regular basis, share information, discuss solutions, and so on. Teams that… Continue reading
The main deliverable in Agile is a working software and not documentation. Documentation is a support to get the working software. In traditional delivery cycle, a lot of documentation is generated in the design and requirement phases. But we are sure most of the documentation were created just for the… Continue reading
Agile modeling defines a set of practices which can show us the way towards becoming successful Agile modelers. These practices are divided into two sections: “Core Principles” and “Supplementary Principles”. The figure below shows this in a pictorial format: Figure: Agile model principles Let’s understand one by one what these… Continue reading
Agile modeling is an approach to the modeling aspects of software development. It’s a practice for modeling and documentation for software systems. In one line: It’s a collection of best practices for software modeling in a lightweight manner. In abstraction, we can say it augments other software processes. For instance,… Continue reading
The dictionary meaning of Agile is quick moving. Now how does that apply to software? The Agile development methodology considers software as the most important entity and accepts user requirement changes. Agile advocates that we should accept changes and deliver them in small releases. Agile accepts change as a norm… Continue reading