Aspects of Agile methodology

 

The image above shows the differences in the SCRUM and the XP(extreme programming) methodologies.

Both XP (extreme programming) and scrum are approaches you can use to develop software in a lightweight, iterative way. They are part of what's collectively known as agile software development methodologies, or simply "agile." 

XP: XP is one of the methods used for the software development process in agile technologies. XP stands for the Extreme Programming. Among the various aspects or methodologies present in the agile technologies, this method is considered as the important one. It has some significance than other methods. This method differs from the other methods in some areas. For example, if we consider the other methods it gives the importance for the predictability. But these methods give importance to the adaptability. This method has some common goals. And they are described below.

• The first and foremost aim of the XP is to improve the productivity and reconcile humanity.
• To develop the mechanism for creating the change in the society.
• Develop the path to improve the process.
• Develop the own style for development activities.
• Last but not least to develop the set of disciplines for the software development process.

SCRUM: SCRUM is also widely used framework for the software development activities. In this methodology the developer can create the check list with the priorities. There are some certain rules which are already followed in the scrum process.  The explanation of scrum process were already explained in the previous parts but lets refresh...

Here’s an example of how Scrum works: Feziwe meets with a customer to discuss her company’s requirements. Those requirements are the product backlog. Feziwe chooses the most important tasks to work on in the next two weeks. Her team meets in a daily scrum(the Daily Scrum is a 15-minute meeting specifically for the Development Team) to target work for the day ahead and address roadblocks(Roadblocks are anything outside the Scrum Team’s control that prevents a Scrum Team member from working at full capacity). At the end of the sprint, Feziwe delivers the work, reviews the backlog, and sets the goal for the next sprint. The cycle repeats until the software is complete.