This document discusses methodologies for transitioning from a waterfall development process to an agile process. It provides an overview of waterfall methodology, describing its structure and predictable nature but noting its limitations in adapting to changes. It then covers several agile methodologies like Scrum, emphasizing its iterative approach, self-organizing teams, and emphasis on early feedback. Challenges of scaling Scrum to larger teams are mentioned. The document suggests when each methodology is best applied and poses questions about determining the optimal approach.

1. METHODOLOGIES
Transitioning Waterfall to Agile
Pance Gasteovski 15-05-2015

2. Agenda
02
○ Waterfall
○ Agile
• SCRUM
• XP,Kanban
○ QA

3. Walking on water and developing
software from a specification are
easy if both are frozen.
Edward V. Berard, in Life-Cycle Approaches

4. W A T E R F A L L M E T H O D O L O G Y

5. ○ Classical lifecycle model – common sense approach
05
WATERFALL METHODOLOGY

6. 06
WATERFALL METHODOLOGY – Why?
○ Easy to understand/easy to use
○ Intuitive
○ Provides Structure
○ Clear Milestones
○ Easy management

7. 07
WATERFALL METHODOLOGY – Problem?

8. 08
WATERFALL METHODOLOGY – Challenges?
○ Everything must be known upfront
○ Deliverables are frozen
• Not flexible to changes
• Cannot adapt
○ Everything comes together in the end (if it does)
○ Test and review at the very end
○ Too late for feedback

9. 9
WATERFALL METHODOLOGY – When?
○ Known environment
○ Predictable steps
○ Known technology
○ Short terms
○ Stable projects

11. A G I L E |

12. 12
SCRUM
KANBAN
XP
Scrumban…
A G I L E

13. 13
S C R U M
Simple management methodology for incremental
product development using cross-functional, self-
organized team

14. 14
• Alternative to Waterfall
• Iterative approach
– Fast feedback
• Exposes problems
• Autonomy/self organize
Scrum

15. 15
Scrum – vertical slice

16. 16
– Product Owner – visionary
– Scrum Team – autonomy
– Scrum Master – facilitator
Scrum Roles

17. 17
– Sprint Planning (beginning of sprint)
• Timeframe
• Stories
• Poker
– Daily standup (daily)
Scrum Meetings

18. 18
– Sprint Review (end of sprint)
– Retrospective (end of sprint)
Scrum Meetings

19. 19
Scrum Board

20. 20
– Boss/worker relationship
– Autonomy
– Responsibility
– Complexity with larger teams
– Product owner not available
– Distributed team
Scrum – Challenges?

21. 21
– Chaotic environment – new product development
– Not intended for repeatable work
– Uncertain requirements
– Unpredictable technology
– Self motivated team
Scrum – When?

22. 22
K A N B A N & XP
M A I N T O P I C |

23. 23
Which is the best?

24. Q U E S T I O N S ? |