0% found this document useful (0 votes)
77 views13 pages

Understanding Agile Methodologies Explained

The document discusses different agile methodologies like Scrum, Kanban, XP, Lean, DSDM, FDD, and Crystal. It notes that while these methodologies share common values like customer collaboration and iterative development, they differ in their specific practices. It concludes by questioning how much customization of agile methods is acceptable and where to draw the line between right and wrong implementations.

Uploaded by

katejohnson.gb
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
77 views13 pages

Understanding Agile Methodologies Explained

The document discusses different agile methodologies like Scrum, Kanban, XP, Lean, DSDM, FDD, and Crystal. It notes that while these methodologies share common values like customer collaboration and iterative development, they differ in their specific practices. It concludes by questioning how much customization of agile methods is acceptable and where to draw the line between right and wrong implementations.

Uploaded by

katejohnson.gb
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Agile, but not.

Right or wrong ?

Catherine Samuel
THE AGILE
METHODOLOGY
Agile methodology is a project management framework that breaks
projects down into several dynamic phases, commonly known as
sprints.
Agile methods
(some of the most well-known)
● Scrum is one of the most widely used Agile
methodologies.

● It organizes work into time-boxed iterations


called sprints, usually 2-4 weeks long.

Scrum ● A Scrum team typically consists of a product


owner, a Scrum master, and development team
members.

● Daily stand-up meetings, sprint planning, sprint


review, and sprint retrospective are key
ceremonies in Scrum.
● Kanban is a visual framework for managing
work as it flows through a process.

● It emphasizes continuous delivery and allows


for changes to be made dynamically.

Kanban ● Work items are represented on a Kanban board,


moving from one column to the next as they
progress.

● It helps manage and optimize the flow of work.


● XP is a software development methodology that
focuses on improving software quality and

Extreme
responsiveness to changing customer
requirements.

Programming ● Practices in XP include pair programming,


test-driven development (TDD), continuous

(XP) integration, and frequent releases.

● It emphasizes customer satisfaction, teamwork,


and simplicity.
● Lean is inspired by lean manufacturing
principles and aims to eliminate waste in the
software development process.

Lean Software ● It focuses on delivering value to the customer,


optimizing the whole process, and empowering

Development the team.

● Principles include maximizing customer value,


minimizing lead time, and continuous
improvement.
Dynamic
● DSDM is an Agile framework that emphasizes
the need for active user involvement throughout

Systems
the project.

● It provides a set of principles, roles, and

Development practices for iterative and incremental


development.

Method (DSDM) ● DSDM projects are time-boxed and require user


feedback at the end of each iteration.
● FDD is an iterative and incremental software
development methodology.

Feature-Driven ● It focuses on building features in small,


client-valued increments.

Development ● The process involves domain walkthroughs,

(FDD)
feature lists, and regular builds.
● Crystal is a family of Agile methodologies
developed by Alistair Cockburn.

● Each variant of Crystal is tailored to specific


project characteristics, such as team size,

Crystal system criticality, and project priorities.

● It emphasizes communication, teamwork, and


simplicity.
These methodologies share common values and principles, such as
customer collaboration, responding to change, and iterative
development, but they may differ in their specific practices and
implementation details.

Teams often choose or customize Agile methodologies based on their


specific project needs and organizational context.
Now, how much
‘agile’ is really agile ?
Where is the line?

How much can it be customised?

What is right and what is wrong?

You might also like