Aspects of Agile Methodologies

Two aspects of agile methodologies.

 Agile methodologies comprise a variety of framework that focus on a broad range of project management chambers. Streamlining collaboration through Kanban, simplifying complex projects through Scrum and improving software quality by employing Extreme programming. Each Agile methodology functions on 12 main principles connected by the Agile manifesto, with technical disparities in their characteristic features and their model on which they function.

SCRUM:

Scrum is a lightweight process framework that utilizes and applies agile project management in its most rudimentary form, that is, Scrum focuses on breaking down complex software development into small iterations called sprints. A sprint is a time-boxed period that lasts between two or four weeks. Each sprint is marked with milestones that are the teams top priority which they work to achieve. Scrum operates on a handful of artifacts that are designed with single objectives of maximizing transparency and providing opportunities for adoption and introspection. These are: Product backlog, Sprint backlog, Increments, Scrum team roles and responsibility, Product owner etc. The scrum framework works on a set of prescribed and regulated events, Each event itself is time-boxed. 

Extreme Programming (XP)

Like scrum, extreme programming is another lightweight agile project management methodology that focuses on adapting change to accommodate client and customer preference. It is called extreme programming because the practices involved in this lightweight agile project management are thrust to an extreme. It was created as an incremental approach to software development with the fundamental emphasis on how the code is written and tested. Fundamental idea classifies XP as an agile methodology is the teamwork and iterative based on system where coding, testing and design are taking place synchronously as the project develops. There is a maximum team collaboration and interaction involved, which however minimises the need for extensive documentation.

XP is not simply a methodology operating on a multitude or steps. A group of values were set to help guide team behaviour and understand how to implement XP with the paradigm of Agile project  management. XP has 5 key values which are; Simplicity, Effective communication, Consistent feedback, Respect and Courage.

Rules of XP

They were published to elucidate the main discipline of software development in XP. The rules outline step by step activities that are a part working XP model.

- Planning: Customer creates users stories, The duration of each iteration is decided and release of schedule is formulated. 

- Managing:  Project management establishes a workspace for his team to start work in. Defines and measures project velocity. Daily stand up meetings are conducted. 

- Designing: Start with a simple design to avoid delays in completion. Additional of functionality to the design should be reserved. Use CRC cards.

- Coding: Implementing collective code and ownership. Any developer can make changes to the code, identify and fix bugs. Use a system metaphor. 

XP team roles and responsibilities  

An XP team is made up of 5 roles besides a manager. It is preferable that each role is made role is designated to separate team members. Programmer , who writes the code implements user stories and unit tests. A coach who overseas  the team and makes sure everyone understands the nature of work assigned. A tracker, whose job is to test the incremental product during each report or cycle. A doomsayer, who keeps an eye out for potential risks and issues.