Development Process For Commercial Software Development

1,864
-1

Published on

Presented at IT-Enterprise, 2009, Minsk

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,864
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
35
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Development Process For Commercial Software Development

  1. 1. Choosing commercial software development process<br />Uladzimir Liashkevich, © 2009<br />
  2. 2. Development process<br />Software engineering – systematic and disciplined approach<br />Code & fix - hack until it works <br />Software development methodologies<br />Waterfall<br />Spiral model<br />Rational Unified Process<br />Agile development<br />Lean development<br />
  3. 3. Waterfall: theory<br />
  4. 4. Waterfall: how it works<br />
  5. 5. Waterfall: time-to-market<br />Safeguard – Ballistic Missile Defense System<br />No late changes in requirements<br />6 years of development<br />5k person-years<br />$25 bln<br />Terminated after 133 days of operation – new missiles were faster, than anti-missile missiles<br />
  6. 6. Waterfall: target aiming<br />
  7. 7. Waterfall: target aiming<br />
  8. 8. Waterfall: target aiming<br />
  9. 9. Waterfall: cost of change<br />
  10. 10. Waterfall: problems<br />Planning doesn’t work<br />Business may change faster than software is developed<br />Changes in requirements are not easy<br />Cost of change<br />Progress is not clear<br />
  11. 11. Solution<br />Communication & Feedback<br />Continuous<br />Software development as social activity<br />It is not about applying math methods<br />
  12. 12. Agile manifesto<br />Individuals and interactions over processes and tools<br />Working software over comprehensive documentation<br />Customer collaboration over contract negotiation<br />Responding to change over following a plan<br />
  13. 13. Agile vs Waterfall<br />
  14. 14. Team building<br />Feature team<br />Sits together<br />Common goal<br />Motivated individuals<br />Team building is hard<br />
  15. 15. Involve customer<br />Product owner<br />Daily collaboration<br />Product backlog<br />User stories<br />Prototyping<br />Prioritizing backlog<br />
  16. 16. Iterative development<br />Working software is the measure of success<br />Continuously deliver value<br />Early and often<br />Valuable feedback<br />Iteration planning<br />High priority user stories<br />Story estimates<br />Acceptance criteria<br />Iteration scope<br />Implementation<br />Tough things first<br />Technical tasks as a part of user stories<br />Complete features<br />Continuous communication<br />
  17. 17. Typical Agile life-cycle<br />
  18. 18. Agile: target aiming<br />
  19. 19. Agile: target aiming<br />
  20. 20. Agile: target aiming<br />
  21. 21. Quality<br />Quality is free<br />Only if you are ready to pay for it<br />External quality<br />Zero defect principle<br />Internal quality<br />Technological debt<br />
  22. 22. Questions?<br />

×