agile session

22

Upload: christian-hipolito

Post on 15-Apr-2017

364 views

Category:

Education


0 download

TRANSCRIPT

Page 1: Agile Session
Page 2: Agile Session

AGILE METHODOLOGYAGILE METHODOLOGY

Page 3: Agile Session

What is AGILE?What is AGILE?

Page 4: Agile Session

QUICKQUICK

EASYEASY

Page 5: Agile Session

So what is an Agile So 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.

Page 6: Agile Session

QUICK GAMEQUICK GAME

Page 7: Agile Session

Ball Point GameBall Point GameThe 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.◦ There are a total of five iterations.

Page 8: Agile Session

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

Page 9: Agile Session

Agile MethodologiesAgile Methodologies

Scrum vs KanbanScrum vs Kanban

Page 10: Agile Session

SCRUMSCRUMis 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

Page 11: Agile Session

ROLESROLESProduct OwnerProduct Owner

Development TeamDevelopment TeamScrum MasterScrum Master

Page 12: Agile Session
Page 13: Agile Session

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

Page 14: Agile Session
Page 15: Agile Session

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

Page 16: Agile Session

Agile vs WaterfallAgile vs Waterfall

Page 17: Agile Session
Page 18: Agile Session
Page 19: Agile Session

QUESTIONS?QUESTIONS?

Page 20: Agile Session

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

Page 21: Agile Session

ENDENDThank youThank you

Page 22: Agile Session