What you should be able to do
- Compare Waterfall, Incremental, Iterative, Prototyping, Spiral and V-model.
- Defend a model through project conditions.
01 / PROCESS MODELS AND AGILE SOFTWARE DEVELOPMENT / L03
Software Process Models
A process model is a trade-off between planning, feedback, risk and cost of change.
Which process model fits the uncertainty in this project?
Terms to use precisely
Common mistakes
- Calling Agile the right answer for every project.
- Choosing a model by memorized definition instead of project evidence.
Choose a model, or let the project recommend one.
Select a model to study it directly. Change the project conditions below when you want to compare which model fits the evidence.
RECOMMENDED FROM CONDITIONS
BEST FIT
Iterative
Frequent feedback and changing requirements favor repeated versions that can be evaluated and improved.
Watch out: Iteration without an evaluation goal can become repeated rework.01Plan a version
02Design
03Build and test
04Evaluate
05Refine the next version
This is a reasoned starting point, not an automatic answer. Defend it with the four conditions above.
CHECKED LEARNING LINKS
Watch the part that solves the gap.
Each link is matched to this lesson. Start with a quick video when available. Open the full lecture when you need the academic explanation.