Downloaded 134 times
Uploaded byThatchaphol Saranurak
Agile Practices
Agile practices are recommended for small teams and projects to help them adapt to changes. Key practices include releasing software frequently to get early feedback, designing for flexibility, thoroughly testing code, writing code with the future in mind, and communicating dynamically through standup meetings, project tracking software, mailing lists, and comments in version control. While these practices are suggested, teams have flexibility in how they apply agile methods suited to their specific needs. The overall goal is to help teams be responsive to changes through an adaptive approach.
More Related Content
Agile Practices
- 1. Agile Practices :case of small teamand small software projectThatchapholSaranurak11 August 2009
- 2.
- 3. What is ‘Agility’?Coined in 2001"The ability to move faster than those things that can harm your project…"
- 4. Agility matters (inour lives) because ofCHANGES
- 5. Agility matters (inour lives) because ofCHANGESFrequently
- 6. Agility matters (inour lives) because ofCHANGESFrequently&Simultaneously
- 7.
- 8.
- 9. Before that…Tune team’smindset To work for outcome
- 10. To beopen-minded
- 11. To becourageous 5 Practices (for small team and small project)Release frequentlyDesign for ideasTest!Code for futureCommunicate agilely
- 12. Practice : ReleasefrequentlyRelease MonthlyAnd you will…
- 13. Practice : Releasefrequently#1Assure aboutintegration and deployment issues early
- 14. Practice : ReleasefrequentlyYou project is alwaysready to submit
- 15. Practice : ReleasefrequentlyUse automated installer(Setup Projectis extremely easy in VS.NET 2008 )
- 16. Practice : Releasefrequently#2Be Productive
- 17. Practice : ReleasefrequentlyTimebox forces you to implement only themostimportant
- 18. Practice : ReleasefrequentlyReachable goal boosts
- 19. Practice : Releasefrequently#3Get Feedback
- 20. Practice : ReleasefrequentlyEvaluate trade-offs, actively(More memory-efficient, less performance ?)
- 21. Practice : Releasefrequently Design is gradually more accurate direction
- 22. 5 Practices(for small team and small project)Release frequentlyDesign for ideasTest!Code for futureCommunicate agilely
- 23. Practice : Designfor ideas Design idea will be evolving during development(Especially when using unfamiliar technology)
- 24. Practice : Designfor ideas If you design it too specifically… (Method details, datatypes, parameters)
- 25. Practice : Designfor ideas and even document it
- 26. Practice : Designfor ideasYou will surely REDO it againor else…GET STUCK with your bad design
- 27. Suggestion 1Design inPaper or whiteboardTake a photo for sharingPractice : Design for ideas
- 28. Suggestion 2Practice :Design for ideasCRC design methodClass nameResponsibilityWhat it is supposed to do ?Collaborator what other objects it works with ?
- 29. Suggestion 3 Practice: Design for ideasMake it easy for test
- 30. Suggestion 4 Practice: Design for ideasAs simple as possibleKISS Principle
- 31. 5 Practices(for small team and small project)Release frequentlyDesign for ideasTest!Code for futureCommunicate agilely
- 32. Practice : Test!Testit!programmatically
- 33. Practice : Test!FewerBugs & Faster DebugKnow problem early and specifically
- 34. Practice : Test!ComfortablyRefactorNo need to check if it still really works
- 35. Practice : Test!SimpleDesignTest Before (TDD): design will be never over complicatedTest After: method that hard to test is need to simplify
- 36. Practice : Test!GoodDocumentationGood test covers use cases
- 37. Practice : Test!UnitTesting Framework(Nunit for .NET, Junit for Java, HttpUnitofr testing web,…)
- 38. Practice : Test!UseMock when method touches another classMore Reason for test ? Where to start ?
- 39. 5 Practices(for small team and small project)Release frequentlyDesign for ideasTest!Code for futureCommunicate agilely
- 40. Practice : Codefor futureYour code is used many many more times than it is written
- 41. Practice : Codefor futureMake code EASY to
- 42. Practice : Codefor futureMake code EASY toRead
- 43. Practice : Codefor futureMake code EASY toReadTest
- 44. Practice : Codefor futureMake code EASY toReadTest& Debug
- 45. #1 EASY toReadReader get what code does without reading commentExpressive namingComment why code does itUse enumDon’t quick hack Insert +1 or -1 and it just works!Don’t concern performance too much<<1 instead of *2Practice : Code for future
- 46. #2 EASY toTestQuery – command separationMake query code has no side-effect (it’s easy to test now)Small classOne method one purposePractice : Code for future
- 47. #3 EASY toDebugAlways handle or throw all exceptionNo empty catch blockProvide useful error messagesCategorize themProgram defectsEnvironment problemsUser ErrorPractice : Code for future
- 48. 5 Practices(for small team and small project)Release frequentlyDesign for ideasTest!Code for futureCommunicate agilely
- 49. Practice : CommunicateagilelyDocuments that dictateall of what to do
- 50. Practice : CommunicateagilelyDocuments that dictateall of what to do
- 51. Practice : CommunicateagilelyNeed more dynamic communication techniques
- 52. Practice : CommunicateagilelyComplete but Flexible
- 53. Stand up MeetingTwicea weekEverybody answers in 3 minutesWhat did I do?What will I do?What problems I face?Everybody Stands UpAnd you ain’tgonna waste time :)
- 54.
- 55. PivotalTracker(Project Management Software)UserstoryFocus on featuresMeasure velocityCan generate charts
- 56. Mailing ListFor SharingIdeasNew design ?Problem’s solution ?Important Issue ?
- 57. Message in VersionControlYou know
- 58. Practice : CommunicateagilelyStand up MeetingPivotalTrackerMailing ListMessage in Version Control
- 59. ConclusionThis concludes AgilepracticesI suggest for small team and small project
- 60. ConclusionHowever, there are…ManyOther Practices
- 61. ConclusionAnd Many Waysto ApplyHow?Image fromhttp://www.flickr.com/photos/legojeff/1296661311/
- 62.