1/18
Vocabulary flashcards covering the core values, principles, and characteristics of Agile, traditional software development models, plan-driven comparisons, and Agile adoption.
Agile Methodology
A modern software development methodology that emphasizes flexibility, collaboration, continuous improvement, and rapid delivery of software in small, manageable iterations.
Agile Manifesto (2001)
A foundational document created by 17 software experts that proposed an adaptive software development approach based on four core values and twelve principles.
Individuals and Interactions
An Agile core value emphasizing that people are the most important part of software development and that effective communication and teamwork lead to better results.
Working Software (Agile Core Value)
An Agile core value prioritizing the frequent delivery of functional software to provide greater customer value than documentation alone.
Customer Collaboration (Agile Core Value)
An Agile core value stating that customers should actively participate throughout the development process and provide regular feedback to ensure the product meets expectations.
Responding to Change (Agile Core Value)
An Agile core value emphasizing that teams welcome changing requirements even in later stages of development due to business needs or market conditions.
Primary Measure of Progress (Agile)
Working software, as defined by the twelve Agile principles.
Traditional SDLC Models
Software Development Life Cycle models that follow a sequential and structured approach where each phase must be completed before moving to the next.
Waterfall Model
The earliest linear, sequential software development model where development proceeds through fixed phases: Requirement Analysis, System Design, Implementation, Testing, Deployment, and Maintenance.
V-Model
An extension of the Waterfall model that pairs each development phase with a corresponding testing phase.
Spiral Model
A risk-driven iterative development model that combines prototyping with systematic development, requiring repeated risk analysis and experienced managers.
Incremental Model
A software development model where the system is developed and delivered in small functional increments.
Prototype Model
A development model in which a working prototype is built to clarify user requirements before constructing the final system.
Plan-Driven Methodology
A development approach summarized as 'plan first, build later,' characterized by complete upfront planning, fixed requirements, extensive documentation, manager-driven teams, and final product delivery at the end.
Agile Mindset
A way of thinking that focuses on continuous learning, collaboration, customer satisfaction, flexibility, and continuous improvement rather than strictly following fixed plans.
Agile Culture
The work environment and organizational values supporting Agile practices, characterized by trust, transparency, collaboration, continuous learning, and innovation.
Self-Organized Teams
Teams that decide how to complete tasks with minimal dependency on managers, fostering shared responsibility and producing the best solutions.
Agile Adoption Challenges
The difficulties organizations encounter when shifting from traditional plan-driven development to Agile, such as resistance to change, lack of knowledge, and scaling difficulties.
Scaling Agile
An adoption challenge involving the increased complexity of managing Agile practices across multiple large teams compared to a single team.