IT 363 - Wk 2 Agile Software Development

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

1/15

encourage image

There's no tags or description

Looks like no tags are added yet.

16 Terms

1
New cards
Agile Software Development
An iterative approach to software development that emphasizes customer involvement, frequent delivery, collaboration, and responding to change.
2
New cards
Problems with Waterfall
High failure rate, heavy process, changing requirements, and unpredictable business situations.
3
New cards
Agile Manifesto
Agile values individuals and interactions over processes and tools; working software over comprehensive documentation; customer collaboration over contract negotiation; and responding to change over following a plan.
4
New cards
Iterative Development
Software is developed in short repeated cycles, usually one to four weeks, with working software demonstrated at the end of each iteration.
5
New cards
Customer Involvement
Agile emphasizes close, frequent cooperation between customers/business people and developers.
6
New cards
Daily Stand-Up
A short daily meeting used to share progress and obstacles.
7
New cards
Review Meeting
A meeting used to review completed work and gather feedback.
8
New cards
Retrospective Meeting
A meeting where the team discusses what went well, what went wrong, and how to improve.
9
New cards
Changing Requirements
Agile welcomes changing requirements, even late in development.
10
New cards
Self-Organized Team
A team that manages its own work and decides how to complete it.
11
New cards
Servant Leader
A leader who supports and coaches the team rather than using command-and-control management.
12
New cards
User Story
A short, high-level description of a requirement from the user's perspective.
13
New cards
Emerging Requirements
In Agile, requirements are not fully predefined and become clearer during development.
14
New cards
Requirements Validation
Agile uses frequent review meetings and acceptance tests to validate requirements.
15
New cards
Advantages of Agile
Increased customer satisfaction, faster time-to-market, reduced risk, improved collaboration, adaptability to change, transparency, and productivity.
16
New cards
Disadvantages of Agile
Difficult effort estimation, heavy dependence on customer input, communication challenges in large or remote teams, limited scope control, less emphasis on nonfunctional requirements, and risk of team burnout.