Download as PDF, PPTX
Uploaded byQA InfoTech
What is Agile Methodology?
The document outlines agile methodology, defining it as an iterative and incremental approach to software development emphasizing collaboration and adaptability. It discusses key agile principles, various models such as Scrum and Extreme Programming, and stresses the importance of communication, customer involvement, and responsiveness to change. The conclusion highlights the diversity of agile methodologies and their applicability depending on the project environment.
In this document
Powered by AI
Introduction to Agile methodology and agenda covering what Agile is, its principles, and types.
Definition of Agile; focused on iterative processes, team collaboration, customer satisfaction, and adaptability.
Visual representation of an Agile iteration including design, build, and test phases.
Introduces SCRUM including its backlog concepts, sprint cycles, and concepts like the Burndown Chart.
Details on Extreme Programming focusing on coding standards, refactoring, and development strategies.
Focus on the design and build processes with methods for feature planning and representation.
Summarizes Agile methodologies, highlighting the importance of choosing the right approach based on the project.
Thank you note and contact information for further inquiries.
More Related Content
Similar to What is Agile Methodology?
What is Agile Methodology?
- 1.
- 2. Agenda ➢ What isAgile? ➢ Generic Agile Methodology ➢ Agile Principles ➢ Types of Agile Methodologies ○ SCRUM Model ■ SCRUM Board ■ Burndown Chart ○ Extreme Programming ○ Feature Driven Development Copyright © by QAInfoTech. All rights reserved.
- 3. What is Agile? “Agileis an iterative and incremental (evolutionary) approach to software development which is performed in a highly collaborative manner with "just enough" ceremony that produces high quality software which meets the changing needs of its stakeholders” - Scott Ambler, IBM In common usage, “Agile” refers to being adaptable; to move and respond quickly. Copyright © by QAInfoTech. All rights reserved.
- 4. Generic Agile Methodology Copyright© by QAInfoTech. All rights reserved.
- 5. Agile Principles ➢ Dothings in small increments with minimal planning ➢ Iterations - short time frames ➢ Follow a full SDLC with small, self-organizing teams which work with a common goal and a high degree of communication ➢ Each team needs to have a customer representative ➢ Frequent meetings and less documentation ➢ Highest priority is to satisfy the customer through early and continuous delivery ➢ Welcome changing requirements ➢ Working software is the primary measure of progress ➢ Business people and developers must work together daily throughout the project Copyright © by QAInfoTech. All rights reserved.
- 6. An Agile Iteration FeatureA Feature C Copyright © by QAInfoTech. All rights reserved. Fixed Time Feature B Design Test Build
- 7. SCRUM Product Backlog Copyright ©by QAInfoTech. All rights reserved. Sprint Backlog Daily SCRUM Sprint 2 - 4 weeks Burndown Chart
- 8. SCRUM Board Copyright ©by QAInfoTech. All rights reserved.
- 9. Learning from theBurndown Chart Copyright © by QAInfoTech. All rights reserved. Start Date Time Target Date
- 10. Extreme Programming Copyright ©by QAInfoTech. All rights reserved. ➢ XP- Project Implementation/Development while SCRUM-Project Management ➢ Metaphor - use short names and descriptions to communicate common terms ➢ Refactoring - improve the design of the software through every stage of development ➢ Coding Standard - the programmers write code in the same way ➢ Paired Programming
- 11. Feature Driven Development Copyright© by QAInfoTech. All rights reserved. ➢ Focuses on the design and building phases ➢ Develop an Overall Model:- overall shape of the system, classes, inter-relationships ➢ Build Feature List:- produce fine grained feature list ➢ Plan By Feature:- sequenced feature set assigned to chief programmers ➢ Design by Feature:- each feature is represented by a sequence diagram in UML ➢ Build By Feature:-the code for each feature is written by the members of the team
- 12. Conclusion ➢ Agile isnot just about scrum and sprint ➢ Various methods are prevalent for implementing agile ➢ Choosing the right Agile methodology depends upon your environment ➢ Agile is IIA-Iteration, incremental, adoptive ➢ Agile or not, ask yourself if the process is IIA ➢ Different aspects of the project can be handled by different methodologies Copyright © by QAInfoTech. All rights reserved.
- 13.