Professional Documents
Culture Documents
Agile
Agile
Methodology
2
HELLO!
I am Cesiah Cascalla
3
4
5
6
7
TOPICS
▸ Waterfall
▸ Agile
▸ Agile versus Waterfall
▸ Scrum
▸ Use Case Diagram
8
1.
Waterfall
Traditional approach to software development
“
You complete one phase
(e.g. design) before moving
on to the next phase (e.g.
development)
You rarely aim to re-visit a
‘phase’ once it’s completed.
That means, you better get
whatever you’re doing right
the first time!
10
2.
Agile
Rapid, Adaptable, Quality-driven, Cooperative, Iterative
“
Agile is a time boxed,
terative approach to
software delivery that
builds software
ncrementally from the
start of the project,
nstead of trying to
deliver it all at once
near the end.
“
▸
▸
Characteristics
Modularity
Iterative
▸ Time-bound
▸ Incremental
▸ People-oriented
▸ Collaborative
13
3.
Waterfall versus
Agile
Rapid, Adaptable, Quality-driven, Cooperative, Iterative
14
Waterfall Agile
Less Efficient Delivers partial output at a
short period of time
Rarely adopts to change Adopts to change
High Risk Low risk
Testing is done at the end Testing is done every after
or sometimes skipped a partial development
Costly Less Cost
15
4.
Scrum Methodology
A methodology under the umbrella of Agile
“
Scrum allows us to focus on delivering the
business value in the shortest time. It rapidly
and repeatedly inspects actual working
software.
4.
Use Case Diagram
A methodology under the umbrella of Agile
“
A use case diagram is
a dynamic or behavior
diagram in UML. Use
case diagrams model
the functionality of a
system using actors
and use cases.
“
Why Make Use Case Diagrams?
▸ Use case diagrams are valuable for visualizing the
functional requirements of a system that will
translate into design choices and development
priorities.
▸ They help identify any internal or external factors
that may influence the system and should be taken
into consideration.
▸ They provide a good high level analysis.
22
THANKS!