Presentation about the basics of Agile Methodologies and how they can be applied to Scientific Research. This presentation later evolved into the Agile Research method. June 2008
8. Agile Response Market Needs EMBRACING CHANGE 02 Traditional Agile Time Cost of Change
9.
10. What is Agile? Agile processes are iterative processes that use specific project management and software engineering practices to sustain the delivery of new software functionality every one to four weeks 02
11. Agile Manifesto That is, while there is value in the items on the left, we value the items on the right more. We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: 02 More Important Important individuals and interactions processes and tools working software comprehensive documentation customer collaboration contract negotiation responding to change following a plan www.agilemanifesto.org
12. Agile Manifesto That is, while there is value in the items on the left, we value the items on the right more. We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: 02 More Important Important individuals and interactions processes and tools working software comprehensive documentation customer collaboration contract negotiation responding to change following a plan www.agilemanifesto.org AGILE : Only code Creating and responding to change
13.
14. Iterative vs Waterfall Soft-NOT-aware Software Software Software Paperware Focus In Executable Software You can't know everything at the beginning You learn as you work WATERFALL AGILE 02 Requirements Analysis&Design Implementation Testing Deployment Architecture Requirements … Iteration1 Iteration2 Iteration3 Release1 Release2 Release3
15. Iterative vs. Waterfall Soft-NOT-aware Software Software Software Paperware Focus In Executable Software You can't know everything at the beginning You learn as you work WATERFALL AGILE Adaptive Management Predictive Management what method fits me best? 02 Requirements Analysis&Design Implementation Testing Deployment Architecture Requirements … Iteration1 Iteration2 Iteration3 Release1 Release2 Release3
16. Why Iterative Development? knowledge Risk Iterations help acquiring knowledge Of both the problem and the solution Estimation Error Short term is easier to predict and estimate rather than long term Time Iterations 02
17. What makes a development process Agile ? Each iteration delivers working software . The phases in each iteration are nearly concurrent . Team uses specific engineering practices to keep the code base fresh and flexible . Teams are self-managing . Lean principles and techniques eliminate waste whenever possible. 02
22. How to use The State of Agile Development. Julio 2007- Version One 72% Pilot experience in Telefónica I+D 02 Scrum Scrum/ XP Custom/ DSDM XP Hybrid Other Hybrid 37% 23% 12% 9% 5%
31. XP. Values & Practices 04 Simple Design Test-Driven Development Pair Programming Refactoring COMMUNICATION SIMPLICITY COURAGE FEEDBACK Stub out code Watch test fail Refactor Repeat Get test to pass
32. XP. Values & Practices 04 COMMUNICATION SIMPLICITY COURAGE FEEDBACK Simple Design Test-Driven Development Pair Programming Refactoring Open Workspace Collective Ownership Continuous Integration Metaphor Sustainable Pace Coding Standard Acceptance Tests One Team Iterations Small Releases Release Plan Retrospective User Stories On–site Customer
33. XP: Planning/Feedback Loop 04 Code Pair Programming Unit Test Pair Negotiation Stand Up Meeting Acceptance Test Iteration Plan Release Plan
34. XP: Employment Practices The State of Agile Development. July 2007- Version One 04 Agile Practices