Alternative Software Development Methodology

download Alternative Software Development Methodology

of 59

  • date post

    12-May-2015
  • Category

    Education

  • view

    1.147
  • download

    3

Embed Size (px)

description

Slide for TDD Workshop at GoSoft

Transcript of Alternative Software Development Methodology

  • 1.AnAlternative Software Development Methodology By @d4jens @9tae and @roomonTuesday, June 28, 2011

2. 2001Tuesday, June 28, 2011 3. Hybrid Theory was a massive commercial success; it soldmore than 4.8million copies during its debut year, earning it thestatus of best-selling album of 2001, while singles such as"Crawling" and "One Step Closer" established themselves asstaples among alternative rock radio play lists during the year.Tuesday, June 28, 2011 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. Tuesday, June 28, 2011 6. Tuesday, June 28, 2011 7. Agenda Morning Session Agile Development Methodology Agile Development Life Cycle Agile Development Tools Afternoon Session Agile Development Best PracticeTuesday, June 28, 2011 8. Software Development ?Tuesday, June 28, 2011 9. Construction Architect EngineeringLabor WorkTuesday, June 28, 2011 10. ConstructionSoftware Architect Software EngineeringSoftware Worker (programmer)Tuesday, June 28, 2011 11. We were forced tobelieved in that.Tuesday, June 28, 2011 12. How many ways can weconstruct the building?Tuesday, June 28, 2011 13. How many ways can we construct software?Tuesday, June 28, 2011 14. As long as, user canchange , adjust softwareto t into their requirements.Tuesday, June 28, 2011 15. SoftwareDevelopmentisCraftsmanshipTuesday, June 28, 2011 16. MethodologyTuesday, June 28, 2011 17. Methodology Team Structure Team Discipline Individual DisciplineTuesday, June 28, 2011 18. The greatest waterfallTuesday, June 28, 2011 19. The greatest waterfallTuesday, June 28, 2011 20. Team Discipline Document Oriented Each step has clearly denition of document standard Timeline is king Change is bad !!!!!Tuesday, June 28, 2011 21. Team Structure Silo Clearly responsibilityTuesday, June 28, 2011 22. Individual Discipline Mostly make something done but not right Mostly said please dont change it Mostly make it for last, not for changeTuesday, June 28, 2011 23. Finally Our software is same as building. Once it done you cant change it.Tuesday, June 28, 2011 24. We need change!Tuesday, June 28, 2011 25. AgileTuesday, June 28, 2011 26. AgileTuesday, June 28, 2011 27. DisciplineIndividuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a planTuesday, June 28, 2011 28. Team Structure One single team Break the damn siloTuesday, June 28, 2011 29. Team Discipline Change is good We love change Eliminate unchangeable modulesTuesday, June 28, 2011 30. Individual Discipline Super Clear and have to follow Test : Code : RefactorTuesday, June 28, 2011 31. The beginning of agile Choose few agile practices and adopted into your team.Tuesday, June 28, 2011 32. Agile Methods Extreme ProgrammingScrum KanbanTuesday, June 28, 2011 33. eXtreme ProgrammingXP is a set of practices that conformto the values and principles of Agile. XPis a discrete method, whereas Agile is aclassication.Tuesday, June 28, 2011 34. Tuesday, June 28, 2011 35. Question? Developers, Do you write automate test? Why do you write test? What is the benet of testing?Tuesday, June 28, 2011 36. Pin XP on TDDTuesday, June 28, 2011 37. Tuesday, June 28, 2011 38. Why TCR? Condent to change Quality is good Executable document Continuous delivery Customer happy :)Tuesday, June 28, 2011 39. Tuesday, June 28, 2011 40. Tuesday, June 28, 2011 41. Whole Team? Same Mind set for the whole teamTuesday, June 28, 2011 42. SustainableTuesday, June 28, 2011 43. Continuous IntegrationTuesday, June 28, 2011 44. We need toolsTuesday, June 28, 2011 45. Tools Project Management Software Development Software Testing Software DeliveryTuesday, June 28, 2011 46. User StoryTuesday, June 28, 2011 47. User StoriesTuesday, June 28, 2011 48. Tuesday, June 28, 2011 49. Agile PM toolTuesday, June 28, 2011 50. Tuesday, June 28, 2011 51. Agile PM toolTuesday, June 28, 2011 52. Version ControlSoftwareTuesday, June 28, 2011 53. Software Development Maven2 : Project Lifecycle Management Version Control Software IDE FrameworkTuesday, June 28, 2011 54. Project Structure Build Dependency Management Test Style Checking Code CoverageTuesday, June 28, 2011 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. IDE doesnt matter as longas it has maven pluginTuesday, June 28, 2011 57. Framework is matter Structure, Denition and Rules Provide Complete Test CycleTuesday, June 28, 2011 58. Lets see how TCRwork?Tuesday, June 28, 2011 59. Tuesday, June 28, 2011