Agile ashish(s.e)

534 views

Published on

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

  • Be the first to like this

No Downloads
Views
Total views
534
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Agile ashish(s.e)

  1. 1. Presented by:Ashish Agrawal M.Tech.(2nd year) (Software Engineering)
  2. 2. Outline ● Introduction to Agile ● Water fall Vs Agile ● Agile lifecycle ● Graphical representation ● Agile manifesto ● Characteristics of Agile ● Techniques of Agile ● Limitations ● Conclusion
  3. 3. AGILE ● “Everything Should Be Made As Simple As Possible But Not Simpler” -Albert Einstein ●“ • -C . Burn
  4. 4. Definition ● The term agile can be defined as1) ability to move with quick easy grace, or 2)having a quick resourceful and adaptable character (Merriam-Webster 2002)
  5. 5. Waterfall Vs Agile Approach
  6. 6. Agile Lifecycle
  7. 7. Graphical Representation
  8. 8. AGILE MANIFESTO VALUES ● V1: Individual and interaction are valued over process and tools ● V2:Working software is valued over comprehensive documentation ● V3:Customer collaboration is valued over contract negotiation ● V4:Responding to change is valued over following a plan
  9. 9. AGILE MANIFESTO PRINCIPLES ● P1:Customer is the highest priority ● P2:Welcome changing requirements , even late in development ● P3:Deliver working software frequently ● P4:Bussiness people and developers must work together daily throughout the project
  10. 10. ● P5:Face-to-face conservation is the best communication method ● P6:Working software is the primary measure of progress. ● P7:Agile process promote sustainable development. ● P8:Continuous attention to technical excellence and good design enhance agility. ● P9:The best architecture , requirement , and design emerge from self-organizing teams.
  11. 11. CHARACTERISTICS ● Agile method break the task into small increments with minimal planning ● Iteration is a short time frame ● Each iteration involves a cross-functional team working in all function ● Each agile team must have customer representative ● Most of the agile methodology use daily face-to-face communication
  12. 12. Techniques of Agile 1. Pair programming-
  13. 13. 2. Continuous Customer Feedback-
  14. 14. 3. Whole team involvement-
  15. 15. 4. Daily stand-up meetings-
  16. 16. Techniques of Agile Agile Techniques Pros Cons • • Improve quality planning Gain commitment everyone • • Reduce bottleneck Increases flexibility changes Continuous integration • • Continuous customer feedback Daily meetings Whole involvement team Pair programming standup • require high level of communication from the entire team • • Lack of compatibility Mismatched skills Identifies build issues early Risk reduction • More work developers • • Customer interest & priorities Lead to more useful products • • Communication gaps Customer may become designer of system • Team work together to improve quality • Purpose of meeting may lost of from making for
  17. 17. Limitations ● The agilest have not clearly defined the context for their statements. ● Agile Manifesto and literature concerning agile software development have not thoroughly discussed the use of software tools and their role in agility. ● When software development is performed by several parties, more pressure to communication and coordination emerges.
  18. 18. Conclusion Most frequently changing thing in software development field is customer requirements which keep on changing with in fraction of second. Hence it become very difficult for developer to cope up with continuously changing requirement. In today’s cut throat competition it is very important to satisfy your customer , if you are not than you are out of the race. So in this environment Agile methodology is panacea to all. It provide flexibility to customers that they can change their requirement at any point of time according to their ease and this change is not a matter of worry to developers. In nutshell , Agile methodology rejuvenate conventional process of software development.
  19. 19. References ● S. W. Ambler, Agile Modeling. New York, NY: John Wiley and Sons, 2002 ● A. Cockburn, Agile Software Development. Reading, Massachusetts: Addison Wesley Longman, 2001. ● James Mark Jamieson, agile Quality Management Techniques,2012. ● A. Ahmed, S. Ahmad, Dr. N Ehsan, E. Mirza, S.Z. Sarwar, “Agile Software Development: Impact on Productivity and Quality” in the Proceedings of IEEE ICMIT.(2010).
  20. 20. Thank you

×