CC 313 Lesson 3 Set 4 — Comparisons and Application

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

1/13

encourage image

There's no tags or description

Looks like no tags are added yet.

Last updated 4:21 PM on 10/11/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai
Chat

No analytics yet

Send a link to your students to track their progress

14 Terms

1
New cards

Sprint Review

An event where the team demonstrates completed work and receives feedback from users or stakeholders.
2
New cards

Sprint Retrospective

A meeting to discuss what went well, what did not, and what to improve next time.
3
New cards

Sprint Review vs. Sprint Retrospective

Sprint Review focuses on the product; Sprint Retrospective focuses on improving the team's process.
4
New cards

Waterfall vs. Agile

Waterfall is more sequential with feedback often arriving later; Agile uses small cycles, frequent feedback, and adaptation.
5
New cards

Waterfall Scenario

A government payroll system with clear requirements and tightly controlled changes suits Waterfall or another plan-driven approach.
6
New cards

Agile or Iterative Scenario

A startup social media app with uncertain user preferences suits Agile or Iterative development.
7
New cards

Incremental Scenario

A school portal that releases login first, enrollment later, and grades afterward uses Incremental development.
8
New cards

Why Agile Became Popular

Applications, user requests, business needs, and technology change quickly.
9
New cards

Advantages of Agile

Frequent feedback, earlier usable software, easier adaptation, better communication, and earlier problem discovery.
10
New cards

Challenges of Agile

It requires strong communication, active users or clients, team discipline, and careful management of changing requirements.
11
New cards

When Agile May Be Difficult

When communication, user involvement, or team discipline is insufficient.
12
New cards

Choosing a Methodology

Choose based on the project's requirements, uncertainty, risks, users, and needs.
13
New cards

Purpose of Software Development Methodologies

To organize how development activities are performed while addressing the needs of a particular project.
14
New cards

Foundation of Software Development

Understand problems, gather requirements, design solutions, build software, then test, deploy, and maintain it.