Agile and Plan-Driven Methodologies

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/18

flashcard set

Earn XP

Description and Tags

Vocabulary flashcards covering the core values, principles, and characteristics of Agile, traditional software development models, plan-driven comparisons, and Agile adoption.

19 Terms

1
New cards

Agile Methodology

A modern software development methodology that emphasizes flexibility, collaboration, continuous improvement, and rapid delivery of software in small, manageable iterations.

2
New cards

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.

3
New cards

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.

4
New cards

Working Software (Agile Core Value)

An Agile core value prioritizing the frequent delivery of functional software to provide greater customer value than documentation alone.

5
New cards

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.

6
New cards

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.

7
New cards

Primary Measure of Progress (Agile)

Working software, as defined by the twelve Agile principles.

8
New cards

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.

9
New cards

Waterfall Model

The earliest linear, sequential software development model where development proceeds through fixed phases: Requirement Analysis, System Design, Implementation, Testing, Deployment, and Maintenance.

10
New cards

V-Model

An extension of the Waterfall model that pairs each development phase with a corresponding testing phase.

11
New cards

Spiral Model

A risk-driven iterative development model that combines prototyping with systematic development, requiring repeated risk analysis and experienced managers.

12
New cards

Incremental Model

A software development model where the system is developed and delivered in small functional increments.

13
New cards

Prototype Model

A development model in which a working prototype is built to clarify user requirements before constructing the final system.

14
New cards

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.

15
New cards

Agile Mindset

A way of thinking that focuses on continuous learning, collaboration, customer satisfaction, flexibility, and continuous improvement rather than strictly following fixed plans.

16
New cards

Agile Culture

The work environment and organizational values supporting Agile practices, characterized by trust, transparency, collaboration, continuous learning, and innovation.

17
New cards

Self-Organized Teams

Teams that decide how to complete tasks with minimal dependency on managers, fostering shared responsibility and producing the best solutions.

18
New cards

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.

19
New cards

Scaling Agile

An adoption challenge involving the increased complexity of managing Agile practices across multiple large teams compared to a single team.