Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Agile Methodology

No description
by

Anastasia Ivanovskaya

on 26 November 2013

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Agile Methodology

Agile methodology
Waterfall development
What is Agile?
Scrum
Kanban
Scrumban -
taking best from both
Traditional approach
highly risky;
often more costly;
generally less efficient than Agile approaches
it's not a process, it's a philosophy or set of values
Agile Manifesto
Individuals and interactions

Working software

Customer collaboration
Responding to change
over processes and tools
over comprehensive documentation
over contract negotiation
over following a plan
instead of a
large group
spending a
long time
building a
big thing
,
we have a
small team
spending a
short time
building a
small thing
,
but
integrating regularly
to see the whole.
Split your organization
into small,
cross-functional, self-organizing teams.
Split your work
into a list of small, concrete deliverables.
Sort the list by priority and estimate the relative effort of each item.
Scrum rules
Split time
into short-fixed iterations (usually from 1 to 4 weeks), with potentially shippable code after each iteration.
Optimize the release plan
and update priorities in collaboration with the customer, based on the insights, gained by inspecting the release after each iteration.
Optimize the process
by having a retrospective after each iteration.
Visualize the workflow.
Kanban Board
Limit WIP (Work In Progress)
Measure the lead time
Workflow board
with limited amount of tasks in each column;
Daily short
scrum meeting
(planning and review);
No iterations, only
continuous flow
;
Team
+
needed roles;
WIP
controlled by workflow
state;
JIT (
Just In Time
) cards
Changes are added
as needed on the board;
Kanban board
with limited amount of tasks in each column;
Daily short
scrum meeting
(planning and review);
No iterations, only
continuous working process
;
Team
+ needed roles;
Work In Progress
controlled by workflow state;
Flexible
changes added
as needed on the board;
JIT (
Just In Time
) cards
Scrumban essentials
It sucks..
Questions?
That is, while there is value in the items on the right, we value the items on the left more.
Full transcript