Software development. xp, agile, etc.
0 likes460 views
Agile, eXtreme Programming (XP), and software prototyping are approaches to software development. Agile focuses on individuals, interactions, working software, and responding to change over processes, tools, documentation, and plans. XP uses pair programming, continuous integration, refactoring, and frequent releases. It also emphasizes shared understanding. Software prototyping identifies requirements early, gets users involved, and enhances or discards prototypes to reduce time and costs and ensure user satisfaction. Different methodologies work best depending on project size and needs.
Software development. xp, agile, etc.
- 1. Software Development Agile, eXtreme Programming and Software prototyping Philipp Rukin Web-developer @ Empatika Ltd. [email protected]
- 2. Agile
- 4. Agile || Principles ● Individuals and interactions over processes and tools ● Working software over comprehensive documentation ● Customer collaboration over contract negotiation ● Responding to change over following a plan
- 8. eXtreme Programming ● Fine scale feedback ● Continuous process ● Shared understanding and simplicity ● Programmer welfare
- 9. XP || Pair programming The driver writes code while the navigator reviews each line of code.
- 10. XP || CI, Refactoring and frequent releases ● CI - everyone works with the latest version of the product ● Refactoring - code only what you need today... if it is hard - refactor ● Frequent releases - satisfy your customer
- 12. XP || Shared understanding ● Everyone is responsible for all the code ● Everyone can explain how it all works (even customers) ● So everything should be simple!
- 14. XP || Criticism ● Small teams only (<12) ● Really good developers are needed ● Lack of documentation ● It is hard to develop estimates ● etc..
- 18. SW Prototyping || Process ● Identify requirements ● Develop ● Review ● Enhance or throw away
- 20. SW Prototyping || Advantages ● Early determination of requirements → reduced time and cost of development ● Increased user involvement → the product will satisfy user desires
- 22. SW Prototyping || Disadvantages ● User confusion ● Developer overattachment ● Excessive development ● Insufficient analysis
- 23. SW Prototyping || Our prototypes
- 24. SW Prototyping || Our prototypes
- 26. Summary ● There are a lot of methodologies ● It is hard to implement them for large teams ● They work great for small teams ● Different methodologies are suitable for different projects
- 27. Q&A In Flow Track your emotions inflow.mobi