Alternative Software Development Methodology

1,259
-1

Published on

Slide for TDD Workshop at GoSoft

Published in: Education, Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

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

No notes for slide

Alternative Software Development Methodology

  1. 1. An Alternative Software Development Methodology By @d4jens @9tae and @roofimonTuesday, June 28, 2011
  2. 2. 2001Tuesday, June 28, 2011
  3. 3. Hybrid Theory was a massive commercial success; it sold more than 4.8 million copies during its debut year, earning it the status of best-selling album of 2001, while singles such as "Crawling" and "One Step Closer" established themselves as staples among alternative rock radio play lists during the year.Tuesday, June 28, 2011
  4. 4. In February 2001, 17 software developers met at the Snowbird, Utah resort, to discuss lightweight development methods. They published the Manifesto for Agile SoftwareTuesday, June 28, 2011
  5. 5. Tuesday, June 28, 2011
  6. 6. Tuesday, June 28, 2011
  7. 7. Agenda • Morning Session • Agile Development Methodology • Agile Development Life Cycle • Agile Development Tools • Afternoon Session • Agile Development Best PracticeTuesday, June 28, 2011
  8. 8. Software Development ?Tuesday, June 28, 2011
  9. 9. Construction Architect Engineering Labor WorkTuesday, June 28, 2011
  10. 10. Construction Software Architect Software Engineering Software Worker (programmer)Tuesday, June 28, 2011
  11. 11. We were forced to believed in that.Tuesday, June 28, 2011
  12. 12. How many ways can we construct the building?Tuesday, June 28, 2011
  13. 13. How many ways can we construct software?Tuesday, June 28, 2011
  14. 14. As long as, user can change , adjust software to fit into their requirements.Tuesday, June 28, 2011
  15. 15. Software Development is CraftsmanshipTuesday, June 28, 2011
  16. 16. MethodologyTuesday, June 28, 2011
  17. 17. Methodology • Team Structure • Team Discipline • Individual DisciplineTuesday, June 28, 2011
  18. 18. The greatest waterfallTuesday, June 28, 2011
  19. 19. The greatest waterfallTuesday, June 28, 2011
  20. 20. Team Discipline • Document Oriented • Each step has clearly definition of document standard • Timeline is king • Change is bad !!!!!Tuesday, June 28, 2011
  21. 21. Team Structure • Silo • Clearly responsibilityTuesday, June 28, 2011
  22. 22. Individual Discipline • Mostly make something “done” but not “right” • Mostly said “please don’t change it” • Mostly make it for last, not for changeTuesday, June 28, 2011
  23. 23. Finally • Our software is same as building. Once it done you can’t change it.Tuesday, June 28, 2011
  24. 24. We need change!Tuesday, June 28, 2011
  25. 25. AgileTuesday, June 28, 2011
  26. 26. AgileTuesday, June 28, 2011
  27. 27. Discipline • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a planTuesday, June 28, 2011
  28. 28. Team Structure • One single team • Break the damn siloTuesday, June 28, 2011
  29. 29. Team Discipline • Change is good • We love change • Eliminate unchangeable modulesTuesday, June 28, 2011
  30. 30. Individual Discipline • Super Clear and have to follow • Test : Code : RefactorTuesday, June 28, 2011
  31. 31. The beginning of agile • Choose few agile practices and adopted into your team.Tuesday, June 28, 2011
  32. 32. Agile Methods Extreme Programming Scrum KanbanTuesday, June 28, 2011
  33. 33. eXtreme Programming XP is a set of practices that conform to the values and principles of Agile. XP is a discrete method, whereas Agile is a classification.Tuesday, June 28, 2011
  34. 34. Tuesday, June 28, 2011
  35. 35. Question? • Developers, Do you write automate test? • Why do you write test? • What is the benefit of testing?Tuesday, June 28, 2011
  36. 36. Pin XP on TDDTuesday, June 28, 2011
  37. 37. Tuesday, June 28, 2011
  38. 38. Why TCR? • Confident to change • Quality is good • Executable document • Continuous delivery • Customer happy :)Tuesday, June 28, 2011
  39. 39. Tuesday, June 28, 2011
  40. 40. Tuesday, June 28, 2011
  41. 41. Whole Team? • Same Mind set for the whole teamTuesday, June 28, 2011
  42. 42. “Sustainable”Tuesday, June 28, 2011
  43. 43. Continuous IntegrationTuesday, June 28, 2011
  44. 44. We need toolsTuesday, June 28, 2011
  45. 45. Tools • Project Management • Software Development • Software Testing • Software DeliveryTuesday, June 28, 2011
  46. 46. User StoryTuesday, June 28, 2011
  47. 47. User StoriesTuesday, June 28, 2011
  48. 48. Tuesday, June 28, 2011
  49. 49. Agile PM toolTuesday, June 28, 2011
  50. 50. Tuesday, June 28, 2011
  51. 51. Agile PM toolTuesday, June 28, 2011
  52. 52. Version Control SoftwareTuesday, June 28, 2011
  53. 53. Software Development • Maven2 : Project Lifecycle Management • Version Control Software • IDE • FrameworkTuesday, June 28, 2011
  54. 54. • Project Structure • Build • Dependency Management • Test • Style Checking • Code CoverageTuesday, June 28, 2011
  55. 55. Maven 2 Providing a uniform build system ๏ Providing quality project information ๏ Providing guidelines for best practices development ๏ Allowing transparent migration to new features ๏ Making the build process easyTuesday, June 28, 2011
  56. 56. IDE doesn’t matter as long as it has maven pluginTuesday, June 28, 2011
  57. 57. Framework is matter • Structure, Definition and Rules • Provide Complete Test CycleTuesday, June 28, 2011
  58. 58. Let’s see how TCR work?Tuesday, June 28, 2011
  59. 59. Tuesday, June 28, 2011
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×