How to succeed in software development. Following agile methodology principles helps to achieve much better results. Know more about eXtreme Programming, one of the famous agile software development methodology.
4. Disadvantages!
• High amount of risk!
• Impossible to go back and fix!
• No result until very end!
• Impossible to strictly follow the requirements!
9. Iteration lifecycle!
1. Figure out Use Cases!
2. Choose most valuable for iteration!
3. Analyze chosen use cases!
4. Design / Code / Deploy / Test!
5. Show results to customer!
6. Repeat from #2 considering feedback #5!
10. Benefits!
• Risk management!
• Early delivery!
• Cost control!
• High quality!
20. Coding Standards!
Coding Rules followed by the team!
• Formatting patterns!
• Naming conventions!
• Programming constructs to avoid!
• Custom agreements!
21. Collective Ownership!
Any developer of a team!
• Has access to the entire source code!
• Is allowed to change any part of code!
• Is responsible for the code!
IMPORTANT: Unit Tests required!
22. Collective Ownership - Benefits!
• Reduce negative effect of losing a programmer!
• Complex code eliminated by teammates!
• No “tricky code” owners!
• Full control over the code for everyone!
28. Continuous Integration!
Get system build several times a day!
Aims
• Prevent “integration hell”!
• Last stable build always available!
• Automatic tests running!
29. Continuous Integration - Principles!
• Maintain single code repository!
• Automate the build!
• Self-testing build!
• Everyone commits to the baseline daily!
• Automate deployment!
30. Planning Game!
• Release (1-6 months)
business cycle!
• Iteration (1-3 weeks)
developer cycle!
• Stand-up meeting
everyday!
• Story (feature)
measure of software for customer!
31. Release Planning!
1. Customer writes stories!
2. Developers estimate the stories!
3. Splitting/Combining the stories!
4. Sorting stories by value and risk!
5. Choosing the scope based on velocity!
6. Steering phase!
• customer can add a story or change the priority!
• developer can change the estimation!
• plan change!
32. Iteration Planning!
1. Dividing stories into tasks!
2. Estimating the tasks yesterday’s weather!
3. Devs take responsibility for tasks!
4. Load factor estimation 0.5 is normal value!
5. Rebalancing according to #4!
6. Steering phase!
• tasks adding!
• tasks reassigning !
• plan change!
33. Stand-Up Meeting!
• Short everyday meeting at the same time!
• Everybody stands for the whole meeting in circle!
• Everybody says!
• what he did yesterday!
• what he is doing today!
• what problems he has!
• For problems announcing (not solving)!
38. TDD - Cycle!
• Add test!
• Run all tests and fail (Red)!
• Make required change to succeed!
• Run all tests and succeed (Green)!
• Refactor to remove duplication (Refactor)!
39. Unit Tests Best Practices!
• Test first!
• Assert first!
• Arrange → Act → Assert!
• Tests isolation!
• Mocking dependencies!
43. Other Unit Tests!
• Explanation Test
explain with test!
• Learning (Boundary) Test
external library!
• Regression Test
bug elimination!
44. Test Greening Rules!
• Getting to Green strategies!
• obvious implementation!
• fake it!
• triangulation!
• Do the simplest solution possible!
• Postpone faced problems for next steps!
• No code for future!
48. Pair Programming - Problems!
• “Watch the master” phenomenon!
• Disengagement and silence!
How to fight with?!
Each developer keeps the keyboard in turn!
49. Pair Programming for TDD!
• Dev1: Write test!
• Dev2: Implement functionality!
• Dev1: Make refactoring!
• Dev1 ⇔ Dev2 and repeat!
51. References!
• Beck K. Extreme Programming Explained: Embrace Change!
• Beck K., Fowler M. Planning Extreme Programming!
• Beck K. Test Driven Development: By Example!