Reducing Cost With Agile
Download as PPT, PDF5 likes6,748 views
The document discusses how adopting Agile practices can help reduce costs and increase project success rates. It provides an overview of the Agile manifesto and techniques like iterative development, improved communication, and leverage existing investments. Adopting Agile can lead to reduced inventory, quick turnaround focusing on required functionality, minimizing costs, and delivering working software sooner to generate savings and quicker time to market. This allows for a focus on ROI and increased project success rates through improved quality, productivity, visibility for customers, and alignment between business and technology needs.
![Agile Flavors Different Agile Flavors Description eXtreme Programming (XP) [Kent Beck] Widest known, developer-focused for small teams Scrum [Ken Schwaber] Focused on management practices Feature-Driven Development (FDD) [Jeff De Luca] Agile approach closest to conventional development Lean Software Development [Poppendieck] Inspired by Toyota Production System, particularly its product development practices Crystal methodologies [Alistair Cockburn] Set of methodologies Dynamic Systems Development Method (DSDM)[DSDM Consortium] Popular approach for Rapid Application Development (RAD) among European IT shops since 199 9](https://image.slidesharecdn.com/reducingcostwithagile-090906113414-phpapp01/85/Reducing-Cost-With-Agile-11-320.jpg)
Reducing Cost With Agile
- 1. Reducing Cost using Agile by Srini Kumar http://www.srinikumar.com
- 2. Agenda Current Scenario Enter Agile ? Agile Manifesto, Techniques Agile Development a Brief Reducing Cost? Project Success Rate Focus on ROI Agile Value Proposition
- 3. Current Scenario Economy slow down
- 4. Current Scenario Affecting IT Sector / Projects
- 5. Enter Agile Behind every cloud sun is shining
- 6. Agile Manifesto Agility is the ability to both create and respond to change in order to profit in a turbulent business environment. From the Manifesto for Agile Software Development We have uncovered better ways of software development by doing it and helping others to do it. Through this work we have come to value: Individuals and interactions Over processes and tools Working software Over comprehensive documentation Customer collaboration Over contract negotiation Responding to change Over following a plan “ That is, while there is value in the items on the right, we value the items on the left more”
- 7. Agile Techniques Techniques Iterative Development Improved Communication, Usage of Google Talk/Skype Share information by Bulletin Boards/Forums/Wikis Leverage Existing hardware/software Investments
- 8. Agility
- 11. Agile Flavors Different Agile Flavors Description eXtreme Programming (XP) [Kent Beck] Widest known, developer-focused for small teams Scrum [Ken Schwaber] Focused on management practices Feature-Driven Development (FDD) [Jeff De Luca] Agile approach closest to conventional development Lean Software Development [Poppendieck] Inspired by Toyota Production System, particularly its product development practices Crystal methodologies [Alistair Cockburn] Set of methodologies Dynamic Systems Development Method (DSDM)[DSDM Consortium] Popular approach for Rapid Application Development (RAD) among European IT shops since 199 9
- 12. Agile Development Example: How does it work?
- 13. Agile Development- Example: Scrum Process Flow
- 14. Agile Development Onsite Offshore Model Key Stakeholders: Team @ Offshore Scrum Master @ Offshore Satyam’s Onsite coordinator or Customer Representative to act as Product Owner Process Responsibility Onsite/ Offshore Product Backlog Update Product Owner Onsite Sprint Planning Team, Scrum Master, Product Owner Both Sprint Review Team, Scrum Master, Product Owner Both Sprint Retro Team, Scrum Master Offshore
- 15. Agile Tools Stack - Indicative Phase Java Release Planning X planer, Mingle, Version One, Rally, Work Load Leveling (Lean) Iteration Planning X planner, Mingle, Rally, Work Load Leveling (Lean) Requirement Management (User Stories) Wikis, Confluence, Optimal Trace, Doors, RequisitePro, CaliberRM Communication Wiki, Video / Tele conference , Instant Message Simple Design Enterprise Architect, Erwin, eUML2 Collaborative Development Collabnet, SourceForge Development IDE Eclipse Unit Testing Junit Code Coverage EMMA, Clover Code Standards Checking CheckStyle, PMD Continuous Int.. Cruise Control, Maven
- 16. Agile Sample Developer Stack Agile best practices Continuous Integration Test Driven Development Java build Best Practices IDE Neutral Ant Based Maven 2 Subversion Eclipse / NetBeans Ant + Maven2 JUnit EMMA Code Coverage Unit Testing Build Scripting IDE CheckStyle Coding Standards Subversion Client TortoiseSVN / Subclipse Continuous Integration CruiseControl Version Control Server Workstation JMeter NetBeans Profiler Load Testing Profiling Performance Validation Watij Automated Functional Testing
- 17. So will Agile reduce Cost? Or Provide Savings…… Reduced Inventory Quick Turn around, Focus on required functionality Minimize Cost spent Deliver soon Generate savings, Quicker go to Market Reprioritizing work Increase cash flow Quicker stabilization Faster offsite-onsite delivery
- 18. Focus On ROI Accept requirement changes as inevitable Work on the Often and Always Used Features FIRST !!
- 19. Agile: Project Success Rate
- 21. Adopting agile leads to Improved quality Improved productivity / reduced cost Increased project visibility for the customer Better alignment of business and technology needs Ready to show product at regular intervals Lower application development risks Better ROI !!! Agile Value Proposition
- 22. Q & A Thank you