Agile methodology is an alternative to traditional project management that emphasizes empowering teams through continuous planning, testing, and integration. It focuses on collaboration and team decision making. Key aspects of Agile include making teams work efficiently through improved processes, applying principles incrementally without disrupting current systems, and choosing between Scrum and Kanban based on a team's needs - with Scrum best for teams requiring fundamental shifts and Kanban for gradual improvements.

2. AGILE METHODOLOGYAGILE METHODOLOGY

3. What is AGILE?What is AGILE?

4. QUICKQUICK
EASYEASY

5. So what is an AgileSo what is an Agile
Methodology???Methodology???
is an alternative to traditional project management
where emphasis is placed on empowering people to
collaborate and make team decisions in addition to
continuous planning, continuous testing and
continuous integration. It is typically used in software
development.

6. QUICK GAMEQUICK GAME

7. Ball Point GameBall Point Game
The objective of the Ball Point game is to get as many balls through the
team as possible within two minutes.
Rules:
◦Everyone is part of one big team.
◦Each ball must have air-time.
◦Each ball must be touched at least once by every team member.
◦Balls cannot be passed to your direct neighbour to your
immediate left or right.
◦Each ball must return to the same person who introduced it into
the system.

8. Agile Key PointsAgile Key Points
- Agile makes the team works- Agile makes the team works
- Agile improves efficiency- Agile improves efficiency
- Agile can work in large teams- Agile can work in large teams

9. Agile MethodologiesAgile Methodologies
Scrum vs KanbanScrum vs Kanban

10. SCRUMSCRUM
is a well defined process framework for structuring your
organization.
initial introduction of Scrum is not an end in itself. Working with
Scrum you want to change your teams’ habits: Take more
responsibility, raise code quality, increase speed. As your
teams commit to sprint goals, they are intrinsically motiviated
to get better and faster in order to deliver what they promised

11. ROLESROLES
Product OwnerProduct Owner
Development TeamDevelopment Team
Scrum MasterScrum Master

13. KANBANKANBAN
is way less structured than Scrum. It’s no process framework at all, but
a model for introducing change through incremental improvements. You
can apply Kanban principles to any process you are already
running, you organize your work on a Kanban board. There you have
states which every work item passes through from left to right. You pull
your work items along through the in progress, testing, ready for
release, and released columns starting from the left hand side based on
the allocated capacity of each of the columns

15. Kanban vs ScrumKanban vs Scrum
Looking at both agile software developmentLooking at both agile software development
methodologies it should be more clear what tomethodologies it should be more clear what to
introduce when: If your organization is really stuckintroduce when: If your organization is really stuck
and needs a fundamental shift towards a moreand needs a fundamental shift towards a more
efficient process, Scrum seems to be moreefficient process, Scrum seems to be more
appropiate. If you already have working processes,appropiate. If you already have working processes,
which you want to improve over time withoutwhich you want to improve over time without
shaking up the whole system, Kanban should beshaking up the whole system, Kanban should be
your tool of choice.your tool of choice.

16. Agile vs WaterfallAgile vs Waterfall

19. QUESTIONS?QUESTIONS?

20. ReferencesReferences
* wikipedia* wikipedia
** agilemethodology.orgagilemethodology.org
* for the image* for the image images.google.comimages.google.com

21. ENDEND
Thank youThank you