Highlevel Intro for students into different processes in software development; Waterfall, Scrum, Kanban, Lean

1. Software Development
Processes
Sergey Nezdoliy,
Mobile developer, CSM

2. Old school style: Waterfall

3. Waterfall: Pros
Pros:
- discipline
- fixed costs ($)
- precise plan of development
- complete requirements
- improved quality based on requirements
(many issues are caught on design stage)

4. Waterfall: Cons
- not flexible scope, 'change requests' are
impossible
- initial phase is too long (product may become
out of date)
- overwork in case of unexpected issues
- redundant communication between devs,
designers, managers on different phases
- frequently failed deadlines
- high risks, no re-visit of phases

5. As a result

6. Waterfall: Cost of change

7. Iterative Waterfall

8. Agile processes: Scrum, Lean, Kanban
- focused on delivering fully-tested,
independent, valuable, small features
- less risks: if one feature goes wrong, it does
not impact other features
- more flexibility (time-cost-scope triangle)
- easy 'change requests'
- ready for release with each new feature
- phases are not separate
- works for both FTE and Time & Material
- ...

9. Time-Cost-Scope-Quality triangle

10. Scrum iterative model

12. Regular Scrum Board

13. Lean development process
- you select, plan develop, test, release one
feature before you select, plan develop, test,
release next feature
- you aim to eliminate 'waste' wherever
possible
- you therefore do nothing until you know it's
necessary or relevant

14. Scrum and Lean: difference
Agile
Lean

15. Kanban
- Came from Toyota manufacturing: JIT (just in
time)
- As flexible as you can imagine
- Limit WIP (Work in progress) as main
concept

16. Regular Kanban board

17. Q&A

18. Thank you!
Any questions?
sergey.nezdoliy@gmail.com