Agile Software Development : case of small teamand small software project

1. Agile Practices : case of small teamand small software project ThatchapholSaranurak 11 August 2009

2. What is ‘Agility’ ?

3. What is ‘Agility’ ? Coined in 2001 "The ability to move faster than those things that can harm your project…"

4. Agility matters (in our lives) because of CHANGES

5. Agility matters (in our lives) because of CHANGES Frequently

6. Agility matters (in our lives) because of CHANGES Frequently&Simultaneously

7. CHANGES

8. Begin -->

10. To be open-minded

12. Practice : Release frequently Release MonthlyAnd you will…

13. Practice : Release frequently #1Assure aboutintegration and deployment issues early

14. Practice : Release frequently You project is alwaysready to submit

15. Practice : Release frequently Use automated installer(Setup Projectis extremely easy in VS.NET 2008 )

16. Practice : Release frequently #2Be Productive

17. Practice : Release frequently Timebox forces you to implement only themostimportant

18. Practice : Release frequently Reachable goal boosts

19. Practice : Release frequently #3Get Feedback

20. Practice : Release frequently Evaluate trade-offs, actively(More memory-efficient, less performance ?)

21. Practice : Release frequently Design is gradually more accurate direction

22. 5 Practices (for small team and small project) Release frequently Design for ideas Test! Code for future Communicate agilely

23. Practice : Design for ideas Design idea will be evolving during development(Especially when using unfamiliar technology)

24. Practice : Design for ideas If you design it too specifically… (Method details, datatypes, parameters)

25. Practice : Design for ideas and even document it

26. Practice : Design for ideas You will surely REDO it againor else…GET STUCK with your bad design

27. Suggestion 1 Design in Paper or whiteboard Take a photo for sharing Practice : Design for ideas

28. Suggestion 2 Practice : Design for ideas CRC design method Class name Responsibility What it is supposed to do ? Collaborator what other objects it works with ?

29. Suggestion 3 Practice : Design for ideas Make it easy for test

30. Suggestion 4 Practice : Design for ideas As simple as possible KISS Principle

31. 5 Practices (for small team and small project) Release frequently Design for ideas Test! Code for future Communicate agilely

32. Practice : Test! Test it!programmatically

33. Practice : Test! Fewer Bugs & Faster DebugKnow problem early and specifically

34. Practice : Test! Comfortably RefactorNo need to check if it still really works

35. Practice : Test! Simple DesignTest Before (TDD): design will be never over complicatedTest After: method that hard to test is need to simplify

36. Practice : Test! Good DocumentationGood test covers use cases

37. Practice : Test! Unit Testing Framework(Nunit for .NET, Junit for Java, HttpUnitofr testing web,…)

38. Practice : Test! Use Mock when method touches another class More Reason for test ? Where to start ?

39. 5 Practices (for small team and small project) Release frequently Design for ideas Test! Code for future Communicate agilely

40. Practice : Code for future Your code is used many many more times than it is written

41. Practice : Code for future Make code EASY to

42. Practice : Code for future Make code EASY to Read

43. Practice : Code for future Make code EASY to Read Test

44. Practice : Code for future Make code EASY to Read Test & Debug

45. #1 EASY to Read Reader get what code does without reading comment Expressive naming Comment why code does it Use enum Don’t quick hack Insert +1 or -1 and it just works! Don’t concern performance too much <<1 instead of *2 Practice : Code for future

46. #2 EASY to Test Query – command separation Make query code has no side-effect (it’s easy to test now) Small class One method one purpose Practice : Code for future

47. #3 EASY to Debug Always handle or throw all exception No empty catch block Provide useful error messages Categorize them Program defects Environment problems User Error Practice : Code for future

48. 5 Practices (for small team and small project) Release frequently Design for ideas Test! Code for future Communicate agilely

49. Practice : Communicate agilely Documents that dictateall of what to do

50. Practice : Communicate agilely Documents that dictateall of what to do

51. Practice : Communicate agilely Need more dynamic communication techniques

52. Practice : Communicate agilely Complete but Flexible

53. Stand up Meeting Twice a week Everybody answers in 3 minutes What did I do? What will I do? What problems I face? Everybody Stands Up And you ain’tgonna waste time :)

54. PivotalTracker(Project Management Software)

55. PivotalTracker(Project Management Software) User story Focus on features Measure velocity Can generate charts

56. Mailing List For Sharing Ideas New design ? Problem’s solution ? Important Issue ?

57. Message in Version Control You know

58. Practice : Communicate agilely Stand up MeetingPivotalTrackerMailing ListMessage in Version Control

59. Conclusion This concludes Agile practicesI suggest for small team and small project

60. Conclusion However, there are… Many Other Practices

61. Conclusion And Many Ways to Apply How? Image fromhttp://www.flickr.com/photos/legojeff/1296661311/

62. Let’s go Agile :)