Your SlideShare is downloading. ×
0
Processes in software development
Processes in software development
Processes in software development
Processes in software development
Processes in software development
Processes in software development
Processes in software development
Processes in software development
Processes in software development
Processes in software development
Processes in software development
Processes in software development
Processes in software development
Processes in software development
Processes in software development
Processes in software development
Processes in software development
Processes in software development
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Processes in software development

173

Published on

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

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

Published in: Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
173
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  1. Software Development Processes Sergey Nezdoliy, Mobile developer, CSM
  2. Old school style: Waterfall
  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. 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. 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 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. Time-Cost-Scope-Quality triangle
  10. Scrum iterative model
  11. Regular Scrum Board
  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. Scrum and Lean: differenceAgileLean
  14. Kanban - Came from Toyota manufacturing: JIT (just intime) - As flexible as you can imagine - Limit WIP (Work in progress) as mainconcept
  15. Regular Kanban board
  16. Q&A
  17. Thank you!Any questions?sergey.nezdoliy@gmail.com

×