Agile Methodologies

AGILE METHODOLOGIES

1.

Development Methodologies..........................................................................................................3 1.1 SCRUM ..................................................................................................................................... 3 1.1.1 1.1.2 1.1.3 1.1.4 1.1.5 1.1.6 1.2 1.3 Roles................................................................................................................................ 4 The Sprint Cycle ............................................................................................................... 5 The Product Backlog ........................................................................................................ 6 The Sprint Backlog........................................................................................................... 6 Burndown Charts ............................................................................................................. 7 Meetings .......................................................................................................................... 9

Kanban................................................................................................................................... 12 Extreme Programming .......................................................................................................... 13 Basic Extreme Programming ......................................................................................... 13

1.3.1

2|Page

1. Development Methodologies
Agilesoftware development is a group of software development methodologies based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptualframework that promotes foreseen interactions throughout the development cycle. The Agile Manifesto introduced the term in 2001.

1.1 SCRUM
Scrum is not a methodology or set of engineering practices. It is, instead, a lightweight framework that was designed to manage software and product development. Ken Schwaber and Jeff Sutherland describe Scrum like this: Scrum (n): A framework within whichpeople can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. Scrum is: • • • Lightweight Simple to understand Extremely difficult to master

Scrum is a process framework that has been used to manage complex product development since the early 1990s. Scrum is not a process or a technique for building products; rather, it is aframework within which you can employ various processes and techniques. Scrum makes clear the relative efficacy of your product management and development practices so that you can improve. Scrum relies on a fixed cadence of iterative cycles called sprints. Each sprint begins with a planning meeting and ends with a demonstration of potentially shippable product. Scrum is characterized by a high levelof feedback and transparency, both within the team and outside of it. Its short cycles and collaborative nature make it ideal for projects with rapidly changing and/or highly emergent requirements.

3|Page

1.1.1 Roles
Scrum is built on five core values and has three distinct roles, three artifacts and three (or four) meetings.
•

ScrumMaster A race car has gauges and sensors to helpmonitor the engine and it also has oil. Without oil, the engine would grind to a halt, destroying itself in the process. The oil is everywhere, keeping the parts of the engine working smoothly, cooling them and ensuring they perform well under stress. The ScrumMaster is like that. He has embedded sensors and gauges that allow him to identify when the team is not performing to its ability and he has...