DEVELOPMENT METHODOLOGIES
|
|
Agile
|
|
A very flexible SDLC methodology in terms of requirements, planning, results, and resources. Major Representatives: eXtreme Programming, SCRUM.
|
|
|
|
|
|
Test Driven Development
|
|
It is not a standalone methodology, rather approach which can be applicable to any methodology.
|
|
|
|
|
|
SCRUM
|
|
Used for long term support projects with changing scope and many independent assignments within an agreed time constrained cycles. This methodology is distinguished by stable project team with well defined roles.
|
|
|
|
|
|
Iterative
|
|
Each Iteration/Phase follows “local” waterfall model and produces interim results for evaluation/approval.
|
|
|
|
|
|
Waterfall
|
|
Within this methodology each consequent phase begins after the previous one has been done.
|
|
|
|
|
|
Staggered Waterfall
|
|
Used for relatively short projects (1-6 months), mostly with Fixed Price contract model.
The difference from classical Waterfall methodology is that the phases may overlap, which allows time saving, better use of resources, trying the results of a previous phase for the next phase.
|
|
|
|
|
|
Iterative Test Driven
|
|
Used for projects lasting 3+ months with distinctive, relatively independent iterations or modules that strongly need quality control.
|
|
|
|
|
|
Support
|
|
Used for support works (task based). This methodology is marked with the simplified tasks processing, few efforts for each task and no set timelines. Project team is small (1-3 people). The lifecycle of every task can be described as waterfall.
|
|
|
|
|