Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Software Development     Processes                Sergey Nezdoliy,          Mobile developer, CSM
Old school style: Waterfall
Waterfall: ProsPros: - discipline - fixed costs ($) - precise plan of development - complete requirements - improved quali...
Waterfall: Cons - not flexible scope, change requests areimpossible - initial phase is too long (product may becomeout of ...
As a result
Waterfall: Cost of change
Iterative Waterfall
Agile processes: Scrum, Lean, Kanban - focused on delivering fully-tested,independent, valuable, small features - less ris...
Time-Cost-Scope-Quality triangle
Scrum iterative model
Regular Scrum Board
Lean development process - you select, plan develop, test, release onefeature before you select, plan develop, test,releas...
Scrum and Lean: differenceAgileLean
Kanban - Came from Toyota manufacturing: JIT (just intime) - As flexible as you can imagine - Limit WIP (Work in progress)...
Regular Kanban board
Q&A
Thank you!Any questions?sergey.nezdoliy@gmail.com
Processes in software development
Upcoming SlideShare
Loading in …5
×

Processes in software development

407 views

Published on

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

Published in: Education
  • Be the first to comment

  • Be the first to like this

Processes in software development

  1. 1. Software Development Processes Sergey Nezdoliy, Mobile developer, CSM
  2. 2. Old school style: Waterfall
  3. 3. Waterfall: ProsPros: - discipline - fixed costs ($) - precise plan of development - complete requirements - improved quality based on requirements(many issues are caught on design stage)
  4. 4. Waterfall: Cons - not flexible scope, change requests areimpossible - initial phase is too long (product may becomeout 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. 5. As a result
  6. 6. Waterfall: Cost of change
  7. 7. Iterative Waterfall
  8. 8. Agile processes: Scrum, Lean, Kanban - focused on delivering fully-tested,independent, valuable, small features - less risks: if one feature goes wrong, it doesnot 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. 9. Time-Cost-Scope-Quality triangle
  10. 10. Scrum iterative model
  11. 11. Regular Scrum Board
  12. 12. Lean development process - you select, plan develop, test, release onefeature before you select, plan develop, test,release next feature - you aim to eliminate waste whereverpossible - you therefore do nothing until you know itsnecessary or relevant
  13. 13. Scrum and Lean: differenceAgileLean
  14. 14. Kanban - Came from Toyota manufacturing: JIT (just intime) - As flexible as you can imagine - Limit WIP (Work in progress) as mainconcept
  15. 15. Regular Kanban board
  16. 16. Q&A
  17. 17. Thank you!Any questions?sergey.nezdoliy@gmail.com

×